Two full repositories moved at the same time

If you move both full repositories to new network addresses at the same time, the cluster is not updated with the new addresses automatically. Follow the procedure to transfer the new network addresses. Move the repositories one at a time to avoid the problem.


Problem

Cluster DEMO contains two full repositories, QM1 and QM2. They were both moved to a new location on the network at the same time.


Solution

  1. Alter the CONNAME in the CLUSRCVR and CLUSSDR channels to specify the new network addresses.
  2. Alter one of the queue managers ( QM1 or QM2) so it is no longer a full repository for any cluster.
  3. On the altered queue manager, issue the command REFRESH CLUSTER(*) REPOS(YES). Note: For large clusters, use of the REFRESH CLUSTER command can be disruptive to the cluster while it is in progress, and again at 27 day intervals thereafter when the cluster objects automatically send status updates to all interested queue managers. See Refreshing in a large cluster can affect performance and availability of the cluster.
  4. Alter the queue manager so it is acting as a full repository.


Recommendation

You could avoid the problem as follows:

  1. Move one of the queue managers, for example QM2, to its new network address.
  2. Alter the network address in the QM2 CLUSRCVR channel.
  3. Start the QM2 CLUSRCVR channel.
  4. Wait for the other full repository queue manager, QM1, to learn the new address of QM2.
  5. Move the other full repository queue manager, QM1, to its new network address.
  6. Alter the network address in the QM1 CLUSRCVR channel.
  7. Start the QM1 CLUSRCVR channel.
  8. Alter the manually defined CLUSSDR channels for the sake of clarity, although at this stage they are not needed for the correct operation of the cluster.

The procedure forces QM2 to reuse the information from the correct CLUSSDR channel to re-establish contact with QM1 and then rebuild its knowledge of the cluster. Additionally, having once again contacted QM1, it is given its own correct network address based on the CONNAME in QM2 CLUSRCVR definition.

Parent topic: Queue manager clusters troubleshooting