| Author |
Message
|
| boca1 |
 Posted: Sun Feb 10, 2008 10:34 am Post subject: Deleted Queue Manager logs |
 |
|
Newbie
Joined: 10 Feb 2008
Posts: 2
|
Can anyone help us in finding the solution for this peculiar problem.
By mistakenly i took the back up and deleted the log files that are in /var/mqm/logs while the queue manager was running and stopped the queue manager .
And i was trying to start the queue manager but it is saying that
>mqsistart MAZDA_BRK
Log not available.
So i replaced all the back up log files in the /var/mqm/logs/(QM)/active.
and again i tried starting the queue manager but iam getting the same problem.
Could anyone help me getting this queue manager starting. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Feb 10, 2008 5:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Create another qmgr with the same name and logging characteristics on a different machine.
Copy the full /var/mqm/logs/QMGR directory to the machine with the problem.
Restart the qmgr with the problem. If it works delete the qmgr you created to fix the problem....
Understand that this is not the officially sanctioned answer. That answer would be delete and recreate the qmgr...
This should however allow you to keep messages already in your queues.
You will have to reset all channels (seqnum).
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| EddieA |
| Posted: Mon Feb 11, 2008 9:46 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| fjb_saper wrote: |
Create another qmgr with the same name and logging characteristics on a different machine.
Copy the full /var/mqm/logs/QMGR directory to the machine with the problem.
Restart the qmgr with the problem. If it works delete the qmgr you created to fix the problem.... |
Make sure that you only ever have one of these QMs active at any one time
| fjb_saper wrote: |
You will have to reset all channels (seqnum). |
Why. The Sequence numbers are kept in a queue, which will remain intact.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Feb 11, 2008 10:15 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Understanding that this is not an official or even approved way of solving this....why would the dummy QM need the same name? Nothing in the logs has the QM name, right?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Feb 11, 2008 4:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| PeterPotkay wrote: |
| Understanding that this is not an official or even approved way of solving this....why would the dummy QM need the same name? Nothing in the logs has the QM name, right? |
Never tried it giving a different name to the qmgr... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dcjs |
| Posted: Mon Feb 11, 2008 5:44 pm Post subject: |
|
|
Acolyte
Joined: 10 Nov 2006
Posts: 53
Location: IBM Bangalore
|
I tried in the same way by creating the queue manager in another system with the same name and took the back up of the logs from C:\IBM\WebSphereMQ\errors and C:\IBM\WebSphereMQ\log\MAZDA_BRK\active.
and copied those files into the existing queue manager file system.
When i tried to sart the queue manager iam getting the same error.
Logs not found
_________________
TRY TRY UNTIL U SUCCEED |
|
| Back to top |
|
|
| csmith28 |
| Posted: Tue Feb 12, 2008 4:08 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
If I were you, I would just dltmqm and create a new instance of the MQManager.
I hope that you recently created a backup image of this MQManager using saveqmgr.
One thing you may have done wrong above is you need to go look at the /var/mqm/qmgrs/<QMGRNAME>/qm.ini and make sure the QManager you created on the other sever has the same amount of logs. Both Primary and secondary.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Feb 12, 2008 9:52 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| dcjs wrote: |
| C:\IBM\WebSphereMQ\errors |
Not necessary. Those will be recreated as required.
| dcjs wrote: |
| C:\IBM\WebSphereMQ\log\MAZDA_BRK\active. |
You also need C:\IBM\WebSphereMQ\log\MAZDA_BRK\amqhlctl.lfh
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| KramJ |
| Posted: Tue Feb 12, 2008 11:04 am Post subject: |
|
|
Voyager
Joined: 09 Jan 2006
Posts: 80
Location: Atlanta
|
Follow these step to rebuild the logs:
1. 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.
2. Create a queue manager called TEMP with identical logging parameters.
3. cd to the queue manager logs directory.
4. Rename the logs directory for the existing queue manager to <qmgr>_old.
5. Rename the TEMP directory to the name of the existing queue manager.
6. cd to …/qmgrs/<qmgr>/
7. Rename the existing queue manager's checkpoint file, amqalchk.fil, to amqalchk.fil_old
8. cd to …/qmgrs/TEMP
9. Copy amqalchk.fil from the TEMP queue manager to the existing queue manager.
10. Delete the TEMP queue manager by running dltmqm TEMP (you will get an error about missing logs)
11. Start the existing queue manager.
12. After the queue manager is verified, cleanup the system by deleting amqalchk.fil_old and <qmgr>_old |
|
| Back to top |
|
|
| broker_new |
| Posted: Tue Feb 12, 2008 6:32 pm Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
It worked for me too if we follow the above procedure
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| dcjs |
| Posted: Tue Feb 12, 2008 6:35 pm Post subject: |
|
|
Acolyte
Joined: 10 Nov 2006
Posts: 53
Location: IBM Bangalore
|
Thank you very much for all who replied to my issue atlast iam able to start the queue manager.
_________________
TRY TRY UNTIL U SUCCEED |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Feb 13, 2008 1:14 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| chrisgclark |
| Posted: Fri Mar 12, 2010 2:56 am Post subject: |
|
|
Apprentice
Joined: 26 Mar 2009
Posts: 35
|
Hi,
I was getting a 'AMQ7017: Log not available' error when starting one of our queue managers. Looking in the queue manager error file, the last linear log the queue manager needs is in the correct location but the queue manager won't start.
I tried KramJ's procedure but the queue manager still wouldn't start. I then copied over qmstatus.ini and amqalchk.fil from our TEMP queue manager. These files and the new logs allowed the queue manager to then start.
Thought I'd add this incase anyone has the same problem.
Chris |
|
| Back to top |
|
|
|
|
