| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQRC_OBJECT_DAMAGED |
« View previous topic :: View next topic » |
| Author |
Message
|
| raju37 |
 Posted: Thu Jan 26, 2017 9:34 am Post subject: MQRC_OBJECT_DAMAGED |
 |
|
Newbie
Joined: 05 Jan 2017
Posts: 5
|
Hi All,
We are getting the below error and the queue log is getting filled. Could anyone please tell what could be the issue ?
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thu January 26 2017 17:28:25 GMT |
| UTC Time :- 1485451705.200198 |
| UTC Time Offset :- 0 (GMT) |
|
| Operating System :- Linux 3.10.0-327.el7.x86_64 |
| PIDS :- 5724H7251 |
| LVLS :- 8.0.0.4 |
| Product Long Name :- WebSphere MQ for Linux (x86-64 platform) |
| Vendor :- IBM |
| O/S Registered :- 1 |
| Data Path :- /var/mqm |
| Installation Path :- /opt/mqm |
| Installation Name :- Installation1 (1) |
| License Type :- Production |
| Probe Id :- ZX103020 |
| Application Name :- MQM |
| Component :- zmuHealthCheck |
| SCCS Info :- /build/slot1/p800_P/src/lib/zu/amqzmut0.c, |
| Line Number :- 3586 |
| Build Date :- Oct 17 2015 |
| Build Level :- p800-004-151017 |
| Build Type :- IKAP - (Production) |
| Effective UserID :- 501 (mqm) |
| Real UserID :- 501 (mqm) |
| Program Name :- amqzmur0 |
|
| Addressing mode :- 64-bit |
| LANG :- en_GB.UTF-8 |
| Process :- 15884 |
| Process(Thread) :- 15884 |
| Thread :- 1 Restartable |
|
| UserApp :- FALSE |
| ConnId(1) IPCC :- 22 |
| ConnId(2) QM :- 17 |
| Last HQC :- 1.0.0-3305664 |
| Last HSHMEMB :- 2.18.18-9408 |
| Last ObjectName :- |
| Major Errorcode :- MQRC_OBJECT_DAMAGED |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 4 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 9979 |
| Arith1 :- 24 (0x18) |
| Arith2 :- 9988 (0x2704) |
| Comment1 :- DEFERRED_DELIVERY | |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jan 26, 2017 9:52 am Post subject: Re: MQRC_OBJECT_DAMAGED |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| raju37 wrote: |
| Could anyone please tell what could be the issue ? |
Well going out on a limb, the problem is probably the one described for that reason code here  
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jan 26, 2017 12:11 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Better you should ask "how should I go about identifying the source of the problem?"
I'd start by searching (google) for the Probe Id named in the symptom report. This may already have been resolved.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jan 26, 2017 9:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Looks like the comment clearly states the problem object. I'd expect there should also be an entry in the queue manager error logs.
If you have linear logging, recover the object. If not, you'll have to delete and recreate it... Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| cgache |
| Posted: Fri Jan 27, 2017 6:33 pm Post subject: |
|
|
Apprentice
Joined: 27 May 2013
Posts: 28
Location: Sydney, AUS
|
| was this mq installation in any kind of (HA) cluster system? (not mq cluster) |
|
| 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
|
|
|
|
