Recovering after the Configuration 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 Configuration Manager environment is damaged, or one or more of the database tables are corrupted, and the problem cannot be corrected using problem determination, or by the IBM Support Center, perform the following sequence of operations to recreate it:

  1. Ensure that all workbench sessions are stopped.
  2. Stop the Configuration Manager using the mqsistop command.
  3. Stop the Configuration Manager's queue manager using the endmqm command.
  4. Delete the Configuration Manager using the mqsideleteconfigmgr command:
    1. If you are recovering the Configuration Manager because one or more of the configuration repository tables is damaged, delete these tables when you delete the Configuration Manager. This destroys all information pertinent to the broker domain (not just data internal to the Configuration Manager). You must export everything you can from the domain before you issue the mqsideleteconfigmgr command specifying the -n and -m flags.
    2. If the database tables are undamaged, omit the -n and -m flags. This preserves your configuration data in the repository.
  5. If you are recovering the Configuration Manager because one or more of the configuration repository tables is damaged, restore the repository from a previously successful backup version.
  6. Recreate the Configuration Manager using the mqsicreateconfigmgr command.
  7. Start the Configuration Manager using the mqsistart command.
  8. Restart the workbench if it is not currently running, and switch to the Broker Administration perspective.
  9. If you have completed step 4a and step 5, you must also redeploy the domain configuration to ensure that the configuration across the broker domain is consistent.
Related tasks
Creating a Configuration Manager
Deleting the Configuration Manager
Deploying message flow applications
Deploying a topology configuration
Recovering after failure
Related reference
mqsicreateconfigmgr command
mqsideleteconfigmgr command
mqsistart command
mqsistop command