Recovering after the broker database fails

Try to get to the root of the problem first, using the diagnosis techniques described throughout the Troubleshooting and support 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 broker database fails and cannot be corrected using problem determination, or by the IBM Support Center, perform the following sequence of operations to re-create the broker:

  1. Ensure that no workbench users are deploying to the broker. You must wait until any such actions have completed.
  2. Stop the broker using the mqsistop command.
  3. Start of changeIf possible, re-create the broker database from a backup version. If this is not possible, perform the following actions in the order shown:
    1. Delete the broker using the mqsideletebroker command.
    2. Remove completely all references to the broker from the Configuration Manager repository. You can do this by removing the broker from the topology using the Message Brokers Toolkit. Ensure that the broker's SYSTEM.BROKER.ADMIN.QUEUE queue has been deleted and initiate a topology deploy.
    3. Re-create the broker using the mqsicreatebroker command.
    4. Add the broker to the Configuration Manager's domain topology.
    End of change
  4. Start the broker using the mqsistart command.
  5. If you were unable to restore the broker's database from a backup, redeploy the broker's configuration.
Related tasks
Creating a broker
Deleting a broker
Recovering after failure
Related reference
mqsicreatebroker command
mqsideletebroker command
mqsistart command
mqsistop command