Home

 

Resolving Problems

 

The following problems can all be resolved using the REFRESH CLUSTER command. It is unlikely that you will need to use this command during normal circumstances. Use it only if you want your queue manager to make a fresh start in a cluster. Issue the REFRESH CLUSTER command from a queue manager to discard all locally held information about a cluster. For example you might use it if you think your full repository is not up-to-date, perhaps because you have accidentally restored an out-of-date backup. The format of the command is:

REFRESH CLUSTER(clustername) REPOS(YES/NO)

The queue manager from which you issue this command loses all the information in its full repository concerning the named cluster. It also loses any auto-defined channels that are not in doubt and which are not attached to a full repository queue manager. The queue manager has to make a cold-start in that cluster. It must reissue all information about itself and renew its requests for updates to other information that it is interested in. (It does this automatically.)

Here are some procedures for recovering clusters.

• Problem 1 — Out of date information in a restored cluster.
  

• Problem 2 — cluster DEMO force removed by mistake.
  

• Problem 3 — Possible repository messages deleted.
  

• Problem 4 — 2 full repositories moved at the same time.
  

• Problem 5 — Unknown state of a cluster.
  

 

Parent topic:

Troubleshooting

qc13300_

 

Home