| Author |
Message
|
| RaviKrG |
 Posted: Mon Mar 22, 2010 11:37 am Post subject: Queue manager not starting |
 |
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Hi, I am trying to start a queue manager on AIX , MQ6. But whenever I try to start the queue manager it ends up unexpectedly generating some core files. While going through the core files I find the error code as rrcE_MQCONN_FAILED with probe desc as AMQ9508: Program cannot connect to the queue manager.Also I get error code as xecF_E_UNEXPECTED_SYSTEM_RC and probe desc as AMQ6119: An internal WebSphere MQ error has occurred (unlink)
Could any help me getting any idea as to what these kind of issues mean and how can I start my queue manager.
I have also tried the amqiclen command and tried to start the queue manager but it failed with the same reasons. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Mar 22, 2010 12:17 pm Post subject: Re: Queue manager not starting |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| RaviKrG wrote: |
| probe desc as AMQ6119: An internal WebSphere MQ error has occurred |
The probe id will be more informative than the description.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Mon Mar 22, 2010 12:49 pm Post subject: Re: Queue manager not starting |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
|
| Back to top |
|
|
| RaviKrG |
| Posted: Mon Mar 22, 2010 1:44 pm Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Thanks for your updates.
The permissions seems to be fine as I can see the permission to the required files as rw.
And the probe ids are RM185002 for the error code rrcE_MQCONN_FAILED and XY490003 for the error code xecF_E_UNEXPECTED_SYSTEM_RC
I am still searching on this probe ids now. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Mon Mar 22, 2010 2:30 pm Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
can you please paste the FFST and MQ Function stack header .
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Mar 22, 2010 2:57 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| RaviKrG wrote: |
| ... error code xecF_E_UNEXPECTED_SYSTEM_RC |
MQ called an AIX Operating System function and it failed. Its likely to be a system resource problem or not all the MQ installation prerequisites have been met.
_________________
Glenn |
|
| Back to top |
|
|
| mvic |
| Posted: Mon Mar 22, 2010 4:33 pm Post subject: Re: Queue manager not starting |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| RaviKrG wrote: |
| I have also tried the amqiclen command and tried to start the queue manager but it failed with the same reasons. |
amqiclen does not solve this type of failure. In fact it is very rare that it will help to solve any failures. Please don't run it manually unless IBM tell you to. ( For example, see http://www.ibm.com/support/docview.wss?uid=swg21414283 )
The probes, etc., that you are seeing are from FDC files, not core files. A core file is something very different from an FDC file.
This error needs to be reported to IBM.. the FDC files contain information intended to be read by IBM. Please don't make big efforts to search inside them for answers. |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Thu Mar 25, 2010 8:18 am Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Thanks to all for their time and inputs.
Finally came to know that the file system was corrupt and after resolving that issue the queue manager started properly. But could any one tell me how can I know from our end, the symptoms of the file system geting corrupt |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Mar 25, 2010 9:58 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The symptoms of data corruption are varied and many. Data corruption manifests itself in applications behaving badly. The o/s is an application; MQ qmgrs are applications.
Generally, data corruption can arise from defective hardware - like media (bad disk), misbehaving adapter cards; or misbehaving software - like applications; by incorrect permissions allowing uninteded access by miscreant users or applications.
The possibilities seem endless. This is why we create disaster/recovery (business continuation, contingency) plans, AND test them. This is why we make backups of important things. This is why we have security policies, and enforce them with hardware/software solutions.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
