IIB 9 Broker startup problem

IIB 9 Broker startup problem is one of the common troubleshooting task that we normally perform. There could be different set of reasons on why a Broker will report problem during startup.

System logs present in IBM Integration Bus v9 give us a clear picture on what the problem is. Most of the cases log file message provides detailed information and we can easily identify the root cause of the problem.

Some of the reasons that I faced recently are due to,

1. Insufficient privileges while starting the broker

2. On Windows, login id password got changed

3. Java version update

4. Environment variables not set properly

While going through the error messages in logs, I could see BIPXXXX codes that provide me basic message on the error that we are facing.

IBM Integration Bus v9 Knowledge center provides most of these message references here. Below are few problems that I faced recently.

1. Warning messages BIP8288-BIP8297 are shown in the syslog when you start a broker

One or more problems were detected with the ODBC environment on Linux and UNIX systems. Run mqsicvp commands to check where is the problem is as it will provide the result on the command prompt.

2. Error messages AMQ7626 and BIP8048 are displayed when you try to start a broker

As mentioned in Knowledge center, we see this error message when using a broker on a queue manager that is configured for global coordination with Oracle. Start the queue manager manually with the -si flag before starting the broker.

3. You have changed your logon password and cannot start your broker on Windows

Change broker properties by using the command:
mqsichangebroker brokername -i ServiceUserID -a ServicePassword

Restart the broker

4. Error message BIP8875 is issued when you start a broker

This is one of the common problem event that occurs on the command prompt (windows or linux). Error message will be shown on the console where exact details will be provided. Refer to knowledge center link to understand what ezactly the issue is.

Some of the BIPXXXX message references are,

BIP8875W: The component verification for ‘component_name’ has finished, but one or more checks failed.
BIP8877W: The environment verification for component ‘component_name’ has finished, but one or more checks failed.
BIP8883W: The WebSphere MQ verification for component ‘component_name’ has finished, but one or more checks failed.
BIP8885E: Verification failed. Failed to connect to queue manager ‘queue_manager_name’. MQRC: return_code MQCC: completion_code
BIP8887E: Verification failed for queue ‘queue_name’ on queue manager ‘queue_manager_name’ while issuing ‘operation’. MQRC: return_code MQCC: completion_code
BIP8888E: Verification failed. Failed to disconnect from queue manager ‘queue_manager_name’. MQRC: return_code MQCC: completion_code
BIP8892E: Verification failed. The installed Java level ‘level_installed’ does not meet the required Java level ‘level_supported’.
BIP8893E: Verification failed for environment variable ‘variable_name’. Unable to access file ‘file_name’ with user ID ‘user_ID’. Additional information for IBM support: data1 data2.
BIP8895E: Verification failed. Environment variable ‘variable_name’ is incorrect or missing.
BIP8896E: Verification failed. Unable to access the registry with user ID ‘user_ID’. Additional information for IBM support: data1 data2
BIP8897E: Verification failed. Environment variable ‘variable_name’ does not match the component name ‘component_name’.
BIP8903E: Verification failed. The APF Authorization check failed for file ‘file_name’.
BIP8904E: Verification failed. Failed to start file ‘file_name’ with return code ‘return_code’ and errno ‘error_number’.