When a hardware or software error occurs in a HiRDB parallel server configuration, HiRDB isolates the affected units and terminates them abnormally, rather than shutting down all the units comprising the HiRDB (although there are some exceptions to this). When an error occurs in a HiRDB single server configuration, HiRDB terminates the unit, which results in complete shutdown of HiRDB, because a HiRDB single server configuration consists of only one unit.

When HiRDB has terminated abnormally and it is restarted after the cause of the error has been eliminated, HiRDB restores the system to its status immediately before the error occurred.

When HiRDB terminates abnormally, the unit will usually restart automatically, depending on the specification of the pd_mode_conf operand in the system common definition. However, if HiRDB terminates abnormally three times^# in succession, the unit will not restart again automatically.

In such a case, the HiRDB administrator must eliminate the cause of the error and use the pdstart command to restart HiRDB.

#

The pd_term_watch_count operand can be used to change this count. For example, if pd_term_watch_count operand=2 is specified, HiRDB restart will not be attempted again after two consecutive abnormal terminations.

In this case, HiRDB enters PAUSE status. When HiRDB is in PAUSE status, you cannot execute the pdstart command, and therefore you cannot restart HiRDB. You can use the pdls -d ust command to check whether HiRDB is in PAUSE status. To release it from PAUSE status, remove the cause of abnormal termination, which is explained in the information included with the KFPS00715-E message, and then execute the pdrpause command. For a HiRDB parallel server configuration, execute the pdrpause command on the unit that is in PAUSE status.