| Author |
Message
|
| t7516dw |
 Posted: Mon Nov 14, 2011 5:44 am Post subject: Issues with MS0L SupportPac |
 |
|
Newbie
Joined: 14 Nov 2011
Posts: 6
|
Hi there,
We migrated some of our queue managers from circular to linear logging on Windows systems and started to use MS0L SupportPac to delete the queue manager's logs that aren't longer needed. Now we are experiencing problems with this SupportPac.
We execute hourly "mqllm-Multi.bat" script and sometimes (once a week per queue manager) it returns the following message: "com.ibm.ms0l.MqLinearLogfileMaint :: Unable to locate oldest file required for Restart. Process HALTED!"
After this, if we execute again the script it finishes OK. We don't understand why it's happening. Have somebody experienced the same issue?
We are using WebSphere MQ 7.0.1.5 and the current release of MS0L SupportPac (2011-02-23).
Regards,
Adib Ahmed Akhtar |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Mon Nov 14, 2011 5:55 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
May I suggest that you research what is required for a qmgr to restart. This documentation can be found in the WMQ System Administration manual, or the InfoCenter equivalent.
_________________
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: Mon Nov 14, 2011 11:22 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Make sure you use the temporary directory to offload the qmgr error logs before looking for the right start and finish log numbers...
I have experienced some grief where this was not the case.
As for the other question, this would be quite normal. Think the qmgr reached max connections and a lot of attempts are made to connect. These attempts write to the log... and the log rolls so fast that there is no message about the last media recovery or the last qmgr restart log in the 3 error logs.
One way to attempt to avoid this is to run rcdmqimg before running the support pack. But if you run the support pack every hour this might not be advisable. We run rcdmqimg once a day and the support pack (MS0L) every hour.
However our platform is AIX
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Nov 14, 2011 5:49 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I was disappointed that the new MQ 7.1 *still* does not offer a way to manage Linear Logs from within the base product.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| t7516dw |
| Posted: Thu Nov 17, 2011 2:10 am Post subject: RE: Issues with MS0L SupportPac [SOLVED] |
|
|
Newbie
Joined: 14 Nov 2011
Posts: 6
|
Finally I discovered what was happening. The SupportPac only reads from the log AMQERR01 to determine "Required Restart Log" and "Required Media Recovery Log".
The folloing is the scenario of what is happening in the script included in this SupportPac:
1. Execution of rcdmqimg: Write of "Required Restart Log" information on AMQERR01, which gets full and empties its contents (previously dumping contents of AMQERR01 on AMQERR02)
2. The java executable of the SupportPac tries to read "Required Restart Log" from AMQERR01 and doesn't find this information, and fails.
The solution is to add the following code just after the line "call mqllm.bat %%M" on "mqllm-Multi.bat" script:
if errorlevel 1 (
rcdmqimg -l -m %%M -t all * 2>> %MULTILOGFILE%
call mqllm.bat %%M
)
Thanks for your help.
Cheers,
Adib Ahmed Akhtar |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 17, 2011 9:01 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Think about it... If your error log file is full before the rcdmqimg is done, there is something wrong with your qmgr... or your error log has been largely understated in size...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
