| Author |
Message
|
| QueenBee |
 Posted: Tue May 18, 2004 12:48 pm Post subject: AIX MQ Filesystem Sizes |
 |
|
Apprentice
Joined: 28 May 2003
Posts: 43
Location: Grand Rapids, MICHIGAN
|
We are running MQ5.3 on our AIX boxes and we have filled our /var/mqm/qmgrs/<QMGR> upto 91 percent.
There was one queue that was holding about 80,000 messages. I cleared that queue. However, the /var/mqm/qmgrs/<QMGR> filesystem still is at 91 percent.
How do I tell MQ to recognize that the queues are empty and the space is available?
Help. |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue May 18, 2004 1:55 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Basically, WMQ will release the space when it wants to. There isn't a way to force it to release the space immediately. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Tue May 18, 2004 2:49 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue May 18, 2004 5:00 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Michael, that link refers to freeing up log space. The problem bower is refering to is the queue file, which is also very big if there were that many messages in the queue.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Tue May 18, 2004 10:47 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| QueenBee |
| Posted: Wed May 19, 2004 5:34 am Post subject: Any Ideas |
|
|
Apprentice
Joined: 28 May 2003
Posts: 43
Location: Grand Rapids, MICHIGAN
|
| but this is happening in production and now its upto 94 percent. There should be some way without recycling the queue manager! |
|
| Back to top |
|
|
| fschofer |
| Posted: Wed May 19, 2004 6:01 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi, not the best solution,
but why not simple delete the queue and define a ne one.
Greetings Frank |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed May 19, 2004 6:35 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Well, if you have free space available then maybe it is time to increase the /var file system.
| Code: |
| chfs -a size=new_size_in_blocks /var |
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu May 20, 2004 7:14 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
http://www.developer.ibm.com/tech/faq/individual?oid=1:401:416:47:13625
| Quote: |
WebSphere MQ returns file space to the file system or operating system as its internal scheduling permits. A couple of circumstances that help with this scheduling are:
When the last user closes an empty queue (CURDEPTH=IPPROCS=OPPROCS=0), all except the header (~2KB) is released.
When a checkpoint is taken or the queue manager is stopped and restarted, empty space at the end of the file is released.
|
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| QueenBee |
| Posted: Thu May 20, 2004 7:44 am Post subject: Been there done that |
|
|
Apprentice
Joined: 28 May 2003
Posts: 43
Location: Grand Rapids, MICHIGAN
|
I have restarted the queue manager but it does NOT help. As a workaround, we have increased the /var/mqm/log filesystem a little but that is not a permananet fix.
We have opened a problem ticket with IBM and they came back with shutting the queue manager and doing a dmpmqlog. However, outage is not something we can come up with as this is PRODUCTION!!!!!!!!!!!!
HELP....
Currently we have about 82 files and our AMQERRO1.LOG suggests the file that is the earliest to keep. So we cannot delete any files from this directory to reduce log space.
Our only other option is to rebuild the queue manager with a dummy Queue Manager's logs and restore the mq objects present. But this is not termed as feasible. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu May 20, 2004 7:48 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Did you drill down into the var/mqm/qmgrs/<QMGR> filesystem to find out exactly which file is so big? We are assuming it was that one with all the messages you cleared. Maybe it is another file?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| QueenBee |
| Posted: Thu May 20, 2004 7:57 am Post subject: Clarified |
|
|
Apprentice
Joined: 28 May 2003
Posts: 43
Location: Grand Rapids, MICHIGAN
|
The /var/mqm/qmgrs/<QMGR> directory is OK. Its the /var/mqm/log directory that is filling up now. And it is at 95 percent with no successfull attempts to bring it down.
All the files in this directory are of equal length. Our error.log says that in order to restart the QMGR, it needs a certain file, say X123.LOG.
In normal situations, we would go delete all files earlier to X123.LOG. However, in our case, the X123.LOG is the earliest log. All other log files are later than that and hence we cannot delete any!
So where do we go from here? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu May 20, 2004 8:01 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
It sounds like there is a long running Unit of Work that has the logs tied up, but I would have thought the bounce of the QM would have ended that.
I dunno, if it were me, I would bump that ticket with IBM to a higher severity level and hope they come up with something. Please keep us updated.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu May 20, 2004 8:28 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
If it is an uncommitted message, couldn't you issue:
display qstatus(*) uncom
to find out which queue has uncommitted messages? You could then start looking for processes that have the queue open and figure out who might be guilty? |
|
| Back to top |
|
|
| QueenBee |
| Posted: Thu May 20, 2004 9:24 am Post subject: Nothing |
|
|
Apprentice
Joined: 28 May 2003
Posts: 43
Location: Grand Rapids, MICHIGAN
|
Nope.
The qstatus command comes back with nothing. ALL queues are EMPTY.
Other ideas? |
|
| Back to top |
|
|
|
|
