THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO DEADLOCK OR TIMEOUT. REASON reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name
Explanation
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. For an explanation of resource type codes, see Resource types.
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:
00C90088 – deadlock
00C9008E – timeout
The changes associated with the unit of work must be entered again.
System action
The statement cannot be processed. 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 of the SQLCODE -911, the application should, in general, terminate.
SQLSTATE
40001
https://www.ibm.com/support/knowledgecenter/en/SSEPEK_10.0.0/codes/src/tpc/n911.html
——————————————————————————————————–
If you would like to Earn Free Stocks, Credit card Points and Bank account Bonuses, Please visit My Finance Blog
——————————————————————————————————–
You may also like to look at:
F1 for Mainframe 