Author |
Message
|
kavithadhevi |
Posted: Fri May 24, 2002 6:32 am Post subject: Error:Queue file primary key length invalid-corrupt or old | |
|
|
 Master
Joined: 14 May 2002 Posts: 201 Location: USA
|
Hi,
Has anyone got this error before in Tandem machine. Pls help me here.
--- Kavitha |
|
Back to top |
|
 |
mqonnet |
Posted: Fri May 24, 2002 7:07 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
Which version of Mq are you on.
Is this error from the app. If so, what is the app doing.
Cheers.
Kumar _________________ IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
Back to top |
|
 |
kavithadhevi |
Posted: Fri May 24, 2002 7:14 am Post subject: |
|
|
 Master
Joined: 14 May 2002 Posts: 201 Location: USA
|
Hi,
Thanks for trying, i dono wats happening, just trying do some research on old errors. so i am not sure whether its from an applicaiton or from qmgr. so i am sending u a part of FDC , see whether it gives some info regd this or not.
-- Kavitha
MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- May 23 23:29:19 2002 |
| Host Name :-
| PIDS :- 5724A39 |
| LVLS :- 510 |
| Product Long Name :- MQSeries for Compaq NonStop Kernel |
| Vendor :- IBM |
| Probe Id :- UN025002 |
| Application Name :- MQM |
| Component :- qslLoadMessages |
| Build Date :- May 29 2001 |
| Exe File Name :- \STLOUIS.$DATA23.ZMQSEXE.MQQSSVR |
| UserID :- MQM.MANAGER |
| Process File Name :- |
| Node number :- 51 |
| CPU :- 8 |
| PIN :- 328 |
| QueueManager :- QM |
| Major Errorcode :- Unknown(1774) |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ1774 |
| Probe severity :- Severity 4: information |
| Probe Description :- AMQ1774: MQSeries was unable to display an error messa |
| ge 24720. |
| Text :- Queue file primary key length invalid - corrupt or old |
| database |
| Arith2 :- 36 (0x24) |
| Comment1 :- $data14.STLOUISM.QEEASEXE |
|
Back to top |
|
 |
mqonnet |
Posted: Fri May 24, 2002 7:33 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
Well unless you know under what circumstances you are getting this problem, it would be hard to comment on it. Could be for a variety of reason. And if you are just looking at this error from one of the so many old FD's, then it makes things even more difficult.
You did not mention as to whats the version of MQ you are using.
Cheers.
Kumar _________________ IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
Back to top |
|
 |
kavithadhevi |
Posted: Mon Jun 03, 2002 5:38 am Post subject: |
|
|
 Master
Joined: 14 May 2002 Posts: 201 Location: USA
|
Hi,
it is 5.2 csd 04. pls let me know if u have any suggestions.
thanks. |
|
Back to top |
|
 |
mqonnet |
Posted: Mon Jun 03, 2002 5:42 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
First of all i think you got it wrong out there.
There is no V 5.2 on Tandem and there are no CSD's yet. So am not quite still sure of what version you are on. Assuming that you are on V5.1 which is the latest, there is one question. Did you recently upgrade from the earlier version. Because if you did, then there are some changes to primary keys. May be you are getting this because of the same.
Cheers.
Kumar _________________ IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
Back to top |
|
 |
|