For details about the measures to be taken when an error occurs in a status file, see the HiRDB Version 9 System Operation Guide.
pd_sts_singleoperation operand value | Processing performed by HiRDB | Action to be taken by the HiRDB administrator |
---|---|---|
continue | When an error is detected in the server status file, HiRDB cannot identify the current file, and thus the startup of the server is stopped, and HiRDB (or a unit for a HiRDB parallel server configuration) 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 the server status file, HiRDB identifies the current file and the startup of the server is continued. However, if File A or B satisfies any of the conditions listed in the following table (cases in which HiRDB cannot identify the current file), the startup of the server is stopped, and HiRDB (or a unit for a HiRDB parallel server configuration) 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, the startup of the server is stopped and HiRDB (or a unit for a HiRDB parallel server configuration) 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 starts, it can be swapped to a spare file. | Even when an error is detected in some 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 | The possibility increases that an error in a server status file stops the startup of HiRDB. | Because HiRDB might be running with only a small number of spare files, system reliability is low. Depending on the number of spare files available, it might not be possible to swap server status files. |
Corresponding No. | Processing performed by HiRDB | Action to be taken by the HiRDB administrator |
---|---|---|
[1] | HiRDB startup processing continues. | None |
[2] | HiRDB identifies the latest current file and continues the startup processing. | Make the file that is in the error-shutdown state into a spare file. |
[3] | Using the file specified in the pd_sts_last_active_file operand as the current status file, HiRDB startup processing continues. | Make the file that is in the error-shutdown state into a spare file. |
[4] | Using the files specified in the pd_sts_last_active_file and pd_sts_last_active_side operands as the current status files, HiRDB startup processing continues. | Make the file that is in the error-shutdown state into a spare file. |
[5] | Because stop is specified for the pd_sts_initial_error operand, HiRDB startup processing is stopped. | See the manual HiRDB Version 9 Messages, and take the corrective action indicated by reason code 0000000010 in message KFPS01005-E. |
[6] | Because the current file that was being used during the previous operation cannot be identified, HiRDB startup processing is stopped. | See the manual HiRDB Version 9 Messages, and take the corrective action indicated by reason code 0000000016 in message KFPS01005-E. |
[7] | Because the normal current file identified by HiRDB does not match the file specified in the pd_sts_last_active_side operand, HiRDB startup processing is stopped. | See the manual HiRDB Version 9 Messages, and take the corrective action indicated by reason code 0000000017 in message KFPS01005-E. |
[8] | Because the current file name identified by HiRDB does not match the file name specified in the pd_sts_last_active_file operand, HiRDB startup processing is stopped. | See the manual HiRDB Version 9 Messages, and take the corrective action indicated by reason code 0000000015 in message KFPS01005-E. |
[9] | Because the normal current file that was being used during the previous operation cannot be identified, HiRDB startup processing is stopped. | See the manual HiRDB Version 9 Messages, and take the corrective action indicated by reason code 0000000018 in message KFPS01005-E. |
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 | The possibility increases that an error in the status file stops HiRDB. 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 restart. |