If server processes terminate abnormally often, servers may not be able to accept new services. However, because HiRDB itself does not usually terminate abnormally when a server process does, frequent server process abnormal terminations could bring online operations to an effective halt. To prevent this from occurring, the abnormal termination monitoring facility has been made available.
If the number of times that a server process is terminated abnormally in a specified amount of time reaches the value specified in the pd_down_watch_proc operand, HiRDB (or the associated unit for a HiRDB/Parallel Server) also terminates abnormally. This capability is provided by the abnormal termination monitoring facility.
We recommend that you use this facility in conjunction with the system switchover facility. This way, if HiRDB terminates abnormally because server processes have terminated abnormally more than the specified number of times, the system will be switched over quickly. If this monitoring facility is not used, HiRDB does not terminate abnormally, and the system is not switched over.
Even if you do not use this facility, you can restart HiRDB, which will refresh memory and other resources, leading to improved processing efficiency.
If HiRDB terminates abnormally due to the abnormal termination monitoring facility, the KFPS-01821-E and KFPS00729-E messages are issued.
This facility monitors processes that have terminated abnormally due to a PDCWAITTIME timeout or an abort. For a HiRDB/Single Server, it counts the number of times that single server processes terminate abnormally. For a HiRDB/Parallel Server, it counts the total number of times that front-end, back-end, and dictionary server processes in the unit terminates abnormally. Table 8-11 lists the factors that may cause server processes to terminate abnormally and indicates which of these are counted as an abnormal termination.
Table 8-11 Causes of abnormal termination of server processes and which are counted as an abnormal termination
Cause of abnormal termination of a server process | Counted as an abnormal termination? | |||
---|---|---|---|---|
Single server process | Front-end server process | Dictionary server process | Back-end server process | |
The value of the PDCWAITTME operand in the client environment definitions was exceeded. | Y | Y | N1 | N1 |
The pdcancel command was executed. | N | N2 | N | N |
An internal forced termination occurred (HiRDB issued SIGKILL internally to stop the process). | Y3 | Y3 | N1 | N1 |
An abort occurred. | Y | Y | Y | Y |
Rollback occurred on an XA-connected UAP. | Y | Y | N | N |
An abnormal termination other than the above occurred. | Y | Y | Y | Y |
You use the pd_down_watch_proc operand to specify the period over which the number of server process abnormal terminations is to be monitored and the maximum number of times that server processes are to be allowed to terminate abnormally.