| Author |
Message
|
| vinumon |
 Posted: Mon Sep 01, 2014 3:07 am Post subject: unexpected system resource FDC error on multi instance QM |
 |
|
Acolyte
Joined: 06 May 2014
Posts: 59
|
Hi,
We are having 3 queue managers on AIX server, and all are configured as multi instance. There is a broker attached to 2 queue managers.
We encountered an issue in which 1 queue manager(queue manager without broker) failed over successfully to standby node, but the other two queue managers did not failover.
We see FDC files generated , mostly of
Probe Id: AD025000
Component: adiForceFile
Major Errorcode : xecF_E_UNEXPECTED_SYSTEM_RC
Probe Type: MSGAMQ6119
Description: Internal Websphere MQ error occured.
Kindly send your answers as this issue is in PRODUCTION |
|
| Back to top |
|
 |
| MQsysprog |
| Posted: Mon Sep 01, 2014 3:30 am Post subject: |
|
|
Centurion
Joined: 24 Feb 2014
Posts: 116
|
Hello,
I would open a pmr with IBM ,because the the failure is in your production enviroment .
However on the technical db there is an apar :
http://www-01.ibm.com/support/docview.wss?uid=swg1IV47426
which leads us to the idea ,that the originating problem could be in the filesystem ,and here we assume you are at V7 level as minimum .
Good Luck |
|
| Back to top |
|
|
| vinumon |
| Posted: Mon Sep 01, 2014 4:18 am Post subject: |
|
|
Acolyte
Joined: 06 May 2014
Posts: 59
|
The queue manager version is 7.5.0.0 on both active and passive nodes.
How to verify if the issue is in the file system ?
Also , what is the reason that the broker queue manager did not start as active on secondary node? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Sep 01, 2014 4:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| vinumon wrote: |
The queue manager version is 7.5.0.0 on both active and passive nodes.
How to verify if the issue is in the file system ?
Also , what is the reason that the broker queue manager did not start as active on secondary node? |
update to 7.5.0.3 as the fix seems to be in this release.
If the problem persists after upgrade open a PMR.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| vinumon |
| Posted: Mon Sep 01, 2014 5:44 am Post subject: |
|
|
Acolyte
Joined: 06 May 2014
Posts: 59
|
Ok thanks...will upgrade to 7.5.0.3.
But before that , as stated in the APAR, iam not having issues for starting the queue manager manually, However the problem is that the queue manager is not getting started automatically on standby node once the queue manager ended on the active node. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Sep 01, 2014 5:48 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| vinumon wrote: |
Ok thanks...will upgrade to 7.5.0.3.
But before that , as stated in the APAR, i am not having issues for starting the queue manager manually, However the problem is that the queue manager is not getting started automatically on standby node once the queue manager ended on the active node. |
This is never the case. The qmgr is only started automatically if it is part of the reboot procedure of the box (in active or standby mode and you need fix pack 3) (at least in windows).
If the qmgr goes down the fail-over kicks in but you also need an alert to restart the failed box's qmgr so that it will be in stand by.... and of course investigate why it failed over in the first place.
If you have trouble with connectivity to the shared storage you are SOL.
Both primary and fail-over will be down as the shared storage is inaccessible.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
