Results 1 to 4 of 4
  1. #1
    Join Date
    Apr 2004
    Posts
    58

    Lightbulb Unanswered: 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.

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    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

  3. #3
    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?

  4. #4
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    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

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •