| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| When archive mq logs fails when AMQERR01.LOG file is corrupt |
« View previous topic :: View next topic » |
| Author |
Message
|
| dgolding |
 Posted: Thu Aug 19, 2004 7:02 am Post subject: When archive mq logs fails when AMQERR01.LOG file is corrupt |
 |
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
A problem I saw today, don't know if anyone else has experienced it:
The linear log file directory filled up, and an internal MQ process went berzerk and filled up the AMQERR0[1-3].LOG files up with 2102 resource problem messages. Within half-an-hour it had completely filled up the three files.
When we came to run the clean-up Perl script, it looks for the the messages AMQ7467 and AMQ7468 in AMQERR0[N].LOG - which of course was not there. So we have a vicous circle - we can't run the cleanup to free space because the error log is full of error messages!
MQ will only write an AMQ7467/8 message every 1000 or so transactions - but if the log files are full, there is no possibility of these transactions occurring.
I THINK there is some "rcdmqimg" option that will write the AMQ7467 & 8 values into the error log, but couldn't find it....  l
The quick fix is to stop and start the queue manager. On startup it will write a AMQ7467 and AMQ7468 message. NOW run the cleanup script.
Of course, it helps to know why the logs filled up in the first place  |
|
| Back to top |
|
 |
| Nigelg |
| Posted: Thu Aug 19, 2004 7:09 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| There is no option in rcdmqimg which will write the AMQ7476/8 msgs to the error logs; these msgs are only written after a checkpoint. Of course, a checkpoint is taken when the qmgr is stopped, so that is why the quick fix works. |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Aug 19, 2004 8:58 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| I THINK there is some "rcdmqimg" option that will write the AMQ7467 & 8 values into the error log, but couldn't find it.... |
-l
Writes messages containing the names of the oldest log files needed to restart the queue manager and to perform media recovery.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Aug 19, 2004 4:27 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
dgolding, you can also set the MQMAXERRORLOGSIZE variable. On UNIX the biggest you can make it is 1000000. On Windows, I made it 5000000 and it worked.
This way your error logs will hold a lot more info.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
