政府机关中间件
调用XAResource后引起的AMQ7626
近日，小菜偶搭建某应用时 配置使用了XAResource 启动队列管理器 报错AMQ7626
查看error信息：
07/19/10 14:13:31
AMQ6120: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 675 --------------------------------------------------------
07/19/10 14:13:31
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
QMXX.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 18508.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 709 --------------------------------------------------------
07/19/10 14:13:31
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 20806010. This message is
issued in association with other messages.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 675 --------------------------------------------------------
07/19/10 14:13:31
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
QMXX.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 18508.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 709 --------------------------------------------------------
07/19/10 11:20:01
AMQ7622: WebSphere MQ could not load the XA switch load file for resource
manager 'Oracle dbinfoTEST'.
EXPLANATION:
An error has occurred loading XA switch file /opt/mqm/samp/xatm/oraswit. If the
error occurred during startup then the queue manager will terminate. At all
other times the queue manager will continue without this resource manager
meaning that it will no longer be able to participate in global transactions.
The queue manager will also retry the load of the switch file at regular
intervals so that the resource manager will be able to participate again should
the load problem be resolved.
ACTION:
Look for a previous message outlining the reason for the load failure. Message
AMQ6175 is issued if the load failed because of a system error. If this is the
case then follow the guidance given in message AMQ6175 to resolve the problem.
In the absence of prior messages or FFST information related to this problem
check that the name of the switch load file is correct and that it is present
in a directory from which it can be dynamically loaded by the queue manager.
The easiest method of doing this is to define the switch load file as a
fully-qualified name. Note that if the queue manager is still running it will
need to be restarted in order that any changes made to its configuration data
can be picked up.
----- amqtrmca.c : 254 --------------------------------------------------------
百思不得其解。后来注意到日志中的“/opt/mqm/samp/xatm/oraswit” 针对IBM相关文档
发现需要对oraswit进行重建
重建方法：在/opt/mqm/samp/xatm/目录下 make -f xaswit.mak oraswit (root用户）如果是DB2用户 就对db2swit 重建
重建前请注意export oracle_home的路径
再次启动队列管理器 成功
以上问题各位老鸟也许早已心知肚明。小菜这里发出来是给一些像小菜一想的新手提供参考~~~惭愧
查看error信息：
07/19/10 14:13:31
AMQ6120: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 675 --------------------------------------------------------
07/19/10 14:13:31
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
QMXX.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 18508.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 709 --------------------------------------------------------
07/19/10 14:13:31
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 20806010. This message is
issued in association with other messages.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 675 --------------------------------------------------------
07/19/10 14:13:31
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
QMXX.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 18508.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 709 --------------------------------------------------------
07/19/10 11:20:01
AMQ7622: WebSphere MQ could not load the XA switch load file for resource
manager 'Oracle dbinfoTEST'.
EXPLANATION:
An error has occurred loading XA switch file /opt/mqm/samp/xatm/oraswit. If the
error occurred during startup then the queue manager will terminate. At all
other times the queue manager will continue without this resource manager
meaning that it will no longer be able to participate in global transactions.
The queue manager will also retry the load of the switch file at regular
intervals so that the resource manager will be able to participate again should
the load problem be resolved.
ACTION:
Look for a previous message outlining the reason for the load failure. Message
AMQ6175 is issued if the load failed because of a system error. If this is the
case then follow the guidance given in message AMQ6175 to resolve the problem.
In the absence of prior messages or FFST information related to this problem
check that the name of the switch load file is correct and that it is present
in a directory from which it can be dynamically loaded by the queue manager.
The easiest method of doing this is to define the switch load file as a
fully-qualified name. Note that if the queue manager is still running it will
need to be restarted in order that any changes made to its configuration data
can be picked up.
----- amqtrmca.c : 254 --------------------------------------------------------
百思不得其解。后来注意到日志中的“/opt/mqm/samp/xatm/oraswit” 针对IBM相关文档
发现需要对oraswit进行重建
重建方法：在/opt/mqm/samp/xatm/目录下 make -f xaswit.mak oraswit (root用户）如果是DB2用户 就对db2swit 重建
重建前请注意export oracle_home的路径
再次启动队列管理器 成功
以上问题各位老鸟也许早已心知肚明。小菜这里发出来是给一些像小菜一想的新手提供参考~~~惭愧