View previous topic :: View next topic
|
Author |
Message |
mailsaurabh.tripathi
New User
Joined: 22 May 2008 Posts: 56 Location: hyderabad
|
|
|
|
i got the following msg......olz help how to pin point the problem, and how to get rid of it...plz provide the steps you used to identify the problem, and steps to remove it. If possible in an elaborate way.
+*********************************************************************
+* ISM603P STEP001 ISM9090 RETURN CODE = 16.
+ DSNT408I SQLCODE = -911, ERROR: THE CURRENT UNIT OF WORK HAS BEEN
+ ROLLED BACK DUE TO DEADLOCK OR TIMEOUT. REASON 00C9008E, TYPE
+ OF RESOURCE 00000D01, AND RESOURCE NAME 00000323.00000130
+ DSNT418I SQLSTATE = 40001 SQLSTATE RETURN CODE
+ DSNT415I SQLERRP = DSNXRFF SQL PROCEDURE DETECTING ERROR
+ DSNT416I SQLERRD = -115 13172746 13172878 13226969 -1026420731
+ 536870912 SQL DIAGNOSTIC INFORMATION
+ DSNT416I SQLERRD = X'FFFFFF8D' X'00C9000A' X'00C9008E'
+ X'00C9D3D9' X'C2D21005' X'20000000' SQL DIAGNOSTIC
+ INFORMATION
Thank You
Regards |
|
Back to top |
|
|
ntmartins
New User
Joined: 03 Mar 2008 Posts: 11 Location: Lisboa, Portugal
|
|
|
|
Someone or something is locking the table you're trying to access.
If you have any DB2 tool it can tell what is locking the table.
Another way is looking into system log. It shoul say who is locking the table. |
|
Back to top |
|
|
Raghu navaikulam
Active User
Joined: 27 Sep 2008 Posts: 193 Location: chennai
|
|
|
|
Hi
Your problem is Timeout. This problem can be caused by many factors like locksize, lock escalation, isolation level, NUMLUKS, acquire and release parameters. In the error message you can see the DBID and OBID(00000323.00000130 ). Check the particular tablespace to see how the locksize is specifies and also check the acquire and release parameter (BIND).
Hope this may help u
Regards
Raghu |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19243 Location: Inside the Matrix
|
|
|
|
Hello,
Keep in mind that the problem is the "other" task - not the one that raised the -911.
Often code is implemented that reads rows for update when it is not necessary. Sometimes a is lock is acquired at the start of a long-running process and is not released until the end - causing this kind of problem for other processes. |
|
Back to top |
|
|
|