If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > SQL0818N A timestamp conflict occurred.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-22-05, 14:26
pinecone pinecone is offline
Registered User
 
Join Date: Apr 2004
Posts: 58
Lightbulb SQL0818N A timestamp conflict occurred.

We have same programs running on DB2 v7.1, AIX 4.3 and another on v8.1., AIX 5.2. Why the programs run fine on the former environment but got SQL0818N A timestamp conflict occurred when running on the latter.

Any inputs would be greatly appreciated. Thanks in advance.
Reply With Quote
  #2 (permalink)  
Old 02-22-05, 14:38
Marcus_A Marcus_A is offline
Registered User
 
Join Date: May 2003
Location: USA
Posts: 5,196
Check out the Messages and Codes Vol 2 manual for a detailed explanaiton of what the problem may be, and ways to fix each problem.

The problem is related to the timestamp of your package not matching the timestamp in the application code that calls DB2 (invoking the package), that is used to make sure that the correct version of the package is being used.
__________________
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390
Reply With Quote
  #3 (permalink)  
Old 02-22-05, 15:33
pinecone pinecone is offline
Registered User
 
Join Date: Apr 2004
Posts: 58
Thanks.

I'd like to check the timestamp of when the stored procedure was last updated. From syscat.procedures, I can only see create_time. Where can I find the last updated timestamp when the store procedure was last compiled?
Reply With Quote
  #4 (permalink)  
Old 02-22-05, 17:27
Marcus_A Marcus_A is offline
Registered User
 
Join Date: May 2003
Location: USA
Posts: 5,196
I am not sure where the timestamp would be for a stored procudure (it might be the create timestamp), but you can see the timestamp of the package.

The first thing I would do is to rebind the stored procedure packages. If that does not work, then try to drop and recreate the stored procedures on the new server.
__________________
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On