MQSeries.net :: View topic

ramnagab · Posted: Sun Dec 12, 2004 8:50 am Post subject:

Hi

first I created a broker called CC on the command line using mqsicreatebroker. second I am trying to create a reference to that broker on the broker toolkit using (new > broker) but I got and error message and the details for it is

BIP1511E: Queue manager 'cc_cm' cannot be associated with broker 'CC'; it is already associated with broker 'CC'.

An attempt was made to associate broker CC with WebSphere MQ queue manager cc_cm, but broker CC already has this association. A WebSphere MQ queue manager can only have one broker associated with it.

Change the queue manager for one of the brokers. If this problem occurs after you have deleted broker CC then tried to recreate it, you must first initiate a deploy operation to automatically delete the configuration from the real broker. It is only after all types of configuration data (message flows, message sets, topology, topics) have been successfully deleted from the real broker that the broker document is finally deleted from the configuration repository. Until that time the queue manager can not be associated with another broker. Once this has been done, you must also physically delete and recreate the real broker using the mqsideletebroker and mqsicreatebroker commands.
____________________________________________________________
BIP1711W: Broker is not accessible or does not exist.

An attempt was made to register for information on the Broker with UUID 'e92211c8-0001-0000-0080-c24078fabc68', but either the user who asked for the information does not have sufficient authority to do so or the Broker does not exist.

Ensure that the user of the application that issued the request has sufficient authority to view the Broker. If the user has sufficient authority and the object exists, attempt to retry the operation. If the problem persists please turn on Configuration Manager tracing to capture the error and contact your IBM support center.
____________________________________________________________
BIP1711W: ExecutionGroup is not accessible or does not exist.

An attempt was made to register for information on the ExecutionGroup with UUID 'ea2211c8-0001-0000-0080-c24078fabc68', but either the user who asked for the information does not have sufficient authority to do so or the ExecutionGroup does not exist.

Ensure that the user of the application that issued the request has sufficient authority to view the ExecutionGroup. If the user has sufficient authority and the object exists, attempt to retry the operation. If the problem persists please turn on Configuration Manager tracing to capture the error and contact your IBM support center.
____________________________________________________________
BIP1520I: Deploy operations successfully initiated.

The Configuration Manager has processed the deploy request and initiated the deploy of configuration data to the following brokers. Active brokers: . Deleted brokers: CC .

Open the Event Log Editor to check the outcome of the operations. There will be a separate set of log messages for each broker.

Thansk