18.22 Actions to take when an error occurs while a local buffer is being used to update a shared table (HiRDB/Parallel Server only)

Executor: HiRDB administrator

You must apply LOCK TABLE to use a local buffer to update a shared table. If the server process terminates abnormally when both of the conditions listed below are applicable, abort code Phb3008 is issued and the unit may terminate abnormally:

When both of these conditions are applicable and an updated page exists at the time the server process terminates abnormally, recovery processing may not be possible by means of rollback processing. If this happens, recovery processing is performed when the unit is restarted. Table 18-23 shows the HiRDB processing and the actions to take if an error occurs when a local buffer is being used to update a shared table (without the LOCK TABLE specification).

Table 18-23 HiRDB processing and actions to take if an error occurs when a local buffer is being used to update a shared table (without LOCK TABLE specification)

Cause of abnormal termination of server processHiRDB processing if an updated page exists when the server process terminates abnormallyAction to be taken by the HiRDB administrator
PDSWAITTIME timeoutAbort code Phb3008 is issued, and the unit may terminate abnormally.Restart the unit if it terminated abnormally.
PDCWAITTIME timeout
pdcancel command executed
AbortAbort that occurs due to detection of a HiRDB conflict.
OtherAny unexpected error, such as SIGSEGV, SIGBUS, reception of an external signal, exi, etc.
Note
HiRDB does not terminate abnormally when a server process terminates abnormally due to a PDSWATCHTIME timeout, even if an updated page exists.