|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Changing log attribute in active mqgr in production |
« View previous topic :: View next topic » |
Author |
Message
|
jeevan |
Posted: Fri May 02, 2008 9:22 am Post subject: Changing log attribute in active mqgr in production |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
We need to change the log attributes of a production queue manager. can we do this without briging the qmgr donw?
We would like to change
ls, lp, lf
Can we just make changes in registry? Will this change get effective without bringing down the qmgr?
Thanks |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri May 02, 2008 9:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You can't change lf without recreating the qmgr.
You can change ls and lp, but must restart qmgr for them to take effect.
Never adjust the registry manually. Use amqmdain if you must change things in the registry. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
jeevan |
Posted: Fri May 02, 2008 10:11 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
Thank you very much Jeff. |
|
Back to top |
|
 |
sunny_30 |
Posted: Sat May 10, 2008 7:04 am Post subject: |
|
|
 Master
Joined: 03 Oct 2005 Posts: 258
|
Jeevan,
As Jeff said- you WILL need to recreate QMgr to change 'lf'.
But you can safely do so, by creating a DUMMY QMgr on PROD.
Follow the below procedure if you want to modify 'lf' OR even 'logtype'. This procedure saves all QM-objects:
Note: The queue manager is referred to as TESTQMGR.
Quote: |
1. cd /var/mqm/qmgrs
2. mv TESTQMGR TEST.OLD
NOTE:This will rename the TESTQMGR directory to be TEST.OLD, effectively backing up all your queues and objects.
3. dltmqm TESTQMGR
Note: This command may not completely run and it may produce error messages. This is OK. At the end of this command there are 3 places to check to make sure everything is cleaned up from TESTQMGR and if it did not then you will need to manually remove what is left.
4. There should not be a directory under /var/mqm/qmgrs by the name of TESTQMGR as it should have been renamed to TEST.OLD.
5. In /var/mqm/log there should not be a directory name TESTQMGR. If there is a directory left there, from /var/mqm/log issue the command rm -rf TESTQMGR to remove the old logs.
6. In /var/mqm there is a file called mqs.ini. Within file mqs.ini there will be QueueManager: stanzas for each queue manager defined on this box. There should no longer be a stanza referring to TESTQMGR. If there is a stanza for TESTQMGR, remove it; the whole stanza (should be 4 lines.)
7. crtmqm TESTQMGR
create with new logtype(lc or ll), new lf, new lp, new ls etc
8. cd /var/mqm/qmgrs
9. cp TESTQMGR/amqalchk.fil TEST.OLD
(This is to copy the new check point file over to the backup directory where you are saving our old queue manager files.)
10. rm -rf TESTQMGR
(This will remove the new qmgr files you just created so you can replace them with the files from the old queue manager that you had saved.)
11. mv TEST.OLD TESTQMGR
(This is where you just restored the old definitions. At this point you should have a new queue manager created with new logs but you should have our old queues and channels still there.)
12. Modify qm.ini to reflect the new changes.
13. strmqm TESTQMGR
(Start up the queue manager. Everything should be back to normal except there will be no attempt to recover any in-flight UOWs because you have nothing in the logs.) |
The same procedure can be followed when active-logs corrupt OR when a QM needs to be cold-started.
Not sure if this process is supported by IBM & also if there are any potential flaws in doing so. I did it on the Production system & it worked for me!
As a precaution do saveqmgr & amqoamd before you resume the above process.
-Sunny. |
|
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
|
|
|
|