MQSeries.net :: View topic

rahoor · Posted: Thu Mar 01, 2007 10:01 am Post subject: Removing linear logfiles

PROBLEM:
Running MQ 6.0.2.0 on SunOS 5.8.
Queue manager crashes appear to coincide with the time linear log files are zipped.

QUESTION:
Can I remove archivable log files when queue manager is running even though lsof shows open file handles to all log files?

BACKGROUND

I run
rcdmqimg -z -l -t MQAPP02 -t all '*'

and see in the AMQERR01.LOG that
AMQ7467: The oldest log file required to start queue manager MQAPP02 is S0000245.LOG.
...
The oldest log file required to perform media recovery of queue
manager MQAPP02 is S0000245.LOG.
...

However lsof reports that AMQZMUC0 has open file handles to all the linear logs, including those that are ready for backup:

bash-2.03$ lsof /var/mqm/log/MQAPP02/active/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
amqzmuc0 16438 mqm 5uR VREG 118,6 16785408 298500 /app/log/MQAPP02/active/S0000245.LOG
amqzmuc0 16438 mqm 6uR VREG 118,6 16785408 298501 /app/log/MQAPP02/active/S0000246.LOG
amqzmuc0 16438 mqm 7uR VREG 118,6 16785408 298502 /app/log/MQAPP02/active/S0000247.LOG
amqzmuc0 16438 mqm 8uR VREG 118,6 16785408 298503 /app/log/MQAPP02/active/S0000248.LOG
amqzmuc0 16438 mqm 9uR VREG 118,6 16785408 298505 /app/log/MQAPP02/active/S0000249.LOG
amqzmuc0 16438 mqm 10uR VREG 118,6 16785408 298509 /app/log/MQAPP02/active/S0000250.LOG
amqzmuc0 16438 mqm 11uR VREG 118,6 16785408 298510 /app/log/MQAPP02/active/S0000251.LOG
amqzmuc0 16438 mqm 12uR VREG 118,6 16785408 298511 /app/log/MQAPP02/active/S0000252.LOG
amqzmuc0 16438 mqm 13uR VREG 118,6 16785408 298514 /app/log/MQAPP02/active/S0000253.LOG
amqzmuc0 16438 mqm 14uR VREG 118,6 16785408 298516 /app/log/MQAPP02/active/S0000254.LOG
amqzmuc0 16438 mqm 15uR VREG 118,6 16785408 298507 /app/log/MQAPP02/active/S0000255.LOG
amqzmuc0 16438 mqm 16uR VREG 118,6 16785408 298497 /app/log/MQAPP02/active/S0000256.LOG
amqzmuc0 16438 mqm 17uR VREG 118,6 16785408 298506 /app/log/MQAPP02/active/S0000257.LOG
amqzmuc0 16438 mqm 18uR VREG 118,6 16785408 298512 /app/log/MQAPP02/active/S0000258.LOG
amqzmuc0 16438 mqm 19uR VREG 118,6 16785408 298515 /app/log/MQAPP02/active/S0000259.LOG
amqzmuc0 16438 mqm 20uR VREG 118,6 16785408 298518 /app/log/MQAPP02/active/S0000260.LOG
amqzmuc0 16438 mqm 21uR VREG 118,6 16785408 298519 /app/log/MQAPP02/active/S0000261.LOG
amqzmuc0 16438 mqm 22uR VREG 118,6 16785408 298824 /app/log/MQAPP02/active/S0000262.LOG
amqzmuc0 16438 mqm 23uR VREG 118,6 16785408 298825 /app/log/MQAPP02/active/S0000263.LOG

Some of these files are older than others, although that should not directly play into this scenario:

bash-2.03$ ls -ltr /var/mqm/log/MQAPP02/active
total 671632
-rw-rw---- 1 mqm mqm 16785408 Jan 9 17:44 S0000250.LOG
-rw-rw---- 1 mqm mqm 16785408 Jan 9 17:44 S0000249.LOG
-rw-rw---- 1 mqm mqm 16785408 Jan 9 17:44 S0000248.LOG
-rw-rw---- 1 mqm mqm 16785408 Jan 9 17:44 S0000247.LOG
-rw-rw---- 1 mqm mqm 16785408 Jan 9 17:44 S0000246.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:25 S0000251.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:25 S0000253.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:25 S0000252.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:25 S0000254.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:25 S0000255.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:25 S0000257.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:25 S0000256.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:25 S0000258.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:26 S0000259.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:26 S0000260.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:26 S0000261.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:26 S0000262.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 26 10:26 S0000263.LOG
-rw-rw---- 1 mqm mqm 16785408 Feb 28 19:56 S0000264.LOG
-rw-rw---- 1 mqm mqm 16785408 Mar 1 12:45 S0000245.LOG

I have read the post on plan to use MS67 http://www-1.ibm.com/support/docview.wss?uid=swg24006603
which does not seem to require the shutting down of the queue manager to run (?)

I would rather be safe than sorry by shutting down qmgr first, before removing files, however being safe also implies understanding what is going on with the MQ open file handles in this case?

thanks in advance!