| Author |
Message
|
| psiracusa |
 Posted: Mon Feb 26, 2007 10:19 am Post subject: SYSTEM.TEMPQMGR when trying to add a partial repository |
 |
|
Apprentice
Joined: 17 Nov 2006
Posts: 34
|
| We are attempting to add in a partial repository (AIX 5.3 MQ V6.0.2.0 to a full repository (SunOS 5.8 MQ V5.3 CSD 07)and immediately get a SYSTEM.TEMPQMGR when running a dis clusqmgr(*) from the partial. As soon as the channel came up we ran into this problem. I deleted all the objects and cleared all the cluster queues, restarted the queue manager, recreated the objects and restarted the channel and ran into the same problem. Any ideas? |
|
| Back to top |
|
 |
| bbburson |
| Posted: Mon Feb 26, 2007 11:05 am Post subject: |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
A google search for SYSTEM.TEMPQMGR quickly turned up http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzah.doc/csq68sym2.htm which contains
| Quote: |
| This queue manager has not received any information from the full repository queue manager that the manually defined CLUSSDR channel points to. The manually defined CLUSSDR should be in running state, check that the CLUSRCVR definition is also correct, especially its conname and cluster parameters. Alter the channel definition. It may take some time for the remote queue managers to complete a retry cycle and restart their channels with the corrected definition. |
I suspect you haven't waited long enough for the partial to join the cluster, or your CLUSSDR definition is in error and it cannot join the cluster. |
|
| Back to top |
|
|
| psiracusa |
| Posted: Mon Feb 26, 2007 11:28 am Post subject: |
|
|
Apprentice
Joined: 17 Nov 2006
Posts: 34
|
| It's been up for a couple of hours now so that should be enough time. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Feb 26, 2007 12:11 pm Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
There is either some configuration error, e.g. the CLUSRCVR (or CLUSSDR to the full repos) does not specify the right IP address, hostname or port (if a CLUSSDR, it does not match the CLUSRCVR at the full repos), or there is some comms error, e.g. there is no listener running at the full or partial repos qmgr, or the listener has the wrong port number.
Another possible config error is that the cluster name on the channel does not match that of the full repos. This will probably cause an error msg in the qmgr error logs, probably at the full repos qmgr.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| psiracusa |
| Posted: Mon Feb 26, 2007 1:02 pm Post subject: |
|
|
Apprentice
Joined: 17 Nov 2006
Posts: 34
|
| Well....both the cluster receiver channels and cluster sender channels are up and have the correct cluster specified. The partial repository doesn't have any cluster queues at this time though. I don't think that matters but I thought I would throw that in. |
|
| Back to top |
|
|
| bbburson |
| Posted: Mon Feb 26, 2007 1:54 pm Post subject: |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
Please post the channel definitions of full-repository CLUSRCVR channel and partial-repository CLUSSDR (to the full-repos) and CLUSRCVR channels.
Thanks |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Feb 27, 2007 12:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And make sure each can reach the other with the def supplied. (telnet should be your prooving tool.)
telnet host port
ctrl+]
quit
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
