KB441941: Report execution fails due to the error “ROLLBACK DUE TO DEADLOCK/TIMEOUT; REASON 68” in MicroStrategy Secure Enterprise 2020 and above

SYMPTOMS

When the data warehouse is hosted on DB2, report execution fails and the DSSErrors.log captures the following error

[Database Classes][Error] Fetch failed.Error type: Odbc error. Odbc operation attempted: SQLExtendedFetch. [01S01:0: on HSTMT] [Strategy][ODBC DB2 Wire Protocol driver]Error in row. For more information, please consult DB2 document for error code SQL00. [01S01:0: on HSTMT] [Strategy][ODBC DB2 Wire Protocol driver]Error in row. [S1000:1210: on HSTMT] [Strategy][ODBC DB2 Wire Protocol driver]Abnormal end unit of work condition occurred. [40001:-911: on HSTMT] [Strategy][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]ROLLBACK DUE TO DEADLOCK/TIMEOUT;  REASON 68. [S1000:8301: on HSTMT] [Strategy][ODBC DB2 Wire Protocol driver]Cursor identified in Fetch statement is not open. It could have been closed by a previous commit or rollback. Connection String: DSN=xxx;UID=yyy;IPADDRESS=xx.xx.xx.xx;TCPPORT=51940;DATABASE=xyz;. SQL Statement: with  gopa1 as...

 

CAUSE

The following snippet of the above error describes the root cause of the error.

[40001:-911: on HSTMT] [Strategy][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]
ROLLBACK DUE TO DEADLOCK/TIMEOUT;  REASON 68

The error code -911 means "The current unit of work was the victim in a deadlock, or experienced a timeout, and had to be rolled back. The reason code indicated whether a deadlock or
timeout occurred" per http://publib.boulder.ibm.com/epubs/pdf/dsnc1k17.pdf
The reason code is 68 in this case, which means "transaction rolled back due to lock timeout". This implies that a database-side governing setting has been reached. Most likely, the database configuration parameter LOCKTIMEOUT is set too low.
 

ACTION

Consult with a database administrator with regards to the details of the error and actions to take.