MQSeries.net :: View topic

ramchandmca · Posted: Mon Jul 19, 2010 4:24 am Post subject:

Hi All,
We are facing a problem in bringing up the queue manager automatically after the reboot of 2000 server..
Operating system : 2000 server with service pack 4
MQ version : 6.0.2.1
The OS will be rebooted every week end as part of their maintenance activity....
Usually the queue manager used to come back automatically once the server comes up....
Two weeks back there was an update in 2000 server, from there on MQ queue manager is failing to pick automatically..

I can see a FDC file generated with the below details:
|[b] Probe Id :- RM185002 |
| Application Name :- MQM |
| Component :- rrmInitRepos |
| SCCS Info :- cmd/remote/amqrrmfa.c, 1.414.1.21 |
| UserID :- MUSR_MQADMIN |
| Process Name :- D:\WebSphere MQ\bin\amqrrmfa.exe
| Major Errorcode :- rrcE_MQCONN_FAILED |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9508

MQM Function Stack
rrmMain
rrmRepository
rrmInitRepos
xcsFFST

Google directed me to a fix pack 6.0.2.6, but I am not clear but not sure will it resolve my issue

From the logs :

17/07/2010 20:00:10 - Process(5260.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ8004: WebSphere MQ queue manager 'MQ0U4' ended.

EXPLANATION:
WebSphere MQ queue manager 'MQ0U4' ended.
ACTION:
None.
-------------------------------------------------------------------------------
17/07/2010 20:00:14 - Process(5220.1934) User(MUSR_MQADMIN) Program(amqrmppa.exe)
AMQ9542: Queue manager is ending.

EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrmssa.c : 2385 -------------------------------------------------------
17/07/2010 20:04:48 - Process(2148.2) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
AMQ5037: The Queue Manager task 'LOGGER-IO' has started.

EXPLANATION:
The Utility Task Manager, processId(0) type(2148), has started the LOGGER-IO
task.
ACTION:
None.
-------------------------------------------------------------------------------
17/07/2010 20:04:49 - Process(2104.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ7229: 5 log records accessed on queue manager 'MQ0U4' during the log replay
phase.

EXPLANATION:
5 log records have been accessed so far on queue manager MQ0U4 during the log
replay phase in order to bring the queue manager back to a previously known
state.
ACTION:
None.
-------------------------------------------------------------------------------
17/07/2010 20:04:49 - Process(2104.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ7230: Log replay for queue manager 'MQ0U4' complete.

EXPLANATION:
The log replay phase of the queue manager restart process has been completed
for queue manager MQ0U4.
ACTION:
None.
-------------------------------------------------------------------------------
17/07/2010 20:04:50 - Process(2104.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ7231: 0 log records accessed on queue manager 'MQ0U4' during the recovery
phase.

EXPLANATION:
0 log records have been accessed so far on queue manager MQ0U4 during the
recovery phase of the transactions manager state.
ACTION:
None.
-------------------------------------------------------------------------------
17/07/2010 20:04:50 - Process(2104.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ7232: Transaction manager state recovered for queue manager 'MQ0U4'.

EXPLANATION:
The state of transactions at the time the queue manager ended has been
recovered for queue manager MQ0U4.
ACTION:
None.
-------------------------------------------------------------------------------
17/07/2010 20:04:50 - Process(2104.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ7233: 0 out of 0 in-flight transactions resolved for queue manager 'MQ0U4'.

EXPLANATION:
0 transactions out of 0 in-flight at the time queue manager MQ0U4 ended have
been resolved.
ACTION:
None.
-------------------------------------------------------------------------------
17/07/2010 20:04:51 - Process(2148.3) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
AMQ5037: The Queue Manager task 'CHECKPOINT' has started.

EXPLANATION:
The Utility Task Manager, processId(0) type(2148), has started the CHECKPOINT
task.
ACTION:
None.
-------------------------------------------------------------------------------
17/07/2010 20:04:52 - Process(2104.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ8003: WebSphere MQ queue manager 'MQ0U4' started.

EXPLANATION:
WebSphere MQ queue manager 'MQ0U4' started.
ACTION:
None.
-------------------------------------------------------------------------------
17/07/2010 20:04:53 - Process(2148.4) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
AMQ5037: The Queue Manager task 'ASYNCQ' has started.

EXPLANATION:
The Utility Task Manager, processId(0) type(2148), has started the ASYNCQ task.
ACTION:
None.
-------------------------------------------------------------------------------
17/07/2010 20:04:53 - Process(2148.5) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
AMQ5037: The Queue Manager task 'EXPIRER' has started.

EXPLANATION:
The Utility Task Manager, processId(0) type(2148), has started the EXPIRER
task.
ACTION:
None.
-------------------------------------------------------------------------------
17/07/2010 20:05:15 - Process(2412.1) User(MUSR_MQADMIN) Program(amqrrmfa.exe)
AMQ9410: Repository manager started

EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
17/07/2010 20:05:16 - Process(2412.1) User(MUSR_MQADMIN) Program(amqrrmfa.exe)
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'MQ0U4' failed with reason code 2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrrmfa.c : 3190 -------------------------------------------------------
17/07/2010 20:05:16 - Process(2412.1) User(MUSR_MQADMIN) Program(amqrrmfa.exe)
AMQ9409: Repository manager ended abnormally.

EXPLANATION:
The repository manager ended abnormally.
ACTION:
Look at previous error messages for the repository manager in the error files
to determine the cause of the failure.
----- amqrrmfa.c : 4090 -----------------

any valuable input is much appreciated...