|
I’m having problems making XA work with MQ 5.3 and Oracle 8.1.7 on AIX 5.1. I created the switch file, added the XAResourceManager stanza to qm.ini and granted the appropriate database privileges.
When I start the QMgr, I get the following in the log: AMQ7604: The XA resource manager 'isgamt06' was not available when called for xa_open. The queue manager is continuing without this resource manager. EXPLANATION: The XA resource manager 'isgamt06' has indicated that it is not available, by returning XAER_RMERR on an xa_open request or XAER_RMFAIL when called for something else. Normally this indicates that the resource manager has been shut down. In this case the resource manager cannot participate in any new transactions. Any in-flight transactions in which it was involved will be backed out, and any transactions in which it is in-doubt will only be resolved when contact with the resource manager is re-established. A further message will be issued when the queue manager has been able to do this. If the problem occurred on an xa_open request, and the resource manager should be available, then there may be a configuration problem. ACTION: Try to establish the reason why the resource manager is unavailable. It may be that an invalid XAOpenString has been defined for the resource manager in the 'qm.ini' configuration file. If this is the case, stop and then restart the queue manager so that any change will be picked up. Alternatively, the queue manager may be reaching a resource constraint with this resource manager. For example, the resource manager may not be able to accommodate all of the queue manager processes being connected at one time, you may need to alter one of its tuning parameters.
I also get a trace file containing: ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'. 110226.158670.1: ORA-03113: end-of-file on communication channel 110226.158670.1: xaolgn: XAER_RMERR; logon failed. ORA-3113.
I tried using the DbgFl parameter and got this additional information in the trace file: xaoopen: return -3
Curiously, If I change the XAOpenString attribute to use SqlNet, everything works.
Can anyone shed any light on this?
CONFIDENTIALITY NOTICE: This E-Mail transmission may contain confidential or legally privileged information that is intended only for the individual(s)or entity(ies) named in the E-Mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this E-Mail is strictly prohibited. If you have received this E-Mail transmission in error, please reply to the sender so that arrangements can be made for proper delivery, after which please delete the message from your inbox. Thank you |
- Re: Transaction coordination with 5.3 and Oracle on AIX 5... Gutekunst, Brant
- Re: Transaction coordination with 5.3 and Oracle on ... Robert Broderick
- Re: Transaction coordination with 5.3 and Oracle on ... Gutekunst, Brant
- Re: Transaction coordination with 5.3 and Oracle on ... Robert Broderick
- Re: Transaction coordination with 5.3 and Oracle on ... Gutekunst, Brant
- Re: Transaction coordination with 5.3 and Oracle on ... Robert Broderick
- Re: Transaction coordination with 5.3 and Oracle on ... Gutekunst, Brant
- Re: Transaction coordination with 5.3 and Oracle on ... Robert Broderick
- Re: Transaction coordination with 5.3 and Oracle on ... Gutekunst, Brant
- Re: Transaction coordination with 5.3 and Oracle on ... Robert Broderick
- Re: Transaction coordination with 5.3 and Oracle on ... Gutekunst, Brant
