| Author |
Message
|
| manishpnp |
 Posted: Mon Jun 06, 2011 8:22 am Post subject: Linear Log - Archive |
 |
|
Apprentice
Joined: 21 Feb 2008
Posts: 46
|
Hello,
WebSphere MQ 7.0.1.3
Linear Logs
/MQHA/QMGMUM/log/QMGMUM/active
I checked the MQ active logs for start queue manager and maintenance using below command.
rcdmqimg -l -m QMGMUM -t qmgr
AMQ7467: The oldest log file required to start queue manager QMGMUM is S0117719.LOG.
AMQ7468: The oldest log file required to perform media recovery of queue manager QMGMUM is S0069321.LOG.
-rw-rw---- 1 mqm mqm 4202496 May 25 23:32 S0069321.LOG
-rw-rw---- 1 mqm mqm 4202496 Jun 06 19:50 S0117719.LOG
Queue manager active logs size (/MQHA/QMGMUM/log/QMGMUM/active) is 200 GB.
The present used size is 197Gb and only 3 GB space is free.
There are multiple logs files available from May 24th to Jun06.
I want to archieve the active logs from 24th May to 30th May (excluding S0069321.LOG - as it is required to start queue manager)
Can you please help me how to archieve the active logs (24-30th May) to make the free space available as only 3GB space is available.
Thanks,
manish |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jun 06, 2011 8:33 am Post subject: Re: Linear Log - Archieve |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| manishpnp wrote: |
| I want to archieve the active logs from 24th May to 30th May (excluding S0069321.LOG - as it is required to start queue manager) |
No you don't. You want to keep all logs from that point as they're required to start the queue manager or you want to take a new image to move that file number to a more recent one.
(you should be doing that on a regular basis anyway)
| manishpnp wrote: |
| Can you please help me how to archieve the active logs (24-30th May) to make the free space available as only 3GB space is available. |
There's a support pac dedicated to this you can find if you try looking for it, along with instructions in the InfoCenter.
If you're using linear logging, you should be doing all of this as a regular scheduled task already.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| manishpnp |
| Posted: Mon Jun 06, 2011 9:23 am Post subject: |
|
|
Apprentice
Joined: 21 Feb 2008
Posts: 46
|
Hi Vitor,
Thanks for quick response.
The present space is available is only 3 GB and it will be 100% fill up in anytime.
Can you please provide the details about taking a new image to move that file number to a more recent one (any command available?).
If it is MS62 Suppor Pack then apply the same will take more time as need to take approval from customer.
Is there any workaround option to free the space from active log partition.
Thanks,
manish |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Jun 06, 2011 9:32 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| manishpnp wrote: |
| Can you please provide the details about taking a new image to move that file number to a more recent one (any command available?). |
Yes there is a command available (you've already used it in fact, but not with the parameter required) and it's listed within the Info Centre, as are alternative commands to provide the information you seek, and there is no work-around - don't even think of copying the logs and manually moving the ones you 'think' are no longer needed.
_________________
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 |
|
|
| Vitor |
| Posted: Mon Jun 06, 2011 9:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| exerk wrote: |
| Yes there is a command available (you've already used it in fact, but not with the parameter required) and it's listed within the Info Centre |
| exerk wrote: |
| don't even think of copying the logs and manually moving the ones you 'think' are no longer needed. |
This is a really, really good way of hosing up your queue manager, especially if your backup strategy is as good as your housekeeping.
And remember if you'd thought about how to manage linear logs at the same time as you decided to use them (i.e. when the queue manager was built) you wouldn't be in this mess, and certainly wouldn't be against this time pressure.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| skoobee |
| Posted: Mon Jun 06, 2011 11:49 am Post subject: |
|
|
Acolyte
Joined: 26 Nov 2010
Posts: 52
|
Sys Admin manual, topic fa14590:
[quote]
Only log files required for queue manager restart, active log files, need to be online. Inactive log files can be copied to an archive medium such as tape for disaster recovery, and removed from the log directory.
[/quote]
So, you can remove all logs up to 117719. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Jun 06, 2011 11:53 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| skoobee wrote: |
Sys Admin manual, topic fa14590:
| Quote: |
Only log files required for queue manager restart, active log files, need to be online. Inactive log files can be copied to an archive medium such as tape for disaster recovery, and removed from the log directory.
|
So, you can remove all logs up to 117719. |
True, but better to force a more recent image into the logs and archive everything backward - should an object require rebuilding the image logs will be immediately available.
_________________
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 |
|
|
| Vitor |
| Posted: Mon Jun 06, 2011 12:05 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| skoobee wrote: |
| So, you can remove all logs up to 117719. |
On the understanding that media recovery would then become impossible.
And the queue manager would whine about that the next time you tried to start it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Jun 06, 2011 12:13 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Vitor wrote: |
| skoobee wrote: |
| So, you can remove all logs up to 117719. |
On the understanding that media recovery would then become impossible. |
Not impossible, merely more protracted. It would involve having to copy back the required logs (see my previous post).
| Vitor wrote: |
| ...And the queue manager would whine about that the next time you tried to start it. |
It might whine, but it would start even if there was a damaged object - unless behaviour has changed in V7.0?
_________________
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 |
|
|
| Vitor |
| Posted: Mon Jun 06, 2011 12:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| exerk wrote: |
| Not impossible, merely more protracted. It would involve having to copy back the required logs (see my previous post). |
Presuming that the "redundant" logs have been backed up before being removed. And yes, I've seen that done, and yes I agree the InfoCenter says what has been quoted in this thread about being "inactive" not "redundant" & being "moved to an archive medium".
| exerk wrote: |
| It might whine, but it would start even if there was a damaged object - unless behaviour has changed in V7.0? |
And the level of whine does correlate to how closely the queue manager logs are being monitored. I'd have a rule that would raise a ticket for that sort of thing, but that's me.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jun 06, 2011 6:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
As the OP was asking about support packs for the management of linear logs,
I wanted to add that we use MS0L and are very happy with it (just make sure you use the temp dir option).
As a piece of advice run "rcdmqimg" at least once a day. It will move your image log forward.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| manishpnp |
| Posted: Mon Jun 06, 2011 11:34 pm Post subject: |
|
|
Apprentice
Joined: 21 Feb 2008
Posts: 46
|
I have taken a new image to move that file number to a more recent one.
rcdmqimg -l -m QMGMUM -t qmgr
Media image for object QMGMUM, type qmgr recorded.
AMQ7467: The oldest log file required to start queue manager QMGMUM is S0110511.LOG.
AMQ7468: The oldest log file required to perform media recovery of queue manager QMGMUM is S0113890.LOG.
-rw-rw---- 1 mqm mqm 4202496 Jun 05 12:50 S0110511.LOG
-rw-rw---- 1 mqm mqm 4202496 Jun 06 22:09 S0113890.LOG
Now we want to housekeep/archive or delete the old logs which are generated from 23rd May to 30th May to free the file system.
Thanks,
manish |
|
| Back to top |
|
|
| skoobee |
| Posted: Tue Jun 07, 2011 12:39 am Post subject: |
|
|
Acolyte
Joined: 26 Nov 2010
Posts: 52
|
Are you sure about those msgs? Look for a later AMQ7467 msg.
The reason that this must be wrong is that you do not have to keep any files before the earliest media recovery log, and according to the msgs the qmgr start log is 3380 extents behind the media recovery log file. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Jun 07, 2011 7:50 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| skoobee wrote: |
Are you sure about those msgs? Look for a later AMQ7467 msg.
The reason that this must be wrong is that you do not have to keep any files before the earliest media recovery log, and according to the msgs the qmgr start log is 3380 extents behind the media recovery log file. |
Who, or what, says it's wrong? It is usual for the media recovery log number to leap-frog the restart log number. Remember, the media recovery log will contain an image of the objects at the moment in time the image was taken, whereas the restart log will contain check-point information and persistent messages. If left long enough without another image being taken, the restart log number will again leap-frog the media log number.
_________________
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 |
|
|
| mvic |
| Posted: Tue Jun 07, 2011 3:58 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
Something very odd is going on.
One June 6 you had:
| Quote: |
| AMQ7467: The oldest log file required to start queue manager QMGMUM is S0117719.LOG. |
And now today you have:
| Quote: |
| AMQ7467: The oldest log file required to start queue manager QMGMUM is S0110511.LOG. |
So your log seems to have gone back in time.
By the way, the rcdmqimg command you used will not necessarily always help much with releasing old log files because you're only storing -t qmgr.
Please check the usage of -t all and this page: http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.amqzag.doc/fa14590_.htm
Now, about why your restart log file is not moving forwards (never mind the fact that it is going backwards, I can't explain that), it might be possible that your qmgr's checkpointing is not working. This would be the sensible explanation for why the restart LSN doesn't move how it should.
It could be time to open a PMR, about the restart LSN issue.
First check whether you have an errors in /var/mqm/errors or your qmgr error logs talking about checkpointing. |
|
| Back to top |
|
|
|
|
