00C90092
Explanation
DB2® received an out-of-storage indication from IRLM resulting from a lock, unlock, or lock change request.
System action
A record is written to SYS1.LOGREC only when an abend is issued. No dump is requested.
Operator response
Notify the system programmer.
System programmer response
IRLM has exhausted the amount of virtual storage available to it to represent locks. Insufficient virtual storage remains to satisfy this request. You can use the IRLM startup procedure to determine the amount of storage space available.
The current mix of transactions caused all available storage to be used. You can find the number of locks held by a particular transaction by either using the DB2 performance trace facility or by performing IRLM tracing.
Determine what transactions were running and the number of locks they held. You might want to schedule some of these transactions at a different time.
- ALTER TABLESPACE...LOCKSIZE ANY
- ALTER TABLESPACE...LOCKSIZE TABLESPACE
- LOCK TABLE
If application logic permits, reduce the number of page or row locks concurrently held for SELECT statements by re-binding application plans with isolation level of cursor stability instead of repeatable read or read stability.
- ALTER TABLESPACE...LOCKSIZE TABLESPACE
- LOCK TABLE statement
Problem determination
- An SQLCODE -904 or -923
- Message DSNT501I
- An abend
SYS1.LOGREC contains information in the variable recording area (VRA) of the system diagnostic work area (SDWA). Significant fields for this code are: VRARRK13, VRARRK14, and VRARRK15. If you suspect an error in DB2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.
- Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
- SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump command or SLIP trap exit.
- Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.
- IRLM trace output.
- SYSPRINT output, including JCL, for the application program or batch job, and system messages that were issued. Make sure that MSGLEVEL=(1,1) on the JOB statement so that all diagnostic information is sent to SYSPRINT.
- Definitions of views and tables involved in the error.
- Listing of the IRLM procedure.