Notes on HiRDB termination

Event: Normal termination of HiRDB failed.

Cause: HiRDB cannot be terminated normally if there are transactions that have not been completed or if there are connected users.

Action

Before terminating HiRDB normally, check for any connected users or transactions that have not been completed:

The pdls -d prc command is used to check for connected users
The pdls -d trn command is used to check transaction status

If no user is connected but there is a transaction processing, the following commands can be entered to complete the transaction:

Use the pdcmt command to commit the transaction
Use the pdrbk command to roll back the transaction

For details on how to terminate HiRDB normally when transactions have not been completed or users are still connected, see 20.14 Actions when there is an undetermined transaction.

(2) Do not stop the pdstop command forcibly

Event: The window from which the pdstop command was entered was closed because there was no response from the command, and HiRDB terminated abnormally.

Cause: If the pdstop command is stopped forcibly, HiRDB terminates abnormally because conformity among shared resources is lost. HiRDB also terminates abnormally if the window is closed while waiting for a response from the pdstop command.

Action: Do not close the window from which the pdstop command is entered until the pdstop command has terminated.; This also applies to the other operation commands and utilities; in other words, do not close the window while waiting for a response from any command or utility or while a command or utility is executing.

(3) Note the shutdown command execution timing

Event: When the pdstop and shutdown commands were executed consecutively in this order as a shell script, the system server terminated abnormally.

Cause: When the pdstop command terminates, the system server has not yet terminated. If the shutdown command is executed while the system server is still engaged in termination processing, the system server terminates abnormally.

Action

Do not execute the shutdown command immediately after the pdstop command. To execute the shutdown command after the pdstop command, execute the following commands in the order shown:

pdstop
sleep 60
shutdown

If the system server terminates abnormally, the HiRDB startup mode after the next OS boot-up is restart. During a restart, HiRDB restores the system to its status at the time of the OS shutdown, which means that the restart operation might take a long time. For notes on restarting HiRDB, see 1.7.2 Notes on planned termination, forced termination, and abnormal termination.

1.7.1 Notes on HiRDB termination

(1) HiRDB cannot be terminated normally if there are uncompleted transactions or connected users

(2) Do not stop the pdstop command forcibly

(3) Note the shutdown command execution timing