logo  
Google
 

DB2 SQL-Error: -911

SQLState: 40001

Short Description: THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO DEADLOCK OR TIMEOUT REASON TYPE OF RESOURCE AND RESOURCE NAME SQLCODE F IMS CICS TSO P DB A P SQL G

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. Refer to message DSNT500I under DB2 Messages for an explanation of 'resource-type' and 'resource-name'. Refer to Table 3 in Appendix C, “Problem determination,” on page 757 for an explanation of resource type codes. Attention: The changes associated with the unit of work must be entered again. SQLERRD(3) also contains the reason-code which indicates whether a deadlock or timeout occurred. The most common reason codes are: v 00C90088 - deadlock v 00C9008E - timeoutThe changes associated with the unit of work must be entered again. System action: The statement cannot be executed. The application is rolled back to the previous COMMIT. Programmer response: A long-running application, or an application that is likely to encounter a deadlock, should (if possible) issue frequent COMMIT commands. This can lessen the possibility of a deadlock occurring. See message DSNT376I for other possible ways to avoid future deadlocks or timeouts. On receipt

 <-  BACK TO INDEX