Oracle9iAS InterConnect Adapter for MQ Series Installation and User's Guide Release 2 (9.0.2) Part Number A95443-01 |
|
This chapter provides answers to frequently asked questions about the MQ Series adapter. This chapter discusses the following topics:
The following questions address installation and other concepts of the MQ Series adapter.
View the oai.txt
file located in the appropriate timestamped subdirectory of the MQ Series adapter log directory:
Platform | Directory |
---|---|
UNIX |
|
Windows |
|
Inspect the exceptions in the oailog.txt
file. The exceptions provide information about what went wrong. One reason is that the MQ Series adapter cannot connect to the repository. Make sure the repository is started properly and the MQ Series adapter connects to the repository once it is started properly. You do not need to restart the MQ Series adapter.
The installer overwrites previous installations of the MQ Series adapter if it is installed a second time in the same Oracle home. However, multiple Oracle homes can exist on one machine and have one MQ Series adapter installed in each Oracle home. An Oracle home can be created by installing the Oracle8i client in different locations. When the MQ Series adapter is installed a second time, choose an Oracle home different from where the first MQ Series adapter is installed.
The following are design time questions for the MQ Series adapter.
The MQ Series adapter caches the information from iStudio that is stored in the repository locally for better performance. If you change something in iStudio and want to see the change in the runtime, you need to stop the MQ Series adapter, delete the MQ Series adapter cache files, and restart the MQ Series adapter.
The MQ Series adapter has a persistence directory located in the MQ Series adapter directory. Deleting this directory when the MQ Series adapter has been stopped should make it obtain the new metadata from the repository when started.
In order to encrypt any values specified in an .ini
file, complete the following steps:
encrypt
utility in $OAI_HOME/bin
directory to encrypt the above value.
.ini
file with encrypted_
.
To encrypt the password for the mq.default.password
parameter, replace mq.default.password=mqm
with the following:
encrypted_mq.default.password=112411071071106510801094108410731070107110811069
Look up the error code in the IBM MQ Series for Java guide Messages Appendix and correct any spelling mistakes for the MQ Series connection information in adapter.ini
. The following lists some common error codes:
2009 MQRC_CONNECTION_BROKEN
--The connection to the queue manager has been lost. This can occur because the queue manager has ended. All previous handles are now invalid, so the MQ Series adapter should be restarted.
2030 MQRC_MSG_TOO_BIG_FOR_Q
--The message length is greater than the maximum for the queue. Increase MaxMsgLength
for the queue (MQ Series Administrator).
2031 MQRC_MSG_TOO_BIG_FOR_Q_MGR
--The message length is greater than the maximum allowed by the remote queue manager. This reason also occurs if a channel, through which the message is to pass, has restricted the maximum message length to a value that is actually less than that supported by the queue manager and the message length is greater than this value.
2035 MQRC_NOT_AUTHORIZED
--The user is not authorized to perform the operation attempted. Make sure the mq.default.user
and mq.default.password
parameters in adapter.ini
are correct.
More error codes can be found at the following url: http://www-4.ibm.com/software/ts/mqseries/library/manuals/csqfao/CSQFAO1P.HTM
.
The means that some outbound messages received from MQ Series did not parse successfully with any of the registered D3L files. Either one or more D3L files should be corrected or the MQ Series sending agent, which enqueued the message on the outbound queue, should correct the messages so they conform to one of the D3L files. If you configure the mq.default.receiver.exception.uri
parameter in the adapter.ini
file, the 'failed' messages will be enqueued on the configured exception queue.
"MQMessageSender_run
: The following exception occurred while invoking oracle.oai.agent.adapter.sdk.Agent.createMessageObject(xml)
. If the Published Message Type in iStudio was XML, try instead to use the Message Type Generic, setting the Object name to be the root element of the XML document."
The error message essentially also provides the solution to this problem.
This is a benign warning message from the MQ Series Java layer which can be avoided by adding the /opt/mqm/java/lib
directory to the Java CLASSPATH before starting the MQ Series adapter (modifying the start
script).
|
Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|