| Author |
Message
|
| Volodya |
 Posted: Fri Jul 01, 2005 6:19 am Post subject: Detected Corrupted Quickcell |
 |
|
Novice
Joined: 04 Mar 2004
Posts: 22
Location: Moscow
|
Hi,
I could not start Listener WMQ5.3.0.8 on HP_UNIX.
runmqlsr gives a mistake AMQ6109 (An internal WebSphere MQ error has occurred) and FDC: Detected Corrupted Quickcell.
dspmq shows that the queue manager have status as Running.
What will you advise in this case?
What means "Detected Corrupted Quickcell"?
How to start Listener?
The FDC has the following :-
| WebSphere MQ First Failure Symptom Report |
| Date/Time :- Friday July 01 11:17:11 WSTDST 2005 |
| Host Name :- mainsvr (HP-UX B.11.11) |
| PIDS :- 5724B4102 |
| LVLS :- 530.8 CSD08 |
| Product Long Name :- WebSphere MQ for HP-UX |
| Vendor :- IBM |
| Probe Id :- XC014032 |
| Application Name :- MQM |
| Component :- xcsAllocateQuickCell |
| Build Date :- Sep 21 2004 |
| CMVC level :- p530-08-L040921 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000135 (root) |
| Program Name :- runmqlsr_nd |
| Process :- 00024540 |
| Thread :- 00000001 |
| Major Errorcode :- STOP |
| Minor Errorcode :- OK |
| Probe Type :- HALT6109 |
| Probe Severity :- 1 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Comment1 :- Detected Corrupted Quickcell
_________________
Vladimir Makushkin, WebSphere MQ administrator |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Jul 01, 2005 6:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
This error seems to have to do with internal MQ memory management.
It also looks like there were some fixes for this in CSD09
I would definitely open a PMR with IBM - as most of the links I could find about the ProbeID were for ISeries, not HP-UX.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Fri Jul 01, 2005 8:35 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
There are also fixes in CSD10 but having said as much. I recently started getting these errors on a Development AIX5.1 Server that was being upgraded from to WMQ5.3.0.10/Workflow3.4 and WAS5.1
Eventually we had to reboot.
The server had been up for 104 days and there had been a lot of recent activity in regards to stopping and restarting the MQManager. There had been numerous instances in which the ipcrm script was used to remove stale semops and I think the server had just had enough of that.
At this point even dspmq was throwing FFST's and it was not functioning normally as in sometimes it would display the status of all the defined MQManagers on the server and sometimes it would not.
"strmqm FMCQM" would sometimes work and other times it would say MQ Manager not defined or some such.
Eventually I made the call to reboot the server. That was two days ago and things have settled down considerably.
A word about semop and ipcrm, ipcrm is the, as far as I know, the only means we have to remove stale semops but from what I am told it is not a very graceful or OS polite way of doing it. In my experience if you do it a lot. Servers can begin to behave............ oddly.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| WillH |
| Posted: Fri Jul 01, 2005 9:43 am Post subject: |
|
|
Novice
Joined: 15 Jun 2005
Posts: 23
|
If bouncing the host isn't a viable solution in the short term (like you have to wait for a maintenance window), you can tell MQ to use as much shared memory as the OS allows with this environment variable:
EXTSHM=ON
Put that in your mqm .profile, and bounce the queue manager. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jul 01, 2005 12:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Once the qmgr is stopped the shared memory is not necessarily freed but held in anticipation of the qmgr restarting shortly.
If you plan an upgrade (CSD) make sure you release all shared memory.
Check out amqmclen for that.
Enjoy  |
|
| Back to top |
|
|
| vennela |
| Posted: Sat Jul 02, 2005 12:06 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| By any chance did you install the DCE version of MQ? |
|
| Back to top |
|
|
| bower5932 |
| Posted: Sun Jul 03, 2005 3:21 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Quote: |
| | Program Name :- runmqlsr_nd | |
I don't think he did. |
|
| Back to top |
|
|
| Volodya |
| Posted: Mon Jul 04, 2005 6:12 am Post subject: |
|
|
Novice
Joined: 04 Mar 2004
Posts: 22
Location: Moscow
|
Hi all from Moscow,
mainsvr is production server.
There is a risk that availability qmgr to not be restored after queue manager reboot.
Therefore I open a PMR with IBM.
The expected decision is upgrade (CSD09 and CSD10).
In this case all your recommendations will be very useful to me.
I shall necessarily inform as to end the decision of this problem.
Many thanks to all for support.
_________________
Vladimir Makushkin, WebSphere MQ administrator |
|
| Back to top |
|
|
| Volodya |
| Posted: Thu Jul 07, 2005 5:49 am Post subject: |
|
|
Novice
Joined: 04 Mar 2004
Posts: 22
Location: Moscow
|
IBM has opened PMR and recommended us install CSD10. It will prevent an opportunity of occurrence 'Corrupted Quickcell' FDC on HP_UNIX qmgr.
This mistake causes unpredictable qmgr behaviour. Originally Listener has not started. Then Listener has started but 2 channels have ceased to start and at attempt of start of the channel was generated 'Corrupted Quickcell' FDC. It is production system and it was necessary to correct a situation urgently. Qmgr has been stopped, shared memory has been cleared(/opt/mqm/bin/amqiclen) and qmgr has started. FDC problems have disappeared.
We will be upgrade (CSD10) test system in the nearest days off and for production system in following days off. Only after that we shall take advantage of advice: Enjoy Thank you.
_________________
Vladimir Makushkin, WebSphere MQ administrator |
|
| Back to top |
|
|
|
|
