Author |
Message
|
matth |
Posted: Fri Mar 20, 2009 12:55 pm Post subject: Troubles after rcdmgimg |
|
|
Apprentice
Joined: 13 Feb 2007 Posts: 44 Location: Brazil
|
Hi:
I´ve a trouble with our WMQ 5.3 CSD14 (Yes, It´s old, but I can´t change it) running on Windows 2003 machine.
We was making an script to clean LOGs directory. So, after running rcdmqimg a few times, the Queue Manager hangs. Command used was:
Code: |
rcdmqimg -l -m %QM% -t * *
|
Tries to startup resulted error AMQ6767.
Before this, I´ve seen these strange behavior on logs:
Code: |
20/3/2009 12:31:38
AMQ7467: O arquivo de registro mais antigo necessário para iniciar o
gerenciador de fila QM.04866275.01 é S0002799.LOG.
-------------------------------------------------------------------------------
20/3/2009 12:31:38
AMQ7468: O arquivo de registro mais antigo necessário para executar a
recuperação de meio do gerenciador de fila QM.04866275.01 é S0002797.LOG.
-------------------------------------------------------------------------------
20/3/2009 12:31:53
AMQ6767: O arquivo de registro C:\Program Files\IBM\WebSphere
MQ\log\QM!04866275!01\active\S0002800.LOG não pôde ser aberto para utilização.
-------------------------------------------------------------------------------
20/3/2009 15:50:05
AMQ6767: O arquivo de registro C:\Program Files\IBM\WebSphere
MQ\log\QM!04866275!01\active\S0002799.LOG não pôde ser aberto para utilização.
|
I´ve verified these files and they weren´t removed (no file was removed, before ask) and disk has 19GB of free space, so, I believe that S0002799.LOG and S0002800.LOG were corrupted.
To resolve this, We made a "cold start" of MQ, as explained in this link:
http://www-01.ibm.com/support/docview.wss?uid=swg21179695
It worked, but would like an explanation about the problem. Same problem occourred in a MQ6.0 in Windows XP Home machine, when the script are deployed, and we need to know about this problem, before apply the script in other MQ achines.
Regard´s |
|
Back to top |
|
 |
exerk |
Posted: Fri Mar 20, 2009 12:59 pm Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Is the rcdmqimg ending before the next one is issued? _________________ 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 |
|
 |
matth |
Posted: Fri Mar 20, 2009 1:14 pm Post subject: |
|
|
Apprentice
Joined: 13 Feb 2007 Posts: 44 Location: Brazil
|
All commands was executed in same Prompt Shell, so they run one after other. Other point. In these machines, rcdmqimg was newer runned before:
Code: |
20/3/2009 12:03:30
AMQ7468: O arquivo de registro mais antigo necessário para executar a
recuperação de meio do gerenciador de fila QM.04866275.01 é S0000000.LOG.
-------------------------------------------------------------------------------
20/3/2009 12:05:42
AMQ7467: O arquivo de registro mais antigo necessário para iniciar o
gerenciador de fila QM.04866275.01 é S0002788.LOG.
|
|
|
Back to top |
|
 |
exerk |
Posted: Fri Mar 20, 2009 1:21 pm Post subject: Re: Troubles after rcdmgimg |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
matth wrote: |
...after running rcdmqimg a few times, the Queue Manager hangs... |
So I'll ask the question again, is the command being reissued before the previous run of the command has completed? _________________ 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 |
|
 |
matth |
Posted: Fri Mar 20, 2009 1:24 pm Post subject: Re: Troubles after rcdmgimg |
|
|
Apprentice
Joined: 13 Feb 2007 Posts: 44 Location: Brazil
|
exerk wrote: |
matth wrote: |
...after running rcdmqimg a few times, the Queue Manager hangs... |
So I'll ask the question again, is the command being reissued before the previous run of the command has completed? |
No. |
|
Back to top |
|
 |
exerk |
Posted: Fri Mar 20, 2009 1:32 pm Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Check that a disk quota has not been set. _________________ 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 |
|
 |
matth |
Posted: Fri Mar 20, 2009 1:45 pm Post subject: |
|
|
Apprentice
Joined: 13 Feb 2007 Posts: 44 Location: Brazil
|
exerk wrote: |
Check that a disk quota has not been set. |
No quotas in both machines. |
|
Back to top |
|
 |
exerk |
Posted: Fri Mar 20, 2009 1:53 pm Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
OK, my last shot - is queue depth high, with persistent messages? _________________ 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 |
|
 |
bruce2359 |
Posted: Fri Mar 20, 2009 5:16 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
So, after running rcdmqimg a few times... |
This is from the v6 WMQ System Admin manual:
When issuing a sequence of rcdmqimg commands, include the -l parameter only on the last command in the sequence, so that the log file information is gathered only once.
I suppose that a corrupted log file might result in the same error mesages. _________________ 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: Sat Mar 21, 2009 9:31 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
As well if you use MS0L to archive the old logs make sure you define a temp directory for copying the log files to (use the corresponding switch on MS0L). Otherwise you might have surprises if the archive process runs at the same time an error log file switch is being initiated by the qm.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
matth |
Posted: Mon Mar 23, 2009 11:54 am Post subject: |
|
|
Apprentice
Joined: 13 Feb 2007 Posts: 44 Location: Brazil
|
Thanks for responses. We don´t find yet a real cause of trouble, but we will simulate these situations:
-Run of twice rcdmqimg at same time.
-Run rcdmqimg with no new logs created, since last run.
In despite this, will check if use of rcdmqimg return codes may help us.
Regard´s |
|
Back to top |
|
 |
|