Resolving an inconsistent problem in DR RDQM

A DR status of inconsistent can be reported if synchronization fails between the primary and secondary instances of a queue manager.

An inconsistent state is reported on the secondary instance of a queue manager because the replication connection to the primary instance is lost during a synchronization operation. We might have to take action to resolve this situation. Consider the following sequence of events:

DR primary queue manager in sync with DR secondary queue manager
Replication link lost between primary and secondary
Replication link restored between primary and secondary
A resynchronization occurs where the DR secondary queue manager catches up with the DR primary queue manager. During this time the DR status of synchronization in progress is reported for both queue managers.
If the replication is then lost again during the resynchronization, the status on the DR secondary is reported as Inconsistent.

If the node hosting the primary queue manager is still operational, and the replication link can be restored, resynchronization happens automatically. The inconsistent state is resolved without you taking any action.

If the node hosting the primary queue manager is no longer operational, we can resolve the inconsistent state by implementing a revert to snapshot on the secondary queue manager. This operation reverts the data to the last known good state.

Procedure

To resolve an inconsistent state:

On the recovery node, make the secondary instance into the primary instance:
```
rdqmdr -m qmname -p
```
The revert to snapshot operation starts.
On the recovery node, check the status of the queue manager to see when the revert to snapshot operation is complete:
```
rdqmstatus -m qmname
```
When the queue manager status is Normal, start the queue manager:
```
strmqm qmname
```

Parent topic: Operate in a disaster recovery environment