DBA DB2:Everything
DBA Scripts

Search dba-db2.com

Follow dba-db2.com

*Use the Comments section for questions

Daily & Exclusive Content

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

01 May,2012 by Tom Collins

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: Rambler(http://www.dba-db2.com)

Share:

Posted by Tom Collins at 4:00 AM in Backup & Restore, DB2 error tips, Deadlocks, Troubleshooting | Permalink | Comments (2) | TrackBack (0)

Searches: db2 backup database, db2 locktimeout, db2 sql0911n, sql0911n 68

HI,

We are facing deadlock issue in DB2. This is happening when we are reading the data through application. We have tried all posible options available for isolation levels and also the configurations provided by DB2 blogs. If require we can send the trace logs of dead lock. Kindly suggest what need to be done.

Posted by: Subramanyam S.g | Apr 13, 2015 11:52:24 PM

Hi, have you tried a deadlock event monitor? This will give you details about the specific deadlock members - Read here on how to set up http://www.dba-db2.com/2012/06/how-to-monitor-a-deadlock-in-db2.html

Posted by: Jack Vamvas | Apr 14, 2015 11:40:22 AM

Verify your Comment

Previewing your Comment

Posted by: |

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

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.