Resolving problems when creating resources

Advice for dealing with some common problems that can occur when you create resources.

Look for the problem that you have encountered, and follow the guidance provided to recover from the error.

Problems when creating a broker:
Problems when creating other resources:

Checklist for configuring databases

  1. Ensure that the ODBC database definitions have been fully configured by following the documented instructions in Configuring broker databases. Remember the following points:
    1. Edit the final stanza in the ODBC files; the [ODBC] stanza.
    2. You must configure the 32-bit odbc.ini settings even if all your execution groups are 64-bit. The exception is HP-UX on Itanium, where all broker processes are 64-bit, and you must configure only the 64-bit ODBC definition file.
    3. Ensure that the ODBC drivers used are as specified in this information center and in the sample odbc.ini files. This check is particularly important when you migrate from an earlier release, when different driver names might have been required. You might need to update the odbc.ini file used with the earlier release to reflect new ODBC driver names, and to include new settings.
  2. Check the environment settings, referring to Configuring broker databases for details. Remember the following points:
    1. Run the mqsiprofile command.
    2. Set the required database environment variables (for example: run db2profile for DB2®).
    3. If you are using a 64-bit DB2 database instance, add <DB2 instance directory>/sqllib/lib32 to the start of the library search path environment variable (for all 32-bit brokers; that is, all broker platforms except HP-UX on Itanium).
    4. If the broker needs to access an Informix® user database, add $INFORMIX/lib:$INFORMIX/lib/esql:$INFORMIX/lib/cli to the library search path environment variable (see the Informix product documentation for more information). You must ensure that any WebSphere® Event Broker libraries appear before any Informix libraries in the library search path.
    5. If you are using a 64-bit Oracle instance, add $ORACLE_HOME/lib32 to the start of the library search path environment variable (for all 32-bit brokers; that is, all broker platforms except HP-UX on Itanium).
  3. Check that the user ID you use to access the database has sufficient permissions on the broker database to connect and to create tables and indices as described in Authorizing access to broker databases.
  4. Ensure that the broker's service user ID has read permissions on the database client lib directories and files.
  5. If you are using Oracle, you must also run the mqsi_setupdatabase command (for details see the mqsi_setupdatabase command).

Message BIP8146E is issued when creating a broker

Message BIP1511 is issued when creating a broker

Do not try to re-create the broker until the deleted topology has been deployed successfully. If the broker is no longer shown in the workbench, you can then re-create the broker:
  1. Create the broker by using the mqsicreatebroker command.
  2. Create the broker in the topology in the workbench.
  3. Deploy the topology.

Message BIP0874 is issued when saving the topology editor after creating or deleting a broker

Messages BIP2321, BIP2322, BIP8040 are issued when creating a broker

Start of change

Message BIP8081 is issued when creating a broker

End of change

You cannot create files when creating a broker on AIX

The Configuration Manager does not remove references to a deleted broker's queue manager

The JCL BIPGEN fails when you create a component on z/OS®

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

The mqsicreatebroker command core dumps when it is run using an Oracle data source

Your DataFlowEngine terminates with an abend when you create a broker on HP-UX using Oracle

Error message BIP8075 is issued when creating a Configuration Manager

Error message BIP2624 is issued when creating an execution group

You do not know what authorities are set as part of the mqsicreateaclentry command

Start of change

The Default Configuration wizard fails with invalid argument specified

End of change
Start of change

The Default Configuration wizard fails after installing DB2

End of change
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:41:15

au16560_