If an error occurs during an HiRDB process, HiRDB terminates the process abnormally, then rolls back the process for each server by activating a recovery process. There is no need for the HiRDB administrator to take any action, because the corresponding process is restarted automatically.
Depending on the severity of the error, HiRDB may terminate abnormally the unit that is executing the erroneous process. In such a case, the HiRDB administrator must restart the abnormally terminated unit (although the unit may be restarted automatically, depending on the specification of the pd_mode_conf operand).
Described below are the actions to be taken by the HiRDB administrator when a unit terminates abnormally due to abnormal termination of a process.
Table 18-2 shows the action to be taken by the HiRDB administrator in the event a HiRDB/Single Server terminates abnormally.
Table 18-2 HiRDB administrator's action in the event of an abnormal termination of a HiRDB/Single Server
HiRDB processing | HiRDB administrator's action |
---|---|
Terminates the HiRDB/Single Server abnormally | Eliminate the cause of the error and restart the HiRDB/Single Server (the HiRDB/Single Server may be restarted automatically, depending on the pd_mode_conf operand specification), then re-execute the previous processing. |
Table 18-3 shows the actions to be taken by the HiRDB administrator in the event a HiRDB/Parallel Server terminates abnormally.
Table 18-3 HiRDB administrator's actions in the event of an abnormal termination of a HiRDB/Parallel Server
Error status | HiRDB processing | HiRDB administrator's action |
---|---|---|
Process error at unit controller | Terminates abnormally the unit where the corresponding process is located. | Restart the corresponding unit (the unit may be restarted automatically, depending on the pd_mode_conf operand specification). |
Process error at system manager | Terminates abnormally the unit where the system manager is located. HiRDB does not accept any operation command or UAP execution request while the system manager is shut down. No message log can be collected during that time. | Eliminate the cause of the error and restart the corresponding unit (the unit may be restarted automatically, depending on the pd_mode_conf operand specification), then re-execute the previous processing. |
Process error at front-end server | Terminates abnormally the unit where the front-end server is located. HiRDB does not accept any processing request while the front-end server is shut down. It treats a processing request as a timeout-level communication error. If a front-end server process terminates abnormally, HiRDB recovers the process. If it is necessary to shut down the unit in such a case, HiRDB terminates abnormally the unit where the corresponding process is located. | Eliminate the cause of the error and restart the corresponding unit (the unit may be restarted automatically, depending on the pd_mode_conf operand specification), then re-execute the previous processing. |
Process error at dictionary server | Terminates abnormally the unit where the dictionary server is located. | |
Process error at back-end server | Terminates abnormally the unit where the back-end server is located. |