|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Error At xa_recover entry point. |
« View previous topic :: View next topic » |
Author |
Message
|
Abraham Issac |
Posted: Thu May 30, 2002 7:33 am Post subject: Error At xa_recover entry point. |
|
|
 Newbie
Joined: 24 May 2002 Posts: 5 Location: Mumbai
|
Hi,
I am getting following error when queue manager is started with XA Resource Stanza. Please reply if u can put some light on it.
AMQ7605: The XA resource manager Oracle trdg.dev2 has returned an
unexpected return code -3, when called for xa_recover.
EXPLANATION:
MQSeries received an unexpected return code when calling XA resource manager
Oracle trdg.dev2 at its xa_recover entry point. This indicates an internal
error, either within MQSeries or the resource manager.
ACTION:
Try to determine the source of the error. A trace of the failure could be used
to look at the XA flows between MQSeries and the resource manager. MQSeries
has allocated an RMId of 1 to this resource manager. This will be useful when
isolating the flows associated with the resource manager concerned. If the
error occurs on an xa_commit or xa_rollback request, the queue manager will not
attempt to redeliver the commit or rollback instruction for this transaction,
until after the queue manager has been restarted. The transaction indoubt is
identified by the following XID of X''. If you think that the error lies within
the queue manager, contact your IBM support center. Do not discard any
information describing the problem until after the problem has been resolved. _________________ _____________
Warm Regards,
Abraham. |
|
Back to top |
|
 |
Pavan Kumar PNV |
Posted: Wed Aug 08, 2007 2:03 am Post subject: Getting same error |
|
|
 Acolyte
Joined: 03 Feb 2007 Posts: 66
|
We are having the same error now. Can you please tell me what did you do to get over it?
I have tried to connect to this database from other newly created queue managers as well, but still the problem persists.
I've read somewhere that we need to clear out on GRANT SELECT ON DBA_PENDING_TRANSACTIONS TO PUBLIC.
Anything else we can try to resolve this issue? |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|