Recovery procedures
In this chapter, we introduce and describe procedures for recovering data in the following cases:
Loss of WebSphere MQ (non-persistent) messages
Data corruption at the target DBMS (not related to Q Replication)
Need to restart send queue from current point in the DB2 log
WebSphere MQ spill queue full during a LOAD phase
We also review the procedure that is available to sync up the Q Capture and Q Apply (planned outage) programs’ shutdown, in particular request the Q Capture program to stop at a particular point in the ...

Get Understanding and Using Q Replication for High Availability Solutions on the IBM z/OS Platform now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.