766 WebSphere Information Integrator Q Replication: Fast Track Implementation Scenarios
Basic troubleshooting methodology
The following basic steps are recommended for troubleshooting a problem:
1. Check if Q Capture and Q Apply programs are running on both servers.
2. Check the Q subscriptions states and receive queue states on both servers.
3. Look into Q Apply logs on both servers.
Solve errors highlighted in the log, if any.
4. Investigate the Q Capture logs on both servers.
Solve errors highlighted in the logs, if any.
5. Check the WebSphere MQ queues.
a. Transmit queue's queue depth.
b. Receive queue's queue depth.
c. Ensure listeners are running on both servers.
d. Ensure channels are running on both servers.
Commonly encountered problems
Some of the more commonly encountered problems may be broadly classified
into setup errors and operational errors. These are briefly described here.
Table D-1 and Table D-2 list some of the common setup errors encountered and
the resolution action relating to WebSphere MQ and Q replication, respectively.
These return codes may be retrieved from one or more of the sources listed in
“Troubleshooting tools available” on page 764.
Table D-1 WebSphere MQ common setup errors
Return code Meaning Resolution
2035 MQRC_NOT_AUTHORIZED Make sure that the password file is
created in the APPLY_PATH and has a
correct entry for the source server.
Make sure that the APPLY_PATH and
PASSWORD_FILE are properly set in
the APPLYPARMS table.
2058 MQRC_Q_MGR_NAME_ERROR Check the value of the QMGR in the