logo  
Google
 

DB2 SQL-Error: -913

SQLState: 57033

Short Description: UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT REASON CODE TYPE OF RESOURCE AND RESOURCE NAME

The application was the victim in a deadlock or experienced a timeout. The reason code indicates 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. System action: The SQL statement cannot be executed. If the SQL statement being executed was a cursor FETCH, DB2 closes the cursor. 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 - timeoutProgrammer response: The application should either commit or roll back to the previous COMMIT. Then, generally, the application should terminate. See message DSNT376I for possible ways to avoid future deadlocks or timeouts. For more information about how CICS and TSO handle deadlocks, see Part 4 of DB2 Application Programming and SQL Guide.

 <-  BACK TO INDEX