14.1.1 Steps to take when the HADB server terminated abnormally

The following figure shows the steps to take when the HADB server terminated abnormally.

Figure 14‒1: Flow of steps to take when the HADB server terminated abnormally

Procedure

Check the message

If the HADB server terminated abnormally, use a text editor to open the server message log file and check the messages that have been output.

The server message log file is /spool/adbmessageXX.log in the server directory. XX in the file name is a sequential number between 01 and 04. Open the file with the latest modification date and time.

Based on the ID of the last error message that was output, see the manual HADB Messages, and check the cause of the error and the recommended action to take under Action.

If the output message text contains Save troubleshooting information by the "adbinfoget" command or if the action to take recommends that you contact the customer support center, proceed to step 2.

Otherwise, proceed to step 3.
If you need to contact the customer support center

Also collect troubleshooting information based on the explanation in 14.2 Collecting troubleshooting information (adbinfoget command). Have the troubleshooting information ready for the customer support center when you contact it.
If you do not need to contact the customer support center

Eliminate the cause of the error by taking the action prescribed in the output message.

After eliminating the cause of the error, restart the HADB server. After the transactions that were being processed when the error occurred are rolled back, the HADB server starts.