Recovering after the configuration repository (DB2) 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 repository fails and cannot be corrected using problem determination, or by the IBM Support Center, perform the following sequence of operations to re-create it:

  1. Ensure that no workbench users are deploying to brokers. You must wait until these actions have completed.
  2. Stop all brokers that are using the Configuration Manager using the mqsistop command.
  3. Stop the Configuration Manager using the mqsistop command.
  4. Re-create the configuration repository from a backup version.
    If you do not have a backup of your configuration repository, re-create the Configuration Manager at this stage. This re-creates the configuration repository. However, any of the data that you previously had in the repository will be lost. To re-create the Configuration Manager:
    1. Delete the Configuration Manager using the mqsideleteconfigmgr command.
    2. Re-create the Configuration Manager using the mqsicreateconfigmgr command. The mqsicreateconfigmgr command creates the configuration repository automatically.
  5. Start the Configuration Manager using the mqsistart command.
  6. Start your brokers using the mqsistart command.

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