The operation to be performed when a heartbeat abnormality is detected using operating system/server heartbeat monitoring is decided on according to the environment where database multiplexing mode is performed or the operating method.
It is possible to select from the four operations below, and specify this in the parameters of Mirroring Controller:
Use the arbitration server to perform automatic degradation (switch/disconnect)
Call the user exit (user command) that will perform the degradation decision, and perform automatic degradation
Notification messages
Perform automatic degradation unconditionally (switch/disconnect)
The table below shows if jobs can be continued on the primary server when an issue is detected during heartbeat monitoring of the operating system/server.
Continuation of jobs on the primary server when an issue is detected during heartbeat monitoring of the operating system/server
Operation | Abnormal event | ||||
|---|---|---|---|---|---|
Server/operating system failures or no responses | Admin network issue | Log transfer network issue | Issue on a network for both admin and log transfer | ||
Primary server | Standby server | ||||
Automatic degradation using the arbitration server | Y | Y | Y | Y | Y (disconnect) |
Call a user exit and perform automatic degradation | Y (switch) | Y (disconnect) | Y | Y | Y |
Notification messages | N | N | Y | Y | Y |
Unconditional automatic degradation | Y | Y | N | Y | N |
Y: Job can be continued
N: Job cannot be continued
