Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

SQLCODE is -818, table name is SYSIBM.SYSDUMMY1

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2
View previous topic :: :: View next topic  
Author Message
Robelis

New User


Joined: 15 Jul 2006
Posts: 1

PostPosted: Sat Jul 15, 2006 1:46 am    Post subject: SQLCODE is -818, table name is SYSIBM.SYSDUMMY1
Reply with quote

I'm having this problem in database, and because this, the Dprop is stoping the propagate.
I did the bind but don't solved this problem.

Please, help me!Thx

Follow the logs of dprop (Capture and Apply):

2006-07-14-16:38:46 ASN1001E: The Apply program encountered an SQL error.
ERRCODE is 0A0101, SQLSTATE is 51003, SQLCODE is -818, SQLERRM is , SQLERRP is SQLRALDP, server name is LNOVODBS, table name is SYSIBM.SYSDUMMY1.
2006-07-14-16:38:46 ASN1097I: The Apply program stopped due to the above error.

trace file name is D:\Replication\PH2QUAL.TRC
Apply program compiled at 11:06:15 on Oct 1 2004 (Level 70114z_FP13)
SQLCA is
00000000 53514C43 41202020 88000000 CEFCFFFF SQLCA ....????
00000010 00002020 20202020 20202020 20202020 ..
00000020 20202020 20202020 20202020 20202020
00000030 20202020 20202020 20202020 20202020
00000040 20202020 20202020 20202020 20202020
00000050 20202020 20202020 53514C52 414C4450 SQLRALDP
00000060 7E87FFFF 00000000 00000000 00000000 ..??............
00000070 00000000 00000000 20202020 20202020 ........
00000080 20202035 31303033 51003
*** SQL ERROR ***: SQL0818N A timestamp conflict occurred. SQLSTATE=51003

CGCT: Prepare failed. errcode is 0A0101. sqlstate is 51003. sqlcode is -818
--------------------------------
Global control record not found.
GCST: get control server timestamp failed. errcode is 0A0101.
--------------------------------
Global control record not found.
GCST: Apply is shutting down.
Back to top
View user's profile Send private message

DavidatK

Active Member


Joined: 22 Nov 2005
Posts: 700
Location: Troy, Michigan USA

PostPosted: Sat Jul 15, 2006 2:43 am    Post subject: Re: SQLCODE is -818, table name is SYSIBM.SYSDUMMY1
Reply with quote

A -818 says that the Program Load Module used in the bind is different than the one being executed.

Make sure you are using the same module to execute as used in the bind.

Dave
Back to top
View user's profile Send private message
senthilssg

New User


Joined: 09 Dec 2005
Posts: 64
Location: USA

PostPosted: Sun Jul 16, 2006 4:09 pm    Post subject: Re: SQLCODE is -818, table name is SYSIBM.SYSDUMMY1
Reply with quote

Hi ,


Quote:
-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:

 Precompile, compile, and link, without doing a BIND of the application,
 Precompile and BIND, without doing the compile and link for the application program, or
 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.

SQLSTATE: 51003



Please bind your dbrm once again after that try to run the program

Regards
Senthil
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2 All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Loading data to table gives wrong for... Raghu navaikulam DB2 19 Thu Jul 13, 2017 2:11 pm
No new posts unload data from table with lob columns farhad_evan DB2 1 Sat Apr 22, 2017 1:32 pm
No new posts Data replication from multiple Db2 ta... kishpra DB2 9 Mon Mar 27, 2017 9:58 pm
No new posts how to send just 10 rows in a CICS sc... Megha Gupta CICS 5 Thu Feb 23, 2017 6:57 pm
No new posts DB2 SQL Error: SQLCODE=-440, SQLSTATE... kishpra DB2 1 Sat Feb 18, 2017 2:31 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us