View previous topic :: View next topic
|
Author |
Message |
sabyasachi
New User
Joined: 31 Aug 2006 Posts: 3
|
|
|
|
How to solve -818 error? |
|
Back to top |
|
|
Gnanas N
Active Member
Joined: 06 Sep 2007 Posts: 792 Location: Chennai, India
|
|
|
|
-818
Timestamp mismatch error.
Read the manual for details. |
|
Back to top |
|
|
vicky10001 Warnings : 1 Active User
Joined: 13 Jul 2005 Posts: 136
|
|
|
|
-818
-818 THE PRECOMPILER-GENERATED TIMESTAMP x IN THE LOAD MODULE IS
DIFFERENT FROM THE BIND TIMESTAMP y BUILT FROM THE DBRM z
Explanation: The SQL precompiler places timestamp 'y' in the DBRM, and
time stamp 'x' in the parameter list in the application program for each
SQL statement. At BIND time, DB2 stores the DBRM timestamp for run-time
use. At run-time, timestamp 'x', for the SQL statement being processed, is
compared with timestamp 'y' derived from the DBRM 'z' at BIND time. If the
two timestamps do not match, the DBRM and the application program were not
the result of the same precompile.
This problem can occur if you:
o Precompile, compile, and link, without doing a BIND of the
application,
o Precompile and BIND, without doing the compile and link for the
application program, or
o BIND the application using a DBRM that resulted from a different
precompile of the application program than that which produced the
object module that is linked into the application module.
The timestamps 'x' and 'y' are DB2 internal timestamps. They do not have
an external interpretation.
System Action: The statement cannot be executed.
Programmer Response: BIND the application again, using the DBRM for the
application program that matches the object module. |
|
Back to top |
|
|
sabyasachi
New User
Joined: 31 Aug 2006 Posts: 3
|
|
|
|
ok, the reply is well n good. |
|
Back to top |
|
|
|