| Author |
Message
|
| MQ_guy12 |
 Posted: Wed Nov 21, 2012 7:36 am Post subject: QM not coming up after server failover .. MQV7.0 |
 |
|
Newbie
Joined: 21 Nov 2012
Posts: 3
|
Hello,
We have a clustered environment and installed the MQ V7.0 separately on both the nodes and created the objects as well. Mounted the sandisk as well. Now, when we tried a failover to the other node, the MQ is not coming up. I have pasted below the FDC. Kindly help.
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wed November 21 2012 14:42:45 W. Europe Standard Time |
| UTC Time :- 1353505365.334000 |
| UTC Time Offset :- 60 (W. Europe Standard Time) |
| Host Name :- XXXXXXXXXXXX |
| Operating System :- Windows Ver 6.1 (7) Server Standard x64 Edition, Build |
| 7601: SP1 |
| PIDS :- 5724H7220 |
| LVLS :- 7.0.1.7 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- XY509007 |
| Application Name :- MQM |
| Component :- xcsOpenFileLock |
| SCCS Info :- lib/cs/pc/winnt/amqxnfln.c, 1.14.1.9 |
| Line Number :- 256 |
| Build Date :- Nov 17 2011 |
| CMVC level :- p701-107-111117 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- I:\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Addressing mode :- 32-bit |
| Process :- 00002796 |
| Thread :- 00000001 |
| QueueManager :- ROUTER!V15 |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 2 |
| ConnId(2) QM :- 2 |
| ConnId(3) QM-P :- 2 |
| ConnId(4) App :- 2 |
| Last HQC :- 2.0.0-10148 |
| Last HSHMEMB :- 4.0.0-22612 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (WinNT error 5 from CreateFile.) |
| FDCSequenceNumber :- 0 |
| Comment1 :- WinNT error 5 from CreateFile. |
| |
| Comment2 :- Access is denied. |
| |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Nov 21, 2012 7:45 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
If by 'clustered environment' you mean MSCS clustering, did you follow all the steps within the Info Centre that relate? If you're trying to MSCS-cluster a Multi-Instance queue manager - don't - it's one or the other, not a combination of the two.
It looks like a permissions problem to me.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| MQ_guy12 |
| Posted: Wed Nov 21, 2012 7:53 am Post subject: |
|
|
Newbie
Joined: 21 Nov 2012
Posts: 3
|
| Thanks for the quick reply. We are doing Veritas Clustering. The D drive is the common drive between the two servers and moves to the active node on failover. The mounting of the MQ files was successful. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Nov 21, 2012 7:57 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| MQ_guy12 wrote: |
| Thanks for the quick reply. We are doing Veritas Clustering. The D drive is the common drive between the two servers and moves to the active node on failover. The mounting of the MQ files was successful. |
I have only ever done HA on Windows using MSCS so all I can suggest is that you consult the Veritas documentation.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Nov 21, 2012 1:14 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Active - active may yield better results. Even when properly configured, I've only been able to get active - passive failover to occur hands-off one in ten times. Nine out of ten times, some form of human intervention was required to get the passive instance to come up for operation. The one in ten times it would come up by itself, it took a 'long' time, like 90 or 100 seconds.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 21, 2012 1:37 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| MQ_guy12 wrote: |
| The mounting of the MQ files was successful. |
Guess again.
If you Google that FDC it's the result of WMQ failing to get the locks it needs on the shared disc, either because the file permissions have been mapped incorrectly between the 2 nodes or there are "stale" file locks on the needed files. Speak to your WIndows admins & make sure they've not "corrected" any of the file permissions in the Windows paths WMQ uses, and speak to whoever runs your Vertias install to make sure that's not doing something daft.
To respond indirectly to the newest example of the active / active crusade, if you need to do active / passive failover manually 9 times out of 10, especially under Vertias, you've got it set up wrong. Even MSCS manages between than that, and that's as solid as the rest of the MSoft product line.
I don't want to or expect a restart of the debate on if active / passive is better or worse than active / active. Those interested in the debate (and it's a valuable debate) should consult the forum search facility. Having decided for better or worse to go active / passive, Vertias should do active / passive reliably.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| MQ_guy12 |
| Posted: Thu Nov 22, 2012 1:38 pm Post subject: |
|
|
Newbie
Joined: 21 Nov 2012
Posts: 3
|
Thanks for those suggestions. It got resolved. The issue was with the authority the service account that was used to configure the VCS. It was provided at the cluster level and not at the node level. Once we added the service account at the node level and provided the complete access, the VCS itself brought up the MQ.  |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 23, 2012 5:19 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| MQ_guy12 wrote: |
| It was provided at the cluster level and not at the node level. Once we added the service account at the node level and provided the complete access, the VCS itself brought up the MQ. |
I'm going to put that in the "something daft" category.
Glad you got it resolved.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
