Here are some easy ways to fix error 913 in DB2.
-913 UNSUCCESSFUL OPERATION DUE TO BLOCKING TIME OR EXTINGUISHING TIME. BASE CODE, reason code, resource type RESOURCE TYPE AND resource name RESOURCE NAME.
Loading Ã— Sorry to interrupt
Short Description: SUCCESSFUL EXECUTION WITH A DELAY OR TYPE OF INTERFERENCE WITH THE MAIN RESOURCE AND THE RESOURCE NAME
The application has crashed or timed out. The reason code indicates whether a deadlock or timeout occurred. See Message DSNT500I under DB2 Messages for an explanation of “Resource Type” and “Resource Name”. See Table 3 in Appendix C, “Troubleshooting,” on page 757 for an explanation of the resource type codes. System Action: The SQL statement cannot be executed. If the SQL statement executed was a FETCH cursor, DB2 closes the cursor. SQLERRD (3) also contains a reason code indicating whether a deadlock or timeout occurred. The most common reason codes are: v 00C90088 – Lock v 00C9008E – timeout Programmer response: the application must either confirm or return to the previous COMMIT. Then the application should normally close. See Post DSNT376I for possible ways to avoid future deadlocks or timeouts. For more information on how CICS and TSO handle deadlocks, seePart 4 of the SQL and Programming Guide for DB2 Applications.
Make the following local change:
- Disable the PersistSystemInfo agent in the agent schedule for each node.
- Cut or delete data in .pr_log_systemstate.