| Author |
Message
|
| Marcus308 |
 Posted: Thu Mar 22, 2012 10:18 am Post subject: Log cleanup and FDC file cleanup. |
 |
|
Novice
Joined: 21 Mar 2012
Posts: 15
|
Question about cleaning up logs here. I have learned the hard way you don't just delete anything in MQ without running the risk of corrupting your message tables.
AIX
MQ 7.0.1.2
I'd like to know how to properly clean up the /var/mqm/errors directory. I have many .FDC files and would like to know how best to clean them up. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Mar 22, 2012 10:24 am Post subject: Re: Log cleanup and FDC file cleanup. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Marcus308 wrote: |
| Question about cleaning up logs here. I have learned the hard way you don't just delete anything in MQ without running the risk of corrupting your message tables. |
That's certainly true for the queue manager logs.
| Marcus308 wrote: |
| I'd like to know how to properly clean up the /var/mqm/errors directory. I have many .FDC files and would like to know how best to clean them up. |
These are not the queue manager logs.
You delete FDCs when you've successfully used their contents to resolve the problems they are reporting. If you have that many FDC files I'd be slightly concerned. The LOG files will roll over by themselves.
The same is true for the errors directory under each queue manager.
The same is not true for the actual queue manager logs, which you mess with at your peril.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Marcus308 |
| Posted: Thu Mar 22, 2012 12:44 pm Post subject: |
|
|
Novice
Joined: 21 Mar 2012
Posts: 15
|
Turns out I have another damaged object problem.
AMQ7472: Object PUBSUBNLCACHE, type damaged.
From what I read it seems I have to delete the object and restart MQ. My question is where do I find the object? |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Mar 22, 2012 2:04 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| Marcus308 wrote: |
Turns out I have another damaged object problem.
AMQ7472: Object PUBSUBNLCACHE, type damaged.
From what I read it seems I have to delete the object and restart MQ. My question is where do I find the object? |
Did you say you had inadvertently deleted some of MQ's important files? Maybe this is an effect from that. You are probably better off if you take the decision to delete the whole queue manager and start again.
Your FDC files are also probably the result of the earlier actions you mentioned. Those FDC files are intended to be sent to IBM when you have called support.
Which files did you delete, by the way? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Mar 22, 2012 2:45 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
FDCs tend to be bulky. If you are short on filesystem space, you can move (archive) FDCs (and traces) elsewhere. Linear logs no longer required for recovery/restart may also be archived.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Mar 22, 2012 3:04 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| bruce2359 wrote: |
| FDCs tend to be bulky. If you are short on filesystem space, you can move (archive) FDCs (and traces) elsewhere. Linear logs no longer required for recovery/restart may also be archived. |
If he hasn't looked already at how to recover the damaged object using rcvrmqobj I don't think he is using linear logs...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Mar 22, 2012 3:41 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
Since the OP referred to
| Quote: |
| /var/mqm/errors directory |
, I figured he meant the AMQERR01.LOG files and FDCs, and not log segments.
The AMQERR01.LOG file grow over time, but get recycled at qmgr restart. If qmgr restart occurs rarely, it is possible for the AMQERR01.LOG to get pretty big. AMQERR02.LOG and AMQERR03.LOG can (should) be archived.
I suspect that some mysterious person cleaned the filesystem with a harsh substance, not knowing what damage it could do.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Mar 22, 2012 3:47 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| bruce2359 wrote: |
| The AMQERR01.LOG file grow over time, but get recycled at qmgr restart. If qmgr restart occurs rarely, it is possible for the AMQERR01.LOG to get pretty big. AMQERR02.LOG and AMQERR03.LOG can (should) be archived. |
These files wrap, and do not grow beyond a pre-configured limit. The default for that limit may have increased recently I think, but it is still not very big (a few MB?). They do not get recycled at qmgr restart, they just get appended.
I agree with the idea to archive them.. this can help in some "what happened, exactly" types of situation. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Mar 22, 2012 3:53 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| mvic wrote: |
| They do not get recycled at qmgr restart, they just get appended. |
More precisely: At restart AMQERR03.LOG vaporizes; 02 is renamed 03; 01 is renamed 02; 01 is created anew.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Mar 22, 2012 4:06 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| bruce2359 wrote: |
| More precisely: At restart AMQERR03.LOG vaporizes; 02 is renamed 03; 01 is renamed 02; 01 is created anew. |
I'm confused.. Do you mean queue manager restart? If so, that's not correct.. test it out.
What you wrote there is what happens when MQ gets to the max length for 01. But as long as it hasn't got to the max length for 01, it keeps writing to 01. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Mar 22, 2012 6:49 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
Hmmmm. I withdraw my comment (after testing). I'm wondering where I got that... an older release? A delusion, possibly.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Mar 23, 2012 12:58 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
And not forgetting that on Windows at least, the size of the queue manager error logs can be specified smaller or larger than the initial value assigned when the queue manager is created.
_________________
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: Fri Mar 23, 2012 4:38 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Marcus308 wrote: |
| From what I read |
Read where?
| Marcus308 wrote: |
| it seems I have to delete the object and restart MQ. |
Possibly in your case, not in all cases.
| Marcus308 wrote: |
| My question is where do I find the object? |
So you have nothing called PUBSUBNLCACHE as a defined object?
Your queue manager is broken. Whatever you deleted last time (when you learned the hard way) is still causing problems. You should consider deleting your queue manager and recreating it.
Or possibly uninstalling WMQ & reinstalling it. In 15 years of WMQ I've seen half a dozen damaged object errors and all were attributible to file system problems and/or OS issues. If you're getting them this frequently, and after you've done something unfortunate, it sounds like there's an underlying issue.
Or not. My 2 cents.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Marcus308 |
| Posted: Fri Mar 23, 2012 5:29 am Post subject: |
|
|
Novice
Joined: 21 Mar 2012
Posts: 15
|
| mvic wrote: |
| Marcus308 wrote: |
Turns out I have another damaged object problem.
AMQ7472: Object PUBSUBNLCACHE, type damaged.
From what I read it seems I have to delete the object and restart MQ. My question is where do I find the object? |
Did you say you had inadvertently deleted some of MQ's important files? Maybe this is an effect from that. You are probably better off if you take the decision to delete the whole queue manager and start again.
Your FDC files are also probably the result of the earlier actions you mentioned. Those FDC files are intended to be sent to IBM when you have called support.
Which files did you delete, by the way? |
In this case no I did not delete any files until it was suggested removing some of the old .FDC was ok to do. Unless there is a way of saving the queues, channels, etc, of the current queue manager deleting the one I currently have is not ideal. The issue with the channel I had seems to have been cleared up.
Last edited by Marcus308 on Fri Mar 23, 2012 5:51 am; edited 1 time in total |
|
| Back to top |
|
|
| Marcus308 |
| Posted: Fri Mar 23, 2012 5:30 am Post subject: |
|
|
Novice
Joined: 21 Mar 2012
Posts: 15
|
| bruce2359 wrote: |
| FDCs tend to be bulky. If you are short on filesystem space, you can move (archive) FDCs (and traces) elsewhere. Linear logs no longer required for recovery/restart may also be archived. |
Not so much short on disk space as some of these FDC files were really old. I deleted those file which were more than 90 days old. There were many 0 byte files from 6 months ago with a .FDC extension. |
|
| Back to top |
|
|
|
|
