| Author |
Message
|
| ryandawson |
 Posted: Fri Oct 26, 2007 5:34 am Post subject: MQ Workflow with DB2 on windows AMQ7626 XA resource manager |
 |
|
Newbie
Joined: 26 Oct 2007
Posts: 5
|
There have been threads on problems very similar to this before but I think mine is different. My configuration of workflow was working fine until I fixpacked my db2 install, thus messing up the workflow database. I've since uninstalled and reinstalled mq series and workflow and now I'm getting this error. (Before you ask, I can't afford to revert back to db2 without the fixpack.)
The error in the workflow queue (FMCQM) is AMQ7626. When I try to start it I get:
"WebSphere MQ queue manager 'FMCQM' starting.
AMQ7626: XA resource manager initialization failure."
I'm aware that this can often mean that I have the wrong db2 password or that db2 is misconfigured. But I've checked this and have set up everything exactly as before.
My mq version is 6.0 and workflow version is 3.6. DB2 is version 8.1.13.
Any suggestions extremely welcome. |
|
| Back to top |
|
 |
| ryandawson |
| Posted: Fri Oct 26, 2007 5:39 am Post subject: |
|
|
Newbie
Joined: 26 Oct 2007
Posts: 5
|
|
| Back to top |
|
|
| jmac |
| Posted: Fri Oct 26, 2007 5:40 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I would suggest you open a PMR.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Fri Oct 26, 2007 5:41 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
|
| Back to top |
|
|
| ryandawson |
| Posted: Fri Oct 26, 2007 5:41 am Post subject: |
|
|
Newbie
Joined: 26 Oct 2007
Posts: 5
|
|
| Back to top |
|
|
| Gaya3 |
| Posted: Fri Oct 26, 2007 5:44 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Do not ignore this too, thats the reason i told you to check the qmgr logs
you will get a good clarity about the error.
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| ryandawson |
| Posted: Fri Oct 26, 2007 5:52 am Post subject: |
|
|
Newbie
Joined: 26 Oct 2007
Posts: 5
|
I started out trying to get it to work with 6.0. I've since fixpacked mq up to 6.0.2.2 but still no luck.
Will get back to you shortly with the error log details. |
|
| Back to top |
|
|
| ryandawson |
| Posted: Fri Oct 26, 2007 6:17 am Post subject: |
|
|
Newbie
Joined: 26 Oct 2007
Posts: 5
|
The error log doesn't really add anything:
"26/10/2007 14:20:10 - Process(2896.3) User(MUSR_MQADMIN) Program(amqmsrvn.exe)
AMQ7880: Error code 71 starting FMCQM/Queue Manager WebSphere MQ service.
EXPLANATION:
The service was unable to start FMCQM/Queue Manager. The error message reported
was as follows: WebSphere MQ queue manager 'FMCQM' starting. AMQ7626: XA
resource manager initialization failure. Refer to the error log for more
information.
ACTION:
Use WebSphere MQ Explorer to investigate why the service could not begin. If
recovery for this service is active, MQ will attempt to recover. "
However, the event viewer has more to say:
"WebSphere MQ could not load the XA switch load file for resource manager 'DB2 FMCDB'.
An error has occurred loading XA switch file d:\ibm\websphere mq workflow\db2swit\db2swit.dll. 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.
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." |
|
| Back to top |
|
|
| hos |
| Posted: Fri Oct 26, 2007 6:33 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
as John recommended, you should
- apply the latest MQWF Service Pac #5
- open a PMR if the problem persists.
If it is an option for you, you could re-install MQWF (leaving the DB untouched). It seems that your switch file settings got ouf of sync. |
|
| Back to top |
|
|
| vennela |
| Posted: Sat Oct 27, 2007 12:21 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Check the workflow installation guide.
In the newer versions, we have to have the MQ user in DB2 groups or vice versa. I don't remember.
This problem has been because of that |
|
| Back to top |
|
|
| spidy |
| Posted: Sun Nov 11, 2007 3:38 pm Post subject: |
|
|
Acolyte
Joined: 04 Oct 2006
Posts: 50
|
| Vennela is right. I had similar problem sometime back. Its the issue with the user's authority. I dont remember myself too but you can check some running machine installed with these products for the user's setup/properties. |
|
| Back to top |
|
|
| sarasu |
| Posted: Tue Nov 13, 2007 1:20 pm Post subject: |
|
|
Master
Joined: 02 Feb 2006
Posts: 229
|
From the Admin Guide you will find how to setup this.
amqmdain reg TEST -c add -s XAResourceManager\Sample -v SwitchFile=sf1 amqmdain reg TEST -c add -s XAResourceManager\Sample -v ThreadOfControl=THREAD amqmdain reg TEST -c add -s XAResourceManager\Sample -v XAOpenString=openit amqmdain reg TEST -c add -s XAResourceManager\Sample -v XACloseString=closeit |
|
| Back to top |
|
|
|
|
