| Author |
Message
|
| sathya532k |
 Posted: Wed Sep 01, 2010 6:37 am Post subject: AMQ7469 - Transaction rolled back to release log space |
 |
|
Novice
Joined: 04 Dec 2006
Posts: 15
|
Hi All,
Need Help in increaing the log space without rebuilding the qmanager.
I went through the IBM website and they say, i can have two options for the above logs.
1. Increase the log file count or
2. Increase th log space ( can be done only with rebuilding the qm again) which is not possible, since this is prod env.
My workaround:
Increased the Pri Log count from 6 to 10 & and sec log count from 5 to 6.
Can u guys help me to resolve this issue. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Sep 01, 2010 6:52 am Post subject: Re: AMQ7469 - Transaction rolled back to release log space |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sathya532k wrote: |
My workaround:
Increased the Pri Log count from 6 to 10 & and sec log count from 5 to 6. |
Presumably in the ini file?
| sathya532k wrote: |
| Can u guys help me to resolve this issue. |
What issue? You've clearly done some research & found the 2 available methods, then selected the one that suits you.
If you find the queue manager still has 6 primary logs, you may find you've not bounced it since you made the change.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sathya532k |
| Posted: Wed Sep 01, 2010 7:07 am Post subject: Hi Vitor |
|
|
Novice
Joined: 04 Dec 2006
Posts: 15
|
Yes i the .INI file i made the changes.
I Could see the changes in the log file count in the <qmanger>/active/ *.LOG
but still see the issue reflecting in the logs. stating the same issue again.
Yes,..I did bounced mq twice and still stuck with this issue.
Any Help is very much appreciated. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 01, 2010 7:29 am Post subject: Re: Hi Vitor |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sathya532k wrote: |
| Yes,..I did bounced mq twice and still stuck with this issue. |
Then you've either miscalculated how much you needed to increase the log size by & need to increase it further, or you have a badly behaved application that's not using transactionality properly. In that latter case, you could theoretically increase the log to the maximum permitted & it would still fill.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Sep 01, 2010 7:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
What criteria did you use to determine that increasing the primary logs to 10 and the secondary logs to 6 was the correct set of numbers to choose?
What transaction, in specific, is being complained about? Is it from one of your applications? Is it from an MQ channel? |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Sep 01, 2010 1:51 pm Post subject: Re: AMQ7469 - Transaction rolled back to release log space |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
This command should list lots of info about the apps using your queue, and should include enough to find whether a transaction is being held open for a "long time".
DISPLAY QSTATUS(your-q-name) TYPE(HANDLE) ALL
If you believe a transaction is being held open for a "long" time by one of the applications, then get in touch with the application's support team, possibly the app is not behaving correctly(?).
Check out this page in the MQ manuals http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzaj.doc/sc12290_.htm (particularly the mention of QMURID). |
|
| Back to top |
|
|
|
|
