DB2 Server for VSE: Messages and Codes
When a system error is detected, message ARI0040E is issued. The
text of the message is:
| ARI0040E | A database manager
system error occurred - ARIxxxx nn
|
Explanation: Communication Link error conditions may have caused the message to be
issued. Communication Link errors are VSE XPCC errors. The
reason code (message ARI0042I) contains the system return code.
When any of these situations occurs, contact the designated support group
for your installation.
Some of the error messages are shown below. ARIxxxx nn in the
message is equal to:
- ARICCLA nn
-
- 01
- Communication Link error - DISCONNECT
- ARICDSP nn
-
- 01
- Communication Link error - READY/RECOVERY AGENT (Reason code of less than
5 is not valid.)
- ARICENA nn
-
- 01
- Communication Link error - CONNECT
- ARICIP2 nn
-
- 01
- Communication Link error - SUBSID
- 02
- Communication Link error - IDENTIFY (General Purpose)
- 03
- Communication Link error - IDENTIFY (INDOUBT)
- 06
- Communication Link error - IDENTIFY (READY/RECOVERY)
- ARICJACC
- The following new SYSTERR codes may be set:
- 01
- Get working error or no storage for accounting queue entry or on-line
accounting records
- 03
- Cannot find the accounting queue entry for the on-line user
- 04
- Cannot find the accounting queue entry for the on-line user being at End
Of Transaction
- ARICMUD nn
-
- 03
- Communication Link error - RECEIVE
- 05
- Communication Link error - PURGE
- ARICMUDC
- The following new SYSTERR codes may be set:
- 07
- Error freeing prereceive buffer
- 08
- Error freeing input mailbox buffer
- ARICOMB nn
-
- 01
- Communication Link error - REPLY
- 02
- Same as 01
- ARICSHT nn
-
- 01
- Communication Link error - TERMQSCE (READY/RECOVERY)
- 02
- Communication Link error - TERMQSCE (General)
- 03
- Communication Link error - TERMQSCE (INDOUBT)
- ARISIIO nn
-
- 05
- The database directory has not been properly restored.
- ARIYC25 nn
-
- 09
- The DB2 Server for VSE system was rolling back the drop index
operation. Message ARI00421 contains the DBSS Return Code. Refer
to Chapter 16, DBSS Return Codes for these codes.
- ARIYD77 nn
-
- 08
- During recovery, an entry was found in the log for a delete, shorten, or
update of a tuple, and the tuple does not exist in the database. You
will need to use filtered log recovery to BYPASS or ROLLBACK this LUW.
- ARIYI01 NN
-
- 05
- During an archive, a DB2 Server for VSE system disk (directory, log or
data disk) was defined in VSAM with SHAREOPTIONS(1). The SHAREOPTIONS
will need to be set to 2, and the archive must be redone.
- ARIYL00 nn
-
- 62
- During warmstart, ARIYL00 tries to read the checkpoint record from the log
and does not find a checkpoint at the address pointed to by the
directory.
- 87
- Performing a restore, the log disk is checked to find the last checkpoint
that occurred before the restore (to determine whether the current log needs
to be archived). This error occurs when the record pointed to (by the
LOGCID)is not a checkpoint.
- ARIYL26 nn
-
- 09
- During a startup of the application server, ARIYL26 scans the logs for the
HSDS (history area) of the logs and there are no HSDS records in the
logs. You may have done a VSAM delete and define of the log
extents. Perform a coldlog and take a new database archive immediately
after performing the coldlog. The coldlog will write the HSDS record to
the log.
- ARIYX29 nn
-
- 04
- Not enough index pages in the dbspace to accomplish the INSERT
- 16
- Not enough index pages in the dbspace to accomplish the INSERT
| NOTE 1 |
|---|
|
Other situations can occur where message ARI0040E is
issued. When any of these situations occurs, make a record of what
went wrong and contact the designated support group for your
installation. |
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]