IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Resolving problems when running commands

Use the advice given here to help you to resolve common problems that can arise when you run commands.

Backing up or restoring the broker returns error BIP1253 or BIP1262

Scenario: An error message is generated when you back up or restore a broker:
- The following message is returned when you run the mqsibackupbroker command:
```
BIP1253E Failed to backup the broker 'broker_name' (error 'error_code')
```
- The following message is returned when you run the mqsirestorebroker command:
```
BIP1262E Could not delete the existing configuration of broker 'broker_name'.
```
Explanation: Both backup and restore commands require read/write access to the files that contain broker configuration data. Access has failed and the command cannot complete its operation successfully.
Solution: Typically, you might see one of these errors if you are running the backup or restore command against an active broker, and a conflict of access has occurred. If your broker is active, use the mqsistop command to stop the broker, and try the operation again.
You might also see one of these errors if the directory to which the command is writing, or from which it is reading, is temporarily inaccessible because of communications or authorization problems. Check that your user ID has access to the directory that you specified in the command.

Scenario: A ReportEvent () message is generated whenever you attempt to run any mqsi* command, The ReportEvent () message is followed by the result of the command itself.
Explanation: The Windows Application Log has become full.
Solution: Clear the Windows Application Log from the Event Viewer.

Scenario: You want to run an mqsi* command using SSL to administer a remote broker over a secured channel. Note, that you can do this only for mqsi* commands that have the -n .broker option.
Solution: In order to connect to a broker using SSL, you must specify the keystore and truststore password for the connection using the IBM_JAVA_OPTIONS environment variable. For example:
```
export IBM_JAVA_OPTIONS=-Djavax.net.ssl.keyStorePassword=MYKEYSTOREPASSWORD 
  -Djavax.net.ssl.trustStorePassword=MYTRUSTSTOREPASSWORD 
```
In the same environment, you must then run the command using the -n option to specify a .broker file that describes the connection you want to establish.

You can export .broker files by using the export option in the IBM® Integration Explorer. To do this, right-click on the secured broker you want to export a .broker file for, and select Export *.broker.

Scenario: You want to run an mqsi* command on AIX® with Stack Execution Disable enabled, but the command times out even if the -w option is set to 360.
Explanation: mqsi* commands attempt to create a JVM with Java™ Native Interface (JNI) calls. Because of Stack Execution Disable, the JVM creation fails. For more information about Stack Execution Disable, see AIX Stack Execution Disable.
Solution: Use the sedmgr command to create exemption records from Stack Execution Disable. For example, for mqsilist:
```
sedmgr c exempt /opt/mqsi/9.0/bin/mqsilist
```
The following commands might be affected by this issue:
- biphttplistener
- bipbroker
- bipservice
- mqsideploy
- mqsilist
- mqsimode
- mqsireloadsecurity
- mqsireportresourcestats
- mqsiwebuseradmin

au16545_.htm |

Last updated Friday, 21 July 2017