Ensure the ODBC database definitions have been fully configured
as per the documented instructions: Configuring databases.
Remember the following points:
Edit the final stanza in the ODBC file; the [ODBC] stanza.
You must configure the 32 bit odbc.ini settings
even if all your Execution Groups are 64 bit. The exception is on the HP-UX platform where all broker processes
are 64 bit, and therefore only the 64 bit ODBC definition file needs to be
configured.
Ensure the ODBC drivers used are as specified in the online
docs and the sample odbc.ini files. This is particularly
important when migrating from an earlier release, when different driver names
may have been used. The odbc.ini file used with the earlier
release may need to be updated to reflect new ODBC driver names and to include
new settings.
Check the environment settings, referring to Configuring databases for
details. Remember the following points:
Run the mqsiprofile command.
Set the required database environment variables (for example:
run db2profile for DB2).
If 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).
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 Message Broker libraries
appear before any Informix libraries in the library search path.
If 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 exceptHP-UX).
Check that the userid 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 the databases.
Ensure that the Broker's service userid has read permissions on
the database client lib directories and files.
If you are using Oracle, you must also run the mqsi_setupdatabase command
(for details see mqsi_setupdatabase command).
Message BIP8146E is issued when creating a broker
Scenario: The mqsicreatebroker command
fails with the message BIP8146E: Unable to retrieve the SQL primitives
supported by the Database.
Explanation: The command has failed to successfully connect
and retrieve database properties information.
Solution: If this is the case:
Check that the userid being used to access the database has sufficient
permissions to connect to the database and to create tables.
Scenario: Error message BIP1511E is displayed
when you create a new broker in the Topology editor, as follows:
BIP1511E: Queue manager 'QM1' cannot be associated with broker
'BR1'; it is already associated with broker 'BR1'
Explanation: A queue manager cannot be associated with the
specified broker because it is already associated with that broker name. The
problem occurs because you performed an incorrect sequence of actions when
you originally deleted the broker, and you are now trying to re-create a broker
of the same name.
Solution: Delete the broker before attempting to re-create
it, as follows:
Stop the broker using the mqsistop command.
Delete the broker from the topology.
Check that the deletion was successful, and that the broker
has disappeared from the list in the workbench.
If you are using publish/subscribe and
the network of connected brokers has been modified as a result of the deletion,
issue a delta deploy of the topology.
Delete the broker using the mqsideletebroker command.
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, as follows:
Create the broker using the mqsicreatebroker command.
Create the broker in the topology.
Deploy the topology.
Message BIP0874 is issued while saving the topology
editor after creating or deleting a broker
Scenario: Message BIP0874E is displayed
while you are saving the topology editor after creating or deleting a broker,
and the broker is not created or deleted.
Explanation: This problem occurs because you are no longer
authorized to modify the topology.
Solution: Ask your WebSphere
Event Broker administrator
to give your user ID full access to the broker topology.
If
you close the editor and save the topology changes, you do not receive any
error messages.
Messages BIP2321, BIP2322, BIP8040 are
issued when creating a broker
Scenario: The mqsicreatebroker command
fails with the above set of messages.
Explanation: The command has failed to successfully connect
and retrieve database properties information.
Solution: Make the following checks:
That the environment has been setup correctly for database access. In
particular, if using a 64 bit DB2 or Oracle instance, ensure the 32 bit database
client libraries directory is at the front of the library search path.
That the Broker's service userid has read access to the database client
libraries.
For all broker platforms except HP-UX,
that the 32 bit ODBC file is configured, as the broker is a 32 bit application.
You cannot create files when creating a broker on AIX
Scenario: When you run the mqsicreatebroker command
on WebSphere
Event Broker for AIX, the following message is
displayed:
BIP8135E Unable to create files. Operating System return code 1
Explanation: The user ID that you create for WebSphere
Event Broker testing
must have a primary group of mqm, and have mqbrkrs as one of the group set. The following
example shows an AIX SMIT panel listing
the Change / Show Characteristics of a User:
Change / Show Characteristics of a User
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[TOP] [Entry Fields]
* User NAME peterc
User ID [202] #
ADMINISTRATIVE USER? false +
Primary GROUP [mqm] +
Group SET [mqm,system,mqbrkrs,sys> +
The Configuration
Manager does not remove references
to a deleted broker's queue manager
Scenario: The broker definition is incorrect, so you cannot
add a new broker.
Explanation: This can occur if you delete a broker component
without removing it from the Message Brokers Toolkit first.
If your broker definition is incorrect, you cannot instruct the Configuration
Manager to
add a new broker with the same queue manager to the broker domain because
the Configuration
Manager reports that the queue manager
is already associated with the broker that you deleted.
If
your broker definition is incorrect, you cannot redeploy. If you delete a
broker component then try to deploy to it, any subsequent deploy to that broker
fails because the Configuration
Manager reports that it
is already deploying to the broker that you have deleted.
Solution: Delete the queue manager for the deleted broker,
then deploy. When you deploy, the Configuration
Manager recognizes
that the queue manager does not exist and cleans up the broker's definition.
You can now associate the queue manager with another broker or redeploy the
broker.
The JCL BIPGEN fails when you create a component on z/OS
Scenario: The BIPGEN job fails when you are copying the
component profile (BIPBPROF, BIPCPROF, or BIPUPROF) from the PDSE to the file
system.
Explanation: There might not be enough space in the file
system, the component profile might not exist, or you might not have the appropriate
authority.
Solution: Make the following checks:
That the file system has sufficient space. You can check how much space
is used and how much is free in a file system using the OMVS command df
-P /pathname. 100 MB is 3 276 800 512 byte sectors.
That the profile file exists in the PDSE.
That you have the appropriate authority to write to the file system.
The mqsicreatebroker command
hangs if the DB2 profile has not been
run
Scenario: The mqsicreatebroker command
hangs if the DB2 profile has not been
run. If you stop the command, this could result in a partial broker
setup. This partially-created broker might be shown by the mqsilist command
and the registry but none of the broker tables will have been created.
Explanation: This error can occur if the environment has
not been set up correctly.
Solution: Remove any partial setup and ensure that the environment
is set up correctly by following the instructions in Configuring WebSphere Event Broker.
Run the DB2 profile before reissuing
the mqsicreatebroker command.
The mqsicreatebroker command
core dumps when it is run using an Oracle data source
Scenario: The mqsicreatebroker command
core dumps when it is run using an Oracle data source
Explanation: This problem occurs when the Oracle libraries
fail to load.
Solution: If you can run the Oracle sqlplus utility,
your basic Oracle environment is correct. However, the default Oracle libraries
are 64 bit versions and these are not compatible with the broker.
Check your LD_LIBRARY_PATH setting in the environment
when you create the broker.
The broker requires the 32 bit Oracle libraries
and these are normally found in <ORACLE_HOME>/lib32 for
a 64 bit Oracle installation. It is possible on some operating systems to
install a 32 bit only version of Oracle; if you have this variant of Oracle
installed, the libraries are in <ORACLE_HOME>/lib
Check that the Broker's service userid has read access to the Oracle client
libraries.
Check that the 32 bit ODBC definition file has been configured for the
broker (all platforms except HP-UX).
Your DataFlowEngine terminates with an abend when you create a Version 6.0 broker on HP-UX using
Oracle
Scenario: Your DataFlowEngine (DFE) terminates with an abend
when you create a Version 6.0 broker on HP-UX using
Oracle.
Explanation: This problem occurs when DB2 is
installed on the same computer as Oracle.
Solution: Remove the DB2 lil
files that are used by WebSphere
Event Broker. For example, issue the following commands:
Error message BIP8075 is issued when creating a Configuration
Manager
Scenario: On a Windows system,
the mqsicreateconfigmgr command
fails with message BIP8075 and a Java exception unsatisfiedLinkException.
Explanation: The Configuration
Manager cannot
find the JAR files that it needs to connect to the configuration database.
If you have installed additional software since installing the broker, or
have made manual updates to your CLASSPATH, these might cause the mqsicreateconfigmgr command to
fail.
Solution: Ensure that the DB2 JAR
files, especially db2java.zip, are in your CLASSPATH.
Error message BIP2624 is issued when creating an execution
group
Scenario: When you create an execution group, you get several BIP2624 messages
(MQRC=2012 (MQRC_ENVIRONMENT_ERROR)), and no WebSphere MQ messages
are processed.
Explanation: You have created the broker to run as a WebSphere MQ trusted application (that is, the broker
runs in the same process as the WebSphere MQ queue
manager), but the user ID that you specified does not have the required authority.
Solution: If you request the trusted application option
on the mqsicreatebroker command
by specifying the -t parameter, perform the appropriate
steps for you operating system:
Windows
Using the -i parameter on the mqsicreatebroker command,
specify a service user ID that is a member of WebSphere MQ group mqm.
AIX
The -t parameter is ignored. The broker does not
run as a trusted application on AIX.
Other UNIX systems
Specify the user ID mqm on the -i parameter
on the mqsicreatebroker command.
You do not know what authorities are set as part of the mqsicreateaclentry command
Scenario: You do not know what authorities are set on the
queue manager as part of the mqsicreateaclentry command.
Solution: Use the WebSphere MQdspmqaut command
to check which authorities have been set on a queue manager by the mqsicreateaclentry command. Ensure
that the following authorities are set: