Recovering after the broker's queue manager fails

Before you start

Try to get to the root of the problem first, using the diagnosis techniques described throughout the Diagnosing errors section of the information center.

If your problem cannot be resolved using these techniques, contact your IBM Support Center.

Use the procedure in this section only as a last resort.

If the failed queue manager is shared between a broker, User Name Server and a Configuration Manager, re-create all three components, because each component creates different queues. For information on how to recover a shared queue manager, see Recovering after a shared queue manager fails.

If the broker's queue manager fails and cannot be corrected using problem determination, or by the IBM Support Center, you must perform the following sequence of operations to re-create it:

  1. Ensure that no workbench users are deploying to the broker. You must wait until these actions have completed.
  2. Stop the broker using the mqsistop command.
  3. If there is no damage to any of the broker database tables, take a backup of these tables. These tables are interdependent and must all be in a consistent state when restored. You cannot backup or restore individual tables.
  4. Delete the broker using the mqsideletebroker command, with the -q flag to remove the queue manager.
  5. Re-create the broker using the mqsicreatebroker command. The mqsicreatebroker command creates the queue manager and default queues automatically.
  6. Re-create any specific queues that are needed for your message flows.
  7. Restore the broker database tables, either from the backup you have just taken, or from a previously-successful backup version.
  8. Start the broker using the mqsistart command.
  9. Redeploy the domain configuration.

Related tasks
Creating a broker
Deleting a broker
Recovering after failure

Related reference
mqsicreatebroker command
mqsideletebroker command
mqsistart command
mqsistop command