| |
- Causa
- 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
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.
Note: 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.
- Ação do sistema
- The statement cannot be executed. The application is rolled back to the previous COMMIT.
- Resposta ao Desenvolvedor
- 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.
For more information about how IMS, CICS, and TSO handle deadlocks, see Part 4 of DB2 Application Programming and
SQL Guide.
SQLSTATE: 40001
© Copyright IBM Corp.
|
| |
