DB2 Server for VM: Messages and Codes


Chapter 26. System Errors


When a system error is detected, message ARI0040E is issued. The text of the message is:

ARI0040EA database manager system error occurred - ARIxxxx nn

Explanation: Communication Link error conditions may have caused the message to be issued. Communication Link errors are VM IUCV 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

ARICINT nn

01
No available pseudo agents

02
Communication Link error - SEVER

03
Communication Link error - ACCEPT

04
Same as 02

05
Communication Link error - Unknown interrupt type. The reason code (message ARI0042I) will contain the invalid interrupt type code.

06
Same as 05

07
Same as 02

08
Same as 02

09
Same as 05

ARICINTC ABEND CODE 251

11
Get storage error when acquiring the prereceive buffer

12
Severe communication error when prereceiving a message

13
Free storage error when returning the prereceive buffer

ARICIP1 nn

12
Communication Link error - IUCV HNDIUCV SET error

13
Communication Link error - IUCV SETCMASK error

ARICIP2 nn

08
Communication Link error - IUCV SETCMASK error

ARICJAC
The following SYSTERR code may be set:

03
Cannot find the accounting queue entry for the on-line user

ARICMUD nn

03
Communication Link error - RECEIVE

05
Communication Link error - REJECT

07
Error freeing prereceive buffer

08
Error freeing input mailbox buffer

ARICOMB nn

01
Communication Link error - REPLY

02
Same as 01

03
Communication Link error - Nonzero message length

04
Communication Link error - RECEIVE

ARISIIO nn

05
The database directory has not been properly restored.

ARIYC25 nn

09
The DB2 Server for VM system was rolling back the drop index operation. Message ARI00421 contains the DBSS Return Code. Refer to Chapter 18, 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.

ARIYI07 nn

05
ARIYI07 is using the CP IUCV DASD block I/O function. An IUCV send request has been made, and the Return Code is in message ARI0925E. See message ARI0925E for diagnosing the Return Code.

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 format and reserve of the log minidisks. 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 ]