HiRDB termination

Question: When I entered the pdstop -f command, why did HiRDB or the unit terminate abnormally with abort code Polkcrt?

Answer: This event likely occurred because a server process in critical status was forcibly terminated. Ignore this event because there is no problem in terms of operations.; This event might also occur because forced termination processing by the pdstop -f command immediately stopped a server process that was in critical status. Therefore, although this event can occur, there is no problem because HiRDB is restarted by the next pdstart command (the database is restored from the system log).

(2) HiRDB will not terminate normally

Question: Why won't HiRDB terminate normally?

Answer

HiRDB cannot terminate normally while there is a transaction in uncompleted status or a connected user. Use the following commands to check the status of connected users and transactions before attempting to terminate HiRDB normally:

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

For details about the actions to be taken, see 20.13 When HiRDB cannot be terminated because a user is still connected or 20.14 Actions when there is an undetermined transaction.

(3) When HiRDB terminated normally, the system server terminated abnormally

Question: I executed the pdstop and shutdown commands consecutively in this order using a shell script, then the system server terminated abnormally. Why?

Answer

The system server does not terminate the moment the pdstop command is entered. If the shutdown command is executed while the system server is still engaged in termination processing, the system server terminates abnormally.

Do not execute the shutdown command immediately after entering the pdstop command. For example, execute the following commands in the sequence shown:

pdstop
sleep 60
shutdown

(4) When I closed the window used to enter the pdstop command, HiRDB terminated abnormally

Question: I entered the pdstop command, but there was no response from the command. Therefore, I closed the window used to enter the pdstop command. HiRDB terminated abnormally immediately after this. Why?

Answer: If the pdstart command is stopped forcibly, conformity cannot be maintained in the shared resources, resulting in abnormal termination of HiRDB. Similarly, if the window is closed while waiting for a response from the pdstop command, HiRDB terminates abnormally.; Do not close the window used to enter the pdstop command until the command has terminated. This also applies to all other operation commands and utilities; do not close the corresponding window during execution or while waiting for a response.

Appendix A.7 HiRDB termination

(1) When the pdstop -f command was entered, the unit terminated abnormally

(2) HiRDB will not terminate normally

(3) When HiRDB terminated normally, the system server terminated abnormally

(4) When I closed the window used to enter the pdstop command, HiRDB terminated abnormally