DB2 Server for VM: Messages and Codes
When limit errors are detected, message ARI0039E is issued. The text
of the message is:
| ARI0039E | Application server
limit error occurred - ARIxxxx nn
|
Explanation: The following are the conditions that cause the message to be issued where
ARIxxxx nn is:
- ARICCRA nn
- (See note 1.)
- 01
- Get working storage error (DSCAREA)
- 02
- Get working storage error (YTABLE1)
- 04
- Get working storage error (SCANS)
- 06
- Working storage initialization error (DSCAREA)
- 07
- Get working storage error (ARIYMBB)
- 08
- Get working storage error (Communication Manager Parameter List)
- 09
- Get working storage error (OMB Parameter List)
- 10
- Get working storage error (RDAREA)
- 11
- Get working storage error (SQLCA)
- 12
- Get working storage error (TBASE)
- 14
- Get working storage error (RI area)
- 15
- Get working storage error (default input buffer)
- 16
- Get working storage error (default output mailbox buffer)
- 17
- Get working storage error (Parser)
- 18
- Get working storage error (Generator)
- 19
- Get working storage error (Conversion)
- 20
- Get working storage error (DRRMSTR)
- 21
- Get working storage error (DCAREA)
- 22
- Get working storage error (ASPAREA)
- 25
- Get working storage error (TRANS)
- 26
- Get working storage error (PCAREA)
- ARICDSP nn
-
- 03
- All agents waiting for buffers, and SQL is out of page buffers
- ARICEXP nn
- (See note 1.)
- 01
- Insufficient storage
- 02
- Insufficient storage
- ARICIP2 nn
- (See note 1.)
- 13
- Get working storage error (translation table)
- ARICIP3 nn
- (See note 1.)
- 15
- Error loading program ARIGCAT or ARISEGB (not enough virtual storage or
program not found)
- 18
- Error loading the user application program in single user mode (not enough
virtual storage or program not found)
- 19
- Error loading the program. The application program was loaded above
the 16MB line in single user mode when the database manager was running AMODE
24. See message ARI0021E for corrective action.
- ARICIPB nn
- (See note 1.)
- 01
- Working storage initialization error (DSCAREAP)
- 02
- Get working storage error (WAITM Table)
- 03
- Get working storage error (DCES)
- 04
- Get below working storage error (HSDS, CID)
- 05
- Get below working storage error (TRACE FDESC)
- 06
- Get working storage error (GLOBAL Tables)
- 10
- Get working storage error (Communication Block Queue Elements and
VMCBLOCKs)
- 14
- Get working storage error (Communication Block Queue Header)
- 17
- Get below working storage error (WAITECB Parameter List)
- 19
- Get working storage error (accounting records)
- 21
- Get working storage error (Guest in-doubt list)
- 22
- Get working storage error (Accounting storage queue header)
- 23
- Get working storage error (Transproc control)
- 31
- Get working storage error (Accounting record write buffer)
- ARICJAC nn
- (See note 1.)
- 01
- Get working storage error (Accounting records)
- ARICSHO nn
- (See note 1.)
- 01
- Insufficient storage
- 02
- Insufficient storage
- ARICSTK nn
- (See note 1.)
- 01
- Not enough virtual storage to allocate DB2 Server for VM stack storage for
agents
- ARISDBR nn
- (See note 1.)
- 01
- Not enough virtual storage for database generation value table
- 02
- Not enough virtual storage for database generation input file control
block
- ARISDSK nn
- (See note 1.)
- 01
- Insufficient storage
- 02
- Insufficient storage
- ARISFDB nn
- (See note 1.)
- 01
- Not enough virtual storage for loading directory block during database
generation
- ARISFMG nn
- (See note 1.)
- 01
- Insufficient storage
- 13
- Insufficient storage
- ARISFM1 nn
- (See note 1.)
- 01
- Not enough virtual storage for input/output buffer to format database
files
- 02
- Not enough virtual storage for VMCBLOCK to format database files
- 03
- Same as 02
- 04
- Same as 02
- ARISIIO nn
- (See note 1.)
- 01
- Not enough virtual storage for directory file buffer during database
generation
- 03
- Not enough virtual storage for directory file blocks during database
generation
- 04
- Same as 03
- 05
- Same as 03
- 06
- Same as 03
- 07
- Same as 03
- 08
- Same as 03
- 09
- Same as 03
- 10
- Same as 03
- ARISRMG nn
- (See note 1.)
- 01
- Insufficient storage
- 10
- Insufficient storage
- ARISUXP nn
-
- 16
- DASD storage assigned to the storage pool is full (See message ARI0201E)
- ARIXERO nn
- (See note 1.)
- 13
- No working storage
- 21
- Same as 13
- 22
- Same as 13
- 23
- Same as 13
- ARIYC11 nn
- (See note 1.)
- 09
- Not enough virtual storage for log buffer
- 13
- Same as 09
- 17
- Not enough virtual storage for log information
- 24
- Same as 17
- 27
- Same as 09
- 30
- Same as 17
- 35
- Not enough virtual storage for log record
- 52
- Same as 17
- 58
- Not enough virtual storage for log
- ARIYD48 nn
-
- 12
- DASD storage assigned to the storage pool is full (See message ARI0201E)
- 13
- DASD storage assigned to the storage pool is full (See message ARI0201E)
- ARIYD69 nn
- (See note 1.)
- 01
- Request for working storage for building new row during row update
recovery (UNDO/BACKUP or REDO) failed
- 02
- Same as 01
- 05
- Same as 01
- ARIYD81 nn
- (See note 1.)
- 06
- Request for working storage to assemble data manipulation call parameter
values for DBSS entry or exit level 2 trace output failed
- 07
- Same as 06
- 08
- Same as 06
- 09
- Same as 06
- 10
- Same as 06
- ARIYI14 nn
-
- 01
- Directory buffer pool is exhausted (NDIRBUF parameter) (See message
ARI0203E)
- ARIYI19 nn
-
- 01
- Page buffer pool is exhausted (NPAGBUF parameter) (See message ARI0203E)
- ARIYI22 nn
- (See note 1.)
- 03
- Not enough storage to allocate VMCBLOCKs for database files
- 04
- Not enough storage to allocate VMCBLOCK pointer array for database files
- 06
- Same as 03
- 07
- Same as 04
- 08
- Same as 03
- 09
- Not enough storage to allocate VMQ pointer array for database files
- 16
- Get working storage error (EXTMAP)
- ARIYI29 nn
-
- 01
- DASD storage assigned to the storage pool is full (See message ARI0201E)
- 02
- DASD storage assigned to the storage pool is full (See message ARI0201E)
- ARIYI36 nn
- (See note 1.)
- 02
- Not enough storage to allocate bit map table for DBSPACE directory file
allocation blocks
- ARIYI63 nn
-
- 01
- Invalid entities table is in new format. The directory must be
reset, but there are either transient or invalid indexes.
- ARIYI66 nn
- (See note 1.)
- 03
- Get working storage error (DS2MOD)
- ARIYI68 nn
- (See note 1.)
- 02
- Get working storage error (DS2MOD)
- ARIYI70 nn
- (See note 1.)
- 01
- Get working storage error (YDATSPC)
- ARIYI71 nn
- (See note 1.)
- 01
- Get working storage error (YDBSPMAP)
- 02
- Get working storage error (YDATSPC)
- 03
- Get working storage error (YDATSPC)
- ARIYI72 nn
- (See note 1.)
- 01
- Get working storage error (YPOOLMAP)
- ARIYI73 nn
- (See note 1.)
- 01
- Get working storage error (XLD block)
- 02
- Get working storage error (XLD block)
- ARIYI74 nn
-
- 01
- |XCONFIG ADDRspace VM directory limit reached, update the VM
|directory XCONFIG ADDRspace statement
- 02
- |XCONFIG ACCEsslist VM directory limit reached, update the VM
|directory XCONFIG ACCEsslist statement
- 03
- Get working storage error (DSMAP) (See note 1.)
- ARIYI84 nn
- (See note 1.)
- 01
- Get working storage error (SLD blocks)
- 02
- Get working storage error (MLD blocks)
- ARIYK12 nn
- (See note 1.)
- 03
- Not enough storage for deadlock cycle tables
- 04
- Same as 03
- 05
- Same as 03
- ARIYK30 nn
- (See note 1.)
- 01
- Get working storage error (Lock List)
- ARIYK41 nn
-
- 01
- No more LRBs available
- ARIYK53 nn
- (See note 1.)
- 01
- Not enough virtual storage space for SHOW LOCK WANTLOCK command
processing.
Insufficient storage for stack storage.
- ARIYK54 nn
- (See note 1.)
- 01
- Not enough virtual storage for SHOW LOCK USER command processing
- ARIYK55 nn
- (See note 1.)
- 01
- Not enough virtual storage for SHOW LOCK DBSPACE command processing
- ARIYK56 nn
- (See note 1.)
- 01
- Not enough virtual storage for SHOW LOCK ACTIVE command processing
- 04
- Same as 01
- ARIYK57 nn
- (See note 1.)
- 01
- Not enough virtual storage for SHOW LOCK GRAPH command processing
- 04
- Same as 01
- ARIYL00 nn
- (See note 1.)
- 04
- Number of log pages exceeds limit. (Note 1 does not apply to this
limit error.)
- 50
- Insufficient storage for checkpoint record
- 51
- Insufficient storage for checkpoint record
- 52
- Insufficient storage for log page
- 54
- Insufficient storage for checkpoint record
- 55
- Insufficient storage for log page
- ARIYL01 nn
-
- 05
- Database manager log file is full (See message ARI0276E)
- ARIYL08 nn
- (See note 1.)
- 01
- Not enough virtual storage for checkpoint record
- ARIYL09 nn
- (See note 1.)
- 60
- Insufficient storage for checkpoint record
- 65
- Insufficient storage for checkpoint record
- ARIYL14 nn
- (See note 1.)
- 08
- Insufficient storage for checkpoint record
- ARIYL17 nn
- (See note 1.)
- 01
- Get working storage error (File Descriptor Block)
- 04
- Same as 01
- ARIYL18 nn
- (See note 1.)
- 01
- Get working storage error (File Descriptor Block)
- 15
- Same as 01
- ARIYL19 nn
- (See note 1.)
- 02
- Get working storage error
- 04
- Get working storage error
- ARIYL21 nn
- (See note 1.)
- 01
- Not enough virtual storage for restore buffer
- 15
- Not enough virtual storage for file descriptor block
- ARIYL23 nn
- (See note 1.)
- 01
- Not enough virtual storage for archive buffer
- 15
- Not enough virtual storage for archive file descriptor block
- ARIYS08 nn
- (See note 1.)
- 02
- Sort REDO/UNDO - not enough virtual storage for log record
- ARIYT00 nn
-
- 08
- Get working storage error (Counter Internal Structure)
- 09
- Get working storage error (Counter Pool Structure)
- ARIYT29 nn
-
- 01
- Not enough agents specified (NCUSERS parameter) (See message ARI0231E)
- ARIYX02 nn
-
- 21
- DASD storage assigned to the storage pool is full (see message ARI0201E)
or internal DBSPACE is full
- ARIYX04 nn
-
- 06
- Create index - not enough virtual storage for sort base
- ARIYX09 nn
-
- 04
- Get working storage error (See note 1.)
- 05
- The index was at the maximum of eight levels, and the insert would have
caused the index to expand to a ninth level.
- ARIYX29 nn
-
- 15
- The index was at the maximum of eight levels, and the INSERT would have
caused the index to expand to a ninth level.
- ARIYX36 nn
-
- 01
- An attempt was made to mark an entity invalid but there are already 16
invalid entities.
- 04
- More entries in the YINVALID table than the maximum number allowed.
- ARIYZ00 nn
- (See note 1.)
- 02
- Insufficient storage
- 03
- Insufficient storage
- 05
- Insufficient storage
- 09
- Insufficient storage (TABSTAT)
| Note: | Note 1These limit errors are caused by insufficient virtual storage.
See message ARI0059E for corrective action.
|
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]