Posted: Sat Oct 09, 2004 7:03 am Post subject: AMQ7469: Transactions rolled back to release log space.
Voyager
Joined: 04 Apr 2004 Posts: 96
hi,
We have installed Mqseries v5.2 on HP running for around 2 years now. It was observed today that we sent a large number of messages around 2000 and we got this error
AMQ7469: Transactions rolled back to release log space.
We have around 1 GB space in the /var/mqm directory on unix
To solve the issue temporary we changed the program and commited the messages. Now there is an requirement to increase the logs of MQ.
I have gone through the system admin guide , and the maximum is 63 logs. I need to know whether i can increase the primary logs to 12 and secondary log to 10
Yes, you can increase the number of files by editing the qm.ini file change:
Code:
LogPrimaryFiles=3
LogSecondaryFiles=2
to
Code:
LogPrimaryFiles=12
LogSecondaryFiles=10
Then stop and restart the MQManager.
However you can not increase the size of the logs by changing the value of "LogFilePages" and restarting the MQManager. To do so you need to delete the existing MQManager after backing up the existing object definitions with the saveqmgr script.
Then re-create the MQManager using crtmqm with the -lf argument to set the size of the log files. If the -lf argument is not specified the default value of 1024 is used based on the entries in the /var/mqm/mqs.ini file. That creates a file that is 4meg. It is possible to edit the mqs.ini file but I don't recomend it.
Ergo if you use the argument, "-lf 3072" in the crtmqm command it will create 12meg log files. The equation is the value of -lf x4kb bytes.
For example if you wanted to create an MQManager as the default QManager with the SYSTEM.DEAD.LETTER.QUEUE as the default DLQ with 12 primary logs an 10 secondary with each log being 12 meg the syntax would be:
Note: I have been told that you can cheat on the recreation of the MQManager and increase the size of the log and number of logs by creating a second QManager with the desired number of logs and the desired size.
Then copy the /var/mqm/log/QMGR/amqhlctl.lfh file and the "active" directory from the newly created QManager over the top of the pre-existing amqhlctl.lfh and "active" directory.
However, this is not IBM recommended Best Practice and I have never tried it. So if you try this and it blows up in your face I doubt you will be able to get IBM support.
But then I'm not so sure this matters so much in your case. MQ5.2 is not longer "Officially" supported by IBM anyway. For more information on this topic see the MQ5.2 Administration Guide.
Alternatively you may want to take advantage of this situation to upgrade from 5.2 to 5.3.0.7 to raise your MQ version to supported levels and solve your active log issue.
Listen to me, I sound like an IBMer now. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial.
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