How does the "DB2-Database HADR State" rule function?
What is the "DB2 - Database HADR State" rule used for?
This alarm is invoked when the HADR state is not in peer state. Ensuring that the database is in PEER state is important in order to prevent data losses in a crisis situation.
a). HADR_SYNCMODE = "SUPERASYNC" and HADR_STATE is not 3
or
b). HADR_SYNCMODE is not "SUPERASYNC" AND HADR_STATE is not 0 or 4
Source external IBM documentation:
SYNC
Compared with the SYNC and NEARSYNC modes, the ASYNC mode results in shorter transaction response times but might cause greater transaction losses if the primary database fails. In this mode, log writes are considered successful only when both of the following conditions are met:
SUPERASYNC
This mode has the shortest transaction response time but also has the highest probability of transaction losses if the primary system fails. This mode is useful when you do not want transactions to be blocked or experience longer response times due to network interruptions or congestion. In this mode, the HADR pair can never be in peer state or disconnected peer state. The log writes are considered successful only when the log records were written to the log files on the primary database. Because the primary system does not wait for acknowledgement from the standby system, transactions might be considered committed when they are still on their way to the standby.
Source external IBM documentation
The database is not connected to its partner database.
CATCHUP (1)
The database is doing local catchup.
The database is waiting to connect to its partner to do remote catchup.
REMOTE CATCHUP (3)
The database is doing remote catchup.
The primary and standby databases are connected and are in peer state.
DISCONNECTED PEER (5)
The primary and standby databases are in disconnected peer state.
