| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| It seems cool start does not work in MQ 7.5` |
« View previous topic :: View next topic » |
| Author |
Message
|
| jeevan |
 Posted: Fri May 16, 2014 7:21 pm Post subject: It seems cool start does not work in MQ 7.5` |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
Is there any changes in log management in MQ 7.5 ? I could not do the cool start. In fact it is little more than the just cool start. I am trying to change number of log files.
I followed the following steps:
End qmgr, channel, listener and connections
Create a dummy qmgr with required log ( with -lc -lp and -ls switch)
Replace log files and amqhlctl.lfh files
Restart the qmgr
The queue manager does not come up and I am getting AMQ7017: Log not available error message. FGC are being cut with the following details.
The error message says, log does not find. There is an FDC file generated with the following details.
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri May 16 2014 22:15:26 Eastern Daylight Time |
| UTC Time :- 1400292926.652000 |
| UTC Time Offset :- 60 (Eastern Daylight Time) |
| Host Name :- MININT-PGIEB9B |
| Operating System :- Windows 7 Professional x64 Edition, Build 7601: SP1 |
| PIDS :- 5724H7220 |
| LVLS :- 7.5.0.2 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Installation Path :- C:\IBM\WebSphere MQ |
| Installation Name :- Installation1 (1) |
| Probe Id :- HL195079 |
| Application Name :- MQM |
| Component :- hpiOpenExtentFile |
| SCCS Info :- F:\build\slot1\p750_P\src\lib\logger\amqherr0.c, |
| Line Number :- 118 |
| Build Date :- Jun 28 2013 |
| Build Level :- p750-002-130627 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\IBM\WebSphere MQ\bin\amqzmuc0.exe |
| Addressing mode :- 32-bit |
| Process :- 00005712 |
| Thread :- 00000003 |
| QueueManager :- TESTQM2 |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 13 |
| ConnId(2) QM :- 12 |
| Last HQC :- 2.0.0-576840 |
| Last HSHMEMB :- 2.17.17-2494128 |
| Major Errorcode :- hrcE_MQLO_ACCD |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
I have done quite a few cool start /log replacement in the past, so I do not think I might have missed any steps.
Any ideas?
Thanks |
|
| Back to top |
|
 |
| Andyh |
| Posted: Fri May 16, 2014 10:59 pm Post subject: |
|
|
Master
Joined: 29 Jul 2010
Posts: 239
|
1. Cold start is not a supported operation and should be avoided where possible.
2. You don't need to cold start to change the number of log extents
3. hrcE_MQLO_ACCD typically indicates an access denied issue, please check the file permissions on your copied log files.
4. MQ 7.5 has no conceptual changes to log file usage, and the UNSUPPORTED cold start procedure should work under the same conditions as earlier versions. |
|
| Back to top |
|
|
| jeevan |
| Posted: Sat May 17, 2014 7:11 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| Andyh wrote: |
1. Cold start is not a supported operation and should be avoided where possible.
|
Though I am aware of it. thanks for reminding. This is basically my personal testing. Even in official context, IBM folks informally suggest that.
| Andyh wrote: |
2. You don't need to cold start to change the number of log extents
|
In fact, I was planning to test the change in log file size which I have been hearing and was myself pledging that we can not do but I recently saw it is possible. So this test is preparation for changing the log file size. But I just started with number of file change with creating new qmgr. Otherwise, yes, I am aware that I can change the number of log file is taken from qm.ini file.
| Andyh wrote: |
3. hrcE_MQLO_ACCD typically indicates an access denied issue, please check the file permissions on your copied log files.
|
I have checked permission in log file and in amqhlctl.lfh. I also compared that with other qmgrs log file has for mqm user id
| Andyh wrote: |
4. MQ 7.5 has no conceptual changes to log file usage, and the UNSUPPORTED cold start procedure should work under the same conditions as earlier versions.
|
Thanks for this. Try to figure out read -->What's new in WebSphere MQ Version 7.5(http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/index.jsp?topic=%2Fcom.ibm.mq.pro.doc%2Fq001050_.htm) |
|
| 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
|
|
|
|
