| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Unable to restart QueueManager |
« View previous topic :: View next topic » |
| Author |
Message
|
| vam |
 Posted: Wed Nov 17, 2010 1:05 pm Post subject: Unable to restart QueueManager |
 |
|
Acolyte
Joined: 16 Mar 2010
Posts: 70
|
Hello All,
I found one of my queue manager got stopped and whhen tried to restart it ,I am getting the flowing message"Log path not valid or inaccessible"
stmqm JCT.JMQ
WebSphere MQ queue manager 'JCT.JMQ' starting.
Log path not valid or inaccessible.
FDC Info:
WebSphere MQ First Failure Symptom Report
=========================================
Date/Time :- Wednesday
Host Name :- xxxxxxxxxxxxxxxxxx
PIDS :- xxxxxxxxxxxx
LVLS :- 6.0.2.0
Product Long Name :- WebSphere MQ for HP-UX (PA-RISC platform)
Vendor :- IBM
Probe Id :- ZX000001
Application Name :- MQM
Component :- ExecCtrlrMain
SCCS Info :- cmd/zmain/amqzxma0.c,
Line Number :- 834
Build Date :- Sep 21 2006
CMVC level :- p600-200-060921
Build Type :- IKAP - (Production)
UserID :- 00008010 (mqm)
Program Name :- amqzxma0_nd
Addressing mode :- 64-bit
Process :- 3384
Thread :- 1
QueueManager :- JCT!JMQ
ConnId(1) IPCC :- 2
ConnId(2) QM :- 2
ConnId(3) QM-P :- 2
ConnId(4) App :- 2
Major Errorcode :- xecF_E_UNEXPECTED_RC
Minor Errorcode :- lpiRC_LOG_LOCATION_INVALID
Probe Type :- MSGAMQ6118
Probe Severity :- 2
Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred
(7064)
FDCSequenceNumber :- 0
Arith1 :- 28772 7064
------------------------------------------------------------------
I went to its log path and found there is no folder for the queue manager in log directory.
Please advice. |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Nov 17, 2010 1:31 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Make sure the file system generally is intact, restore from backup, and trout the idiot that deleted the files.
And apply maintenance - I think that we're up to FixPack 9 or 10 for that version of WMQ.
_________________
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 |
|
|
| KramJ |
| Posted: Fri Nov 19, 2010 9:53 am Post subject: |
|
|
Voyager
Joined: 09 Jan 2006
Posts: 80
Location: Atlanta
|
You can rebuild the log files.
1. su to mqm.
2. Record the logging parameters of the failed queue manager by checking .../qmgrs/<qmgr>/qm.ini. These parameters include the type, number, and size and location of the log files.
3. Create a queue manager called TEMP with identical logging parameters.
4. cd to the queue manager logs directory.
5. Rename the logs directory for the existing queue manager to <qmgr>_old.
6. Rename the TEMP directory to the name of the existing queue manager.
7. cd to …/qmgrs/<qmgr>/
8. Rename the existing queue manager's checkpoint file, amqalchk.fil, to amqalchk.fil_old
9. cd to …/qmgrs/TEMP
10. Copy amqalchk.fil from the TEMP queue manager to the existing queue manager.
11. Delete the TEMP queue manager by running dltmqm TEMP (you will get an error about missing logs)
12. Start the existing queue manager by running /startmqm as root
13. After the queue manager is verified, cleanup the system by deleting amqalchk.fil_old and <qmgr>_old |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Nov 19, 2010 8:48 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| KramJ wrote: |
You can rebuild the log files.
1. su to mqm.
2. Record the logging parameters of the failed queue manager by checking .../qmgrs/<qmgr>/qm.ini. These parameters include the type, number, and size and location of the log files.
3. Create a queue manager called TEMP with identical logging parameters.
4. cd to the queue manager logs directory.
5. Rename the logs directory for the existing queue manager to <qmgr>_old.
6. Rename the TEMP directory to the name of the existing queue manager.
7. cd to …/qmgrs/<qmgr>/
8. Rename the existing queue manager's checkpoint file, amqalchk.fil, to amqalchk.fil_old
9. cd to …/qmgrs/TEMP
10. Copy amqalchk.fil from the TEMP queue manager to the existing queue manager.
11. Delete the TEMP queue manager by running dltmqm TEMP (you will get an error about missing logs)
12. Start the existing queue manager by running /startmqm as root
13. After the queue manager is verified, cleanup the system by deleting amqalchk.fil_old and <qmgr>_old |
I notice that you used /startmqm... That would be a custom script and I am sure that the OP does not have it.
Instead run strmqm with user mqm. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
