Observation manager and Replication manager might cause a deadlock exception

The trace for some exceptions might has the following line: Caused by: com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -911, SQLSTATE: 40001, SQLERRMC: 2

Both the Observation manager and the Replication manager components access the same database tables, and this occasionally causes a deadlock problem. The deadlock exception is thrown in the WebSphere® Application Server SystemOut.log file. If the exception has in its trace

Caused by: com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -911, SQLSTATE: 40001, SQLERRMC: 2

Then the SQL code -911 indicates that this is a deadlock problem.

The exception is totally recoverable when either of the components, Observation manager or the Replication manager, finishes its transaction.


Copyright IBM Corporation 2005, 2006. All Rights Reserved.