SQL0911N Reason Code 68 The current transaction has been rolled back because of a deadlock or timeout

01 May,2012 by Jack Vamvas

Question : I am seeing this SQL0911N Reason Code 68 message in my DB2 diaglog file:

command : db2 backup db MYDB online use TSM include logs
SQL0911N  The current transaction has been rolled back because of a deadlock
or timeout.  Reason code "68".  SQLSTATE=40001

 

How do I fix this SQL0911N error?

 

Answer: The DB2  command line error utility  shows this detailfor  the SQL0911N Reason Code 68 error., indicating that the SQL0911N error is caused by a deadlock or locktimeout.

A DB2  ONLINE backup attempts to obtain a IN lock on tables in SMS table spaces. DB2 tries to upgrade BLOB fileds to an S LOCK during an ONLINE backup.

 If an application is holding a lock incompatible with the ONLINE backup lock attempt, The ONLINE BACKUP waits for the period of the LOCKTIMEOUT ,  where the ONLINE backup fails.

Possible solutions for SQL0911N  Reason Code 68

1)       Analyse scheduled backup times and move to a quieter time frame

2)       Change table space to DMS from SMS. DMS doesn’t require the SHARE lock for BLOBs

3)       Force the application off.

4)       Increase LOCKTIMEOUT

Read More on DB2 deadlocks

How to monitor a deadlock in DB2 - DBA DB2

DB2 - Drop the DB2DETAILDEADLOCK event monitor

Author: Jack Vamvas(http://www.dba-db2.com)

Share:

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment on SQL0911N Reason Code 68 The current transaction has been rolled back because of a deadlock or timeout

Comments are moderated, and will not appear until the author has approved them.


dba-db2.com | DB2 Performance Tuning | DBA DB2:Everything | FAQ | Contact | Copyright