| Author |
Message
|
| nathanw |
 Posted: Thu Jul 13, 2006 2:21 am Post subject: SYSTEM.CLUSTER.REPOSITORY.QUEUE - Problem with message |
 |
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
Yesterday we had a problem with our cluster and it was removed and redefined.
Since then the data has not been able to be transmitted from one queue manager to another with the 2085 error of object does not exist.
Looking through the various posts here I checked the SYSTEM.CLUSTER.REPOSITORY.QUEUE on the FR queue manager and found that it had 422 messages sat on there.
The first message is from 4 15 pm yesterday and the rest are from approx 10 minutes ago when I refreshed the Cluster information along with recomendations from posts here.
Question should this message from over 15 hour ago still be on the queue?
As an afterthought the message from 15 hours ago is approx 12k with a message from the refresh str8 after of 14 k then alot of smaller messages of 500 b which I assume are the queue definitions being refresh through teh system
If the answer is no then I will need to remove it obviously - any ideas how?
If this is not the solution any ideas?
The solution has 3 QMs with a gateway and 2 brokers all in the cluster
all queues are shard withing the cluster on all 3 QMS and when i do a runmsc dis qc(*) all are displayed.
Data is entering the gateway but failing to be put to the QMS with error 2085 and the messages sit on the DLQ for gateway.
All help gratefully received |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Thu Jul 13, 2006 3:26 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
you should not start to work with the messages on the SYSTEM.CLUSTER.REPOSITORY.QUEUE . instead, you should investigate the status of your cluster. start with dis clusqmgr to verify that all required queuemanagers are member of the lcuster,
, check the cluster channels if they are all working, check if the FR has all available information about participating cluster queuemanagers and their queues, check the mqseries logs for error messages.
use the supplied commands but do not play around with messages in the SCRQ.
i assume that maybe the "remove and redefine" of the cluster is the problem. maybe you did not use toe correct action sequence. or the cluster was not "redefined" properly.
what problem did the cluster have that required to remove it?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| nathanw |
| Posted: Thu Jul 13, 2006 4:20 am Post subject: ***SOLVED*** SYSTEM.CLUSTER.REPOSITORY.QUEUE - Problem |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
have sorted the problem in the end it wasnt a cluster problem it was a hardware.
apologies |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jul 13, 2006 5:09 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
how does a hardware problem cause a 2085?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jul 14, 2006 4:13 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| PeterPotkay wrote: |
| how does a hardware problem cause a 2085? |
corrupt or inaccessible media maybe ? Corrupted FAT?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| nathanw |
| Posted: Mon Jul 17, 2006 6:14 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
It turns out the problems were separate and the cluster had not refreshed through but once doe it was fine.
The hardware was a separate problem apologies for confusing |
|
| Back to top |
|
|
|
|
