Db2 HADR log shipping during SET WRITE SUSPEND

Answer

The SET WRITE SUSPEND operation is only supported on the HADR primary database.

If a SET WRITE SUSPEND INCLUDE LOGS operation is performed on the primary database while in PEER or REMOTE CATCHUP states, then new log generation on the primary database will stop immediately, and any existing log data on the primary database will be shipped to the standby database.

If a SET WRITE SUSPEND EXCLUDE LOGS operation is performed on the primary database while in PEER or REMOTE CATCHUP states, then new log generation on the primary database can still occur, and any existing or new log data on the primary database will be shipped to the standby database. See the SET WRITE Command Knowledge Center page for expectation so the EXCLUDE LOGS option.

If a SET WRITE SUSPEND operation is performed on the primary database while the HADR database pair are in REMOTE CATCHUP state, then:

o In Version 10.5 Fix Pack 7 and later releases, the databases will not attempt to transition to PEER state and will remain in REMOTE CATCHUP state until a SET WRITE RESUME operation is issued. While in REMOTE CATCHUP state, log shipping to the standby database may continue as described above.

o In Version 10.5 Fix Pack 6 and earlier releases, when the database attempts to transition to PEER state, log shipping to the standby database may stop.

If a SET WRITE SUSPEND operation is performed on the primary database, and the HADR_PEER_WINDOW configuration parameter is enabled, the Standby database may remain in REMOTE_CATCHUP_PENDING state, for the duration of time until the SET WRITE RESUME command is issued.