For details about the measures to be taken when an error occurs in a status file, see the HiRDB Version 8 System Operation Guide.
pd_sts_singleoperation operand value | Processing by HiRDB | HiRDB administrator's action |
---|---|---|
continue | When an error is detected in a server status file, HiRDB cannot identify the current file, and thus startup of the server is stopped and HiRDB (or the unit in the case of a HiRDB/Parallel Server) is not started. | The HiRDB administrator identifies the current file and specifies the pd_sts_last_active_file and pd_sts_last_active_side operands. Afterwards, start HiRDB. |
stop (default value) | When an error is detected in a server status file, HiRDB identifies the current file and startup of the server is continued. However, if the primary and secondary files satisfy any of the conditions listed in the table below (cases in which HiRDB cannot identify the current file), startup of the server is stopped and HiRDB (or the unit in the case of a HiRDB/Parallel Server) is not started. | If HiRDB cannot identify the current file, the HiRDB administrator identifies the current file and specifies the pd_sts_last_active_file and pd_sts_last_active_side operands. Afterwards, start HiRDB. |
pd_sts_initial_error operand value | File A status | File B status |
---|---|---|
continue | Error shutdown | Error shutdown |
Error shutdown | Open (initial state) | |
Error shutdown | No real file | |
Open (initial state) | Error shutdown | |
Open (initial state) | No real file | |
No real file | Open (initial state) | |
No real file | Error shutdown | |
No real file | No real file | |
excontinue | Error shutdown | Error shutdown |
Error shutdown | No real file | |
No real file | Error shutdown | |
No real file | No real file |
Item | pd_sts_initial_error operand value | |
---|---|---|
stop | continue or excontinue | |
Processing by HiRDB during server startup | When an error is detected in a server status file, startup of the server is stopped and HiRDB (or the unit in the case of a HiRDB/Parallel Server) is not started. | Even when an error is detected in a server status file, the startup of the server is continued if the current file is normal. |
Specification guideline | To improve system reliability, specify stop. | To simplify the error-handling actions during HiRDB startup, specify continue or excontinue. |
Advantage | Guarantees that all server status files of the server are normal when the server starts. Therefore, if an error occurs in the current file after HiRDB has started, it can be swapped to a spare file. | Even when an error is detected in a server status file during server startup, HiRDB can start with the remaining normal files only. Therefore, HiRDB stop time can be shortened. In this case, because the number of spare files has become small, it is necessary to immediately repair the status files containing errors. |
Disadvantage | Possibility increases that an error in a server status file stops the startup of HiRDB. | Because HiRDB may be running with only a small number of spare files, system reliability is low. Depending on the number of spare files available, it may not be possible to swap server status files. |
Item | pd_sts_singleoperation operand value | |
---|---|---|
stop | continue | |
Specification guideline | To improve system reliability, specify stop. | Specify continue if it is important not to stop HiRDB. |
Advantage | When an error occurs in one of the current files and a spare file is not available, operation in the single-operation mode does not occur and HiRDB is abnormally terminated. Consequently, the possibility of losing the content of the current files is reduced. | Even when an error occurs in one of the current files and a spare file is not available, processing can be continued. Therefore, the possibility that an error in the status file stops HiRDB is reduced. |
Disadvantage | Possibility that an error in the status file stops HiRDB increases. However, increasing the number of spare files can reduce this possibility. | If an error occurs in the normal status file during operation in the single-operation mode or if HiRDB is abnormally terminated during updating of the status file, the content of the current file is lost and HiRDB cannot be restarted. |