Resolving problems when deleting resources

This topic contains advice for dealing with some common problems that can arise when deleting resources:

Problems when deleting a broker:
Problems when deleting other resources:

You cannot delete your broker after deleting your broker database

The workbench is deploying to a deleted broker

If the deployment step fails because the broker has already been deleted using the mqsideletebroker command, or it is otherwise unable to respond, remove 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 further topology deploy.

Alternatively, you can use the Configuration Manager Proxy API "TopologyProxy.removeDeletedBroker(String)" to programmatically purge all references to the broker:
  1. Start the Configuration Manager Proxy API Exerciser sample (which is available on the Start menu in Windows).
  2. Connect to the Configuration Manager.
  3. Right-click the topology object and click Remove references to a previously deleted broker.

The broker should now have disappeared from the workbench.

Do not try to re-create a broker using the mqsicreatebroker command until you are confident that it has been removed from the workbench. Similarly, do not reuse broker or queue manager names until you are confident that they are not in use elsewhere.

You cannot delete a broker following a disk failure, or the Configuration Manager contains references to a deleted broker

The mqsideletebroker command hangs if the DB2 profile has not been run

Error message BIP8052 is issued when you delete the Configuration Manager

You cannot delete a project from your workspace

You are unable to remove a domain from the Domains navigator