Author |
Message
|
Vinoth Kumar |
Posted: Sun Mar 08, 2015 5:44 am Post subject: MQ Internal Error Occured |
|
|
Newbie
Joined: 27 Jan 2015 Posts: 5
|
Hi Guys,
AM getting below error while creating queues on MY QMGR.
define ql(Temp)
2 : define ql(Temp)
AMQ8101: WebSphere MQ error (893) has occurred.
Analyzing at the FDC files, it doesnt give me clear idea.
Major Errorcode :- arcE_OBJECT_NOT_FOUND |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
|
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
MY QMGR is running on V7.5
Can some one help me with this???
Thanks,
Vinoth |
|
Back to top |
|
 |
bruce2359 |
Posted: Sun Mar 08, 2015 5:51 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
What is the ProbeId? Search google for it. _________________ 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 |
|
 |
Vinoth Kumar |
Posted: Sun Mar 08, 2015 6:05 am Post subject: |
|
|
Newbie
Joined: 27 Jan 2015 Posts: 5
|
Nothing Much with Probe Id i Can figure out.
Probe Id :- ZF044022 |
| Application Name :- MQM |
| Component :- zfu_as_calculateauthority |
| SCCS Info :- /build/slot1/p750_P/src/lib/exits/oam/amqzfubx.c, |
| Line Number :- 1966 |
| Build Date :- Jan 23 2014 |
| Build Level :- p750-003-140123 |
| Build Type :- IKAP - (Production) |
| Effective UserID :- 40377 (mqm) |
| Real UserID :- 40377 (mqm) |
| Program Name :- amqzlaa0 |
| Addressing mode :- 64-bit |
| LANG :- en_US |
| Process :- 7471262 |
| Thread :- 20 |
|
Back to top |
|
 |
nelson |
Posted: Sun Mar 08, 2015 7:19 am Post subject: |
|
|
 Partisan
Joined: 02 Oct 2012 Posts: 313
|
Even not solved this post could give you some hints. |
|
Back to top |
|
 |
Vinoth Kumar |
Posted: Sun Mar 08, 2015 9:22 am Post subject: |
|
|
Newbie
Joined: 27 Jan 2015 Posts: 5
|
Thanks.
I checked this already nothing helped, actually final solution on this post they have deleted and recreated the QMGR. But its not possible in my case. |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Mar 08, 2015 4:45 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Vinoth Kumar wrote: |
Thanks.
I checked this already nothing helped, actually final solution on this post they have deleted and recreated the QMGR. But its not possible in my case. |
You may have to define all parameters. Is SYSTEM.DEFAULT.LOCAL.QUEUE available and undamaged? Do you have access to it (+dsp +inq)?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
Vinoth Kumar |
Posted: Sun Mar 08, 2015 6:02 pm Post subject: |
|
|
Newbie
Joined: 27 Jan 2015 Posts: 5
|
Yupp have access and it looks good. I tried defining with all parameters same error occurs  |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Mar 08, 2015 8:36 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Vinoth Kumar wrote: |
Yupp have access and it looks good. I tried defining with all parameters same error occurs  |
Looks good may not be good enough. Can you put a message to it and get a message from it? May be you need to bounce the qmgr?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
gbaddeley |
Posted: Tue Mar 10, 2015 1:46 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
Further down the FDC file, what is MQ doing just before arcE_OBJECT_NOT_FOUND ? It might indicate exactly what object is not found, and why zfu_as_calculateauthority is being done. _________________ Glenn |
|
Back to top |
|
 |
Andyh |
Posted: Tue Mar 10, 2015 2:32 pm Post subject: |
|
|
Master
Joined: 29 Jul 2010 Posts: 239
|
The subset of the FDC you've provided is much too small to offer any real hope of identifying the underlying issue. The probe id suggests some issue with the @class authorizations for queues. Have you made any direct change to the SYSTEM.AUTH.DATA.QUEUE object? (you should NEVER do this), or disabled and then re-enabled the OAM at any time ?
Is there some reason why you've not taken this up directly with MQ support ? |
|
Back to top |
|
 |
|