Ansicht
Dokumentation

SQL0595 - Commit level *&1 escalated to *&2 lock. ( OS/400 )

ABAP Short Reference   ABAP Short Reference  
This documentation is copyright by IBM.


Message : SQL0595
Commit level *&1 escalated to *&2 lock.

Message Long Text :

Cause . . . . . : *&1 was specified for the commit level, but *&1 was not used. The base tables were locked *&2 to satisfy the request for commitment level of *&1. If a ROLLBACK HOLD statement is requested, the cursor will remain in the same position.
*&1 was not used for one of the following reasons:
-- A GROUP BY clause, HAVING clause, or an aggregate function was specified in the statement.
-- A DISTINCT keyword was specified in the statement.
-- A UNION keyword was specified in the statement.
-- A join was specified in the statement, but not all of the tables are journaled to the same journal.
-- The repeatable read commit level is implemented by DB2 for IBM i by locking the table.
Recovery . . . : If escalation of commit level is not desired, change the statement or the requested commit level. If a lock level of share-no-update (*SHRNUP) was granted, but is not acceptable, specify *CHG or *NONE for the commit level.

Message File : QSQLMSG
Library Message File : QSYS2924


CPI1466 during Backup   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by IBM.

Length: 3233 Date: 20240423 Time: 081923     sap01-206 ( 3 ms )