| Author |
Message
|
| gaurav |
 Posted: Sun Jun 24, 2007 9:38 pm Post subject: AMQ7017: Log Not Available |
 |
|
Novice
Joined: 18 Jun 2007
Posts: 14
Location: Mumbai, India
|
Hi
Acciedently i have deleted all the log files of the queue manager in the locn log\QMName. When i try to restart the QM, an exception is thrown AMQ7017: Log Not Available, as obvious. Is there a solution to this problem? I dont know whether backup for the QM was done or not.
Pls advice.
Thanks in advance.
Gaurav |
|
| Back to top |
|
 |
| DTran |
| Posted: Sun Jun 24, 2007 10:31 pm Post subject: |
|
|
Acolyte
Joined: 11 May 2006
Posts: 62
Location: Amsterdam
|
By deleting the active LOG files your are deleting all the messages in the queue. If you don't have a backup there are 2 things to do.
1. check the FDC files and see which log is missing, and recreate that LOG file. After that you can restart the qmgr. Or
2. delete and recreate the qmgr.
In both way the messages are lost!!!
_________________
There are 10 types of people in this world - those who understand binary and those who don't |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 25, 2007 12:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
You could try the following:
- Define another queue manager of the same name (on a different machine obviously)
- copy the log files from this machine to your failed machine
- restart the failed queue manager.
If it starts, you're lucky. If it starts and you're very lucky, you should find persistent messages will be recovered from the queue files on the disk.
Do not rely on this procedure for future errors. Have procedures in place to recover accidently deleted files.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 25, 2007 12:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| DTran wrote: |
| By deleting the active LOG files your are deleting all the messages in the queue. |
There should be a copy of the persistent messages in the queue files associated with the queue manager.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gaurav |
| Posted: Mon Jun 25, 2007 5:02 am Post subject: |
|
|
Novice
Joined: 18 Jun 2007
Posts: 14
Location: Mumbai, India
|
I have resolved the issue by recreating the Queue manager with its old configurations.
Thanks guys |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 25, 2007 5:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gaurav wrote: |
I have resolved the issue by recreating the Queue manager with its old configurations.
|
Probably the best move if there's nothing in the queues you need. My method's rather a last resort. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| happyj |
| Posted: Mon Jun 25, 2007 5:19 am Post subject: |
|
|
Voyager
Joined: 07 Feb 2005
Posts: 87
|
Does the queue manager you copy the logs from need to have the same
name ? I'm sure we've recovered from a dead qmgr by creating a test qmgr with the same log structure and copying these across. |
|
| Back to top |
|
|
| gaurav |
| Posted: Mon Jun 25, 2007 5:25 am Post subject: |
|
|
Novice
Joined: 18 Jun 2007
Posts: 14
Location: Mumbai, India
|
| i think so, coz the log files contain the name of the queue manager. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 25, 2007 5:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| happyj wrote: |
Does the queue manager you copy the logs from need to have the same
name ? I'm sure we've recovered from a dead qmgr by creating a test qmgr with the same log structure and copying these across. |
I think so to. But go to quite paranoid lengths to avoid having to find out. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bbburson |
| Posted: Mon Jun 25, 2007 6:53 am Post subject: |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
| happyj wrote: |
Does the queue manager you copy the logs from need to have the same
name ? I'm sure we've recovered from a dead qmgr by creating a test qmgr with the same log structure and copying these across. |
No, the queue manager name does not have to be the same, just the log type (LINEAR,CIRCULAR) and log size. This is documented several places as the "cold start" procedure.
Unfortunately I have had to use it twice on real queue managers. Fortunately it works. |
|
| Back to top |
|
|
| dgolding |
| Posted: Mon Jun 25, 2007 6:54 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| The copy queue manager does NOT have to have the same name, just the the exact same logging spec (size and number of primary and secondary log files). It worked for me - twice at least I think |
|
| Back to top |
|
|
| bbburson |
| Posted: Mon Jun 25, 2007 7:00 am Post subject: |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
| dgolding wrote: |
| The copy queue manager does NOT have to have the same name, just the the exact same logging spec (size and number of primary and secondary log files). It worked for me - twice at least I think |
"Number of primary and secondary log files" doesn't even matter. I've created my TEMP queue manager with the bare minimum number of files. The ailing queue manager will sort out the real number of files when it restarts. You do have to grab amqalchk.fil from TEMP queue manager directory.
Disclaimer: actual experience with this procedure under WMQ v5.3 only; I don't think there are any changes under v6. |
|
| Back to top |
|
|
| gaurav |
| Posted: Mon Jun 25, 2007 8:29 pm Post subject: |
|
|
Novice
Joined: 18 Jun 2007
Posts: 14
Location: Mumbai, India
|
if queue manager name doesnt matter, then does that mean that i could use any queue managers log files for any other queue manager to restart it in case if there is an error 7017.
Please clarify. |
|
| Back to top |
|
|
| bbburson |
| Posted: Tue Jun 26, 2007 5:43 am Post subject: |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
You really would not want to do that. The logs for the other queue manager will contain any persistent messages for queues that may or may not exist on the ailing queue manager. Totally unpredictable results if you tried mixing logs from two active queue managers.
The cold start procedure is a last resort only. Don't use it if there is any other way to get your queue manager up and running. If you do have to use it, create a brand new temporary queue manager with the same log file type and size and then DO NOT use that queue manager for any messages before grabbing the log files. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jun 26, 2007 6:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Cold starting a queue manager is something that should only be done under very very very controlled situations, and only very very very rarely.
It should not be done because you THINK it might help. It should not be done because "It worked the last time".
It should only be done, basically, because some panicked or misinformed sysadmin did something wrong and deleted some or all of the active logs.
It should not be done as part of a normal backup/cleanup/archive process. It should not be done as part of any normal process.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
