DB2 SQL-Error: -880
SQLState: 08003
Short Description: SAVEPOINT DOES NOT EXIST OR IS INVALID IN THIS CONTEXT A SAVEPOINT WITH NAME ALREADY EXISTS BUT THIS SAVEPOINT NAME CANNOT BE REUSED SAVEPOINT DOES NOT EXIST THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE APPLICATION PROCESS IS NOT CONNECTED TO AN APPLICATION SERVER C E SQL P I I F CONNECT C DB SQL R
The RELEASE TO SAVEPOINT or ROLLBACK TO SAVEPOINT statement does not identify a savepoint that exists. System action: DB2 does not process the statement. Programmer response: Correct the statement to use a valid savepoint name. SQLSTATE: 3B001 Explanation: The SAVEPOINT statement uses the same savepoint name as another savepoint, and it cannot be created because at least one of the savepoints was defined with the UNIQUE clause to indicate that the name cannot be reused within the transaction. System action: The statement is not executed and a new savepoint is not set. The old savepoint still exists. Programmer response: Correct the statement. Either use a different savepoint name, or omit the UNIQUE clause if the other savepoint was created without the UNIQUE clause and your intention is to reuse that savepoint name. SQLSTATE: 3B501 Explanation: A ROLLBACK TO SAVEPOINT statement was specified without a savepoint name to rollback to the last active savepoint, but no savepoint exists. System action: The statement is not executed. Programmer response: Correct the application logic to either set a savepoint or to not attempt to rollback to a savepoint. SQLSTATE: 3B502 Explanation: A previous failure has placed the application process in the unconnected state. The only SQL statements that can be successfully executed from the unconnected state are CONNECT, COMMIT, ROLLBACK, and local SET statements. System action: The statement cannot be executed.