| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| XA error on windows with MQ and DB2 |
« View previous topic :: View next topic » |
| Author |
Message
|
| vennela |
 Posted: Thu Aug 18, 2005 8:11 am Post subject: XA error on windows with MQ and DB2 |
 |
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
When I try to start workflow QMGR on a windows box I am getting this error.
| Code: |
The XA resource manager 'DB2 FMCDB' was not available when called for xa_open. The queue manager is continuing without this resource manager.
The XA resource manager 'DB2 FMCDB' 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.
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. |
| Code: |
An exception occurred during an xa_open call to XA resource manager 'DB2 FMCDB'.
An exception has been detected during a call to an XA resource manager. The queue manager will continue after assuming a return code of XAER_RMERR from the call.
An FFST should have been produced which documents the exception. Use this and any further FFSTs to try and determine the reason for the failure. A trace of the problem will be useful to identify the XA flows between the queue manager and the resource manager concerned. MQ has allocated an RMId of 1 to this resource manager. Use this to isolate the flows concerned. First contact the supplier of the resource manager for problem resolution. If however you think that the problem lies within the queue manager then contact your IBM support center. Do not discard any information describing the problem until after it has been resolved. |
db2 is 8.1 with fixpack 9a
MQ CSD 10
Windows 2000.
Workflow 3.6
I tried with the following
DB=FMCDB, toc=p, UID=db2admin, PWD=password and ThreadOfControl is process and
DB=FMCDB, toc=t, UID=db2admin, PWD=password and ThreadOfControl is thread |
|
| 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
|
|
|
|
