| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| FDC |
« View previous topic :: View next topic » |
| Author |
Message
|
| kavithadhevi |
 Posted: Tue Sep 24, 2002 6:34 am Post subject: FDC |
 |
|
Master
Joined: 14 May 2002
Posts: 201
Location: USA
|
Hi,
I need some help to understand this FDC. I dont understand this error type, if anybody has come across or got any idea about this error, please help me out.
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Sunday September 22 16:01:39 CDT 2002 |
| Host Name :- st102 (AIX 4.3) |
| PIDS :- 5765B73 |
| LVLS :- 520 |
| Product Long Name :- MQSeries for AIX |
| Vendor :- IBM |
| Probe Id :- ZX000001 |
| Application Name :- MQM |
| Component :- ExecCtrlrMain |
| Build Date :- Mar 27 2002 |
| CMVC level :- p520-CSD04G |
| Build Type :- IKAP - (Production) |
| UserID :- 00000228 (mqm) |
| Program Name :- amqzxma0_nd |
| Process :- 00025604 |
| Thread :- 00000001 |
| QueueManager :- MQRTST1A02 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- lpiRC_LOG_LOCATION_INVALID |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal MQSeries error has occurred |
| (7064) |
| Arith1 :- 28772 7064 |
| |
+-----------------------------------------------------------------------------+
--} xlsReleaseMutex rc=OK
-} xcsDisconnectSharedMem rc=xecS_I_NO_OTHER_CONNS
-{ xcsDestroySharedMemSet
--{ xcsDisconnectSharedMem
---{ xstUnregisterConnectionFromSet
----{ xcsRequestThreadMutexSem
----} xcsRequestThreadMutexSem rc=OK
----{ xcsReleaseThreadMutexSem
----} xcsReleaseThreadMutexSem rc=OK
---} xstUnregisterConnectionFromSet rc=xecS_E_NOT_CONNECTED
--} xcsDisconnectSharedMem rc=xecS_E_NOT_CONNECTED
--{ xlsRequestMutex
--} xlsRequestMutex rc=OK
_________________
Thanks in Advance. 
Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com |
|
| Back to top |
|
 |
| bduncan |
| Posted: Tue Sep 24, 2002 9:51 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Kavitha,
In what context did you get this FDC? What was the queue manager doing at the time? Did you have any applications connected to it, etc... Also, check the queue manager logs (AMQERR0X.log files) for additional information. Usually when the queue manager creates an FDC, it happened as the result of some problem which would have already been logged in the regular queue manager logs...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| kavithadhevi |
| Posted: Tue Sep 24, 2002 11:55 am Post subject: |
|
|
Master
Joined: 14 May 2002
Posts: 201
Location: USA
|
Application is running as usual, i dont see anything different, other than the FDC and when i checked the qmgr/error log, didnt give much of idea other than channels stopped and restarted back on automatically.
From the FDC i am not gettign a head start what this error is all about. Got any idea 
_________________
Thanks in Advance.
Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue Sep 24, 2002 2:06 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Have you checked the diskspace on the partition holding the queue manager logs? The FDC seems to indicate you ran out of space when the queue manager attempted to write to its logs (not the error logs, but the actual queue manager logs). It may have some free space now (especially if you were using syncpoint because it would have automatically rolled back).
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Sep 25, 2002 10:05 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I checked an internal database. All of the hits that I got indicated that your log files are corrupted. There weren't any details on what caused them to corrupt in the first place.... |
|
| 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
|
|
|
|
