| Author |
Message
|
| nina |
 Posted: Tue Oct 18, 2005 7:22 am Post subject: Problem in upgrading MQ5.2.1. to 5.3 with CSD10 on AIX |
 |
|
Novice
Joined: 13 Sep 2005
Posts: 11
|
Hi All,
We have upgraded MQ5.2.1 to MQ5.3 with CSD10 on AIX without uninstalling MQ5.2.1 on one of the servers. Queue Managers started properly. All of a sudden, MQCluster environment is not working properly. We have two clusters overlapping on Gateway Queue manager, and we are unable to transfer messages from one cluster to other cluster through Gateway shared queues. We are getting the following error MQRC 2001 MQRC_ALIAS_BASE_Q_TYPE_ERROR.
Could you please help me for the following questions:
1. Can we install MQ5.3 without uninstalling previous version of MQ?
2. Do we need to recreate MQ objects and cluster environment? as some of the Queue managers in cluster are still on MQ5.2.1 only.
Waiting for your reply..as this is very critical for our environment.
Thanks, and Regards,
Nina |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Oct 18, 2005 7:29 am Post subject: Re: Problem in upgrading MQ5.2.1. to 5.3 with CSD10 on AIX |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| nina wrote: |
| 1. Can we install MQ5.3 without uninstalling previous version of MQ? |
No.
| nina wrote: |
| 2. Do we need to recreate MQ objects and cluster environment? as some of the Queue managers in cluster are still on MQ5.2.1 only. |
No.
These should be carried through, as long as you do not delete MQ file systems between the uninstall and the reinstall.
DO NOT put 5.3 qmgrs in a cluster where all the full repositories are 5.2. You can corrupt the repository, badly, if you enable SSL.
So upgrade your Full Repositories FIRST.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Tue Oct 18, 2005 7:50 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
I suspect that there was a bug in 5.2 which allowed your invalid queue definition to resolve to a queue name in the cluster, and that this bug has been fixed in one of the many CSDs since.
Check the APG table 3, Queue name resolution, for the definiitive guide.
Can you post your definitions (just the affected queues)?
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| nina |
| Posted: Tue Oct 18, 2005 8:20 am Post subject: |
|
|
Novice
Joined: 13 Sep 2005
Posts: 11
|
Here are more specific information.
AIX version 4.3.3 patch 10
MQ version 5.2.0 CSD 6, and we upgraded to MQ 5.3 CSD10
Here alias queue definition on Gateway Queue Manager
dis qalias(UPX.GL.EDINA.REQUEST) all
3 : dis qalias(UPX.GL.EDINA.REQUEST) all
AMQ8409: Display Queue details.
DESCR( ) TARGQ(UPX.GL.EDINA.REQUEST)
CLUSTER(CLUNTR) CLUSNL( )
QUEUE(UPX.GL.EDINA.REQUEST) ALTDATE(2004-05-24)
ALTTIME(11.09.12) GET(ENABLED)
PUT(ENABLED) DEFPRTY(0)
DEFPSIST(NO) SCOPE(QMGR)
DEFBIND(NOTFIXED) TYPE(QALIAS)
Let me know for any other information.
Thanks, and Regards,
Nina |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 18, 2005 8:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is that really a circular qalias, pointing back to itself?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| nina |
| Posted: Tue Oct 18, 2005 8:39 am Post subject: |
|
|
Novice
Joined: 13 Sep 2005
Posts: 11
|
Not actually, TARGQ(UPX.GL.EDINA.REQUEST) is on other queue manager which is in cluster CLUNTR. We defined QALIAS on overlapped Gateway Queue Manager to put messages from other cluster Queue Mangers.
Thanks, and Regards,
Nina |
|
| Back to top |
|
|
| mq_developer |
| Posted: Tue Oct 18, 2005 9:50 am Post subject: |
|
|
Voyager
Joined: 18 Feb 2002
Posts: 82
|
Your qalias on gateway should look like this ..
DEF QA(UPX.GL.EDINA.REQUEST) TARGQ(UPX.GL.EDINA.REQUEST)
CLUSTER('DifferentClusterName') ( or, if you can leave the Cluster name blank , but definitely not CLUNTR)
On the queue manager where you have the queue it should be like
DEF QA(UPX.GL.EDINA.REQUEST) TARGQ(UPX.GL.EDINA.REQUEST)
CLUSTER('CLUNTR')
So now on your gateway, queue UPX.GL.EDINA.REQUEST will be advertised in cluster 'DifferentClusterName' and the real queue will be in 'CLUNTR'.
From your current defintions you should getting the error that you are getting as per name resolution , because you have advertised your gateway queue manager definition in the same cluster as the target queue in other queue manager which will result in circular reference.
cheers |
|
| Back to top |
|
|
| nina |
| Posted: Tue Oct 18, 2005 10:28 am Post subject: |
|
|
Novice
Joined: 13 Sep 2005
Posts: 11
|
I am sorry, TARGQ(UPX.GL.EDINA.REQUEST) is on other queue manager which is in cluster CLUNGL.
I was working fine before upgrade, and we never had problems with Clusters and overlapping Gateway Queue manager.
Do we need to do anything for mqs.ini file after upgrade?
Please let me know.
Regards,
Nina |
|
| Back to top |
|
|
| mq_developer |
| Posted: Tue Oct 18, 2005 11:17 am Post subject: |
|
|
Voyager
Joined: 18 Feb 2002
Posts: 82
|
Can you issue the following display and post the results ..
On Gateway Qmgr , dis qcluster(UPX.GL.EDINA.REQUEST) all
once again on Gateway Qmgr , dis ql(SYSTEM.CLUSTER.COMMAND.QUEUE) all
Where does this error (2001) occur , which queue manager ? |
|
| Back to top |
|
|
| nina |
| Posted: Tue Oct 18, 2005 11:25 am Post subject: |
|
|
Novice
Joined: 13 Sep 2005
Posts: 11
|
dis qcluster(UPX.GL.EDINA.REQUEST) all
1 : dis qcluster(UPX.GL.EDINA.REQUEST) all
AMQ8409: Display Queue details.
DESCR( ) CLUSTER(CLUNTR)
QUEUE(UPX.GL.EDINA.REQUEST) CLUSQMGR(QMUNGTR003)
QMID(QMUNGTR003_2003-12-24_00.19.2 CLUSDATE(2005-10-17)
CLUSTIME(19.39.17) ALTDATE(2005-10-17)
ALTTIME(00.07.53) CLUSQT(QALIAS)
TYPE(QCLUSTER) PUT(DISABLED)
DEFPRTY(0) DEFPSIST(NO)
DEFBIND(OPEN)
AMQ8409: Display Queue details.
DESCR( ) CLUSTER(CLUNTR)
QUEUE(UPX.GL.EDINA.REQUEST) CLUSQMGR(QMUNGTR001)
QMID(QMUNGTR001_2002-07-26_14.17.13) CLUSDATE(2005-10-17)
CLUSTIME(19.39.17) ALTDATE(2005-10-16)
ALTTIME(20.02.12) CLUSQT(QALIAS)
TYPE(QCLUSTER) PUT(DISABLED)
DEFPRTY(0) DEFPSIST(NO)
DEFBIND(OPEN)
AMQ8409: Display Queue details.
DESCR( ) CLUSTER(CLUNGL)
QUEUE(UPX.GL.EDINA.REQUEST) CLUSQMGR(QMUNBTR002)
QMID(QMUNBTR002_2002-06-26_13.21.22) CLUSDATE(2005-10-17)
CLUSTIME(19.39.09) ALTDATE(2004-05-24)
ALTTIME(11.22.39) CLUSQT(QLOCAL)
TYPE(QCLUSTER) PUT(DISABLED)
DEFPRTY(0) DEFPSIST(YES)
DEFBIND(NOTFIXED)
AMQ8409: Display Queue details.
DESCR( ) CLUSTER(CLUNGL)
QUEUE(UPX.GL.EDINA.REQUEST) CLUSQMGR(QMUNBTR006)
QMID(QMUNBTR006_2003-12-23_22.59.19) CLUSDATE(2005-10-17)
CLUSTIME(19.39.09) ALTDATE(2005-10-16)
ALTTIME(23.44.57) CLUSQT(QLOCAL)
TYPE(QCLUSTER) PUT(DISABLED)
DEFPRTY(0) DEFPSIST(NO)
DEFBIND(OPEN)
AMQ8409: Display Queue details.
DESCR( ) CLUSTER(CLUNGL)
QUEUE(UPX.GL.EDINA.REQUEST) CLUSQMGR(QMUNBTR004)
QMID(QMUNBTR004_2003-06-26_18.03.34) CLUSDATE(2005-10-17)
CLUSTIME(19.39.09) ALTDATE(2004-05-24)
ALTTIME(11.05.46) CLUSQT(QLOCAL)
TYPE(QCLUSTER) PUT(ENABLED)
DEFPRTY(0) DEFPSIST(YES)
DEFBIND(NOTFIXED)
AMQ8409: Display Queue details.
DESCR( ) CLUSTER(CLUNTR)
QUEUE(UPX.GL.EDINA.REQUEST) CLUSQMGR(QMUNGTR002)
QMID(QMUNGTR002_2003-06-26_18.06.50) CLUSDATE(2004-05-24)
CLUSTIME(11.09.12) ALTDATE(2004-05-24)
ALTTIME(11.09.12) CLUSQT(QALIAS)
TYPE(QCLUSTER) PUT(ENABLED)
DEFPRTY(0) DEFPSIST(NO)
DEFBIND(NOTFIXED)
dis ql(SYSTEM.CLUSTER.COMMAND.QUEUE) all
2 : dis ql(SYSTEM.CLUSTER.COMMAND.QUEUE) all
AMQ8409: Display Queue details.
DESCR(MQSeries Cluster Command Queue) PROCESS( )
BOQNAME( ) INITQ( )
TRIGDATA( ) CLUSTER( )
CLUSNL( ) QUEUE(SYSTEM.CLUSTER.COMMAND.QUEUE)
CRDATE(2003-06-26) CRTIME(18.06.51)
ALTDATE(2003-06-26) ALTTIME(18.06.51)
GET(ENABLED) PUT(ENABLED)
DEFPRTY(0) DEFPSIST(NO)
MAXDEPTH(640000) MAXMSGL(4194304)
BOTHRESH(0) SHARE
DEFSOPT(SHARED) HARDENBO
MSGDLVSQ(PRIORITY) RETINTVL(999999999)
USAGE(NORMAL) NOTRIGGER
TRIGTYPE(FIRST) TRIGDPTH(1)
TRIGMPRI(0) QDEPTHHI(80)
QDEPTHLO(20) QDPMAXEV(ENABLED)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QSVCINT(999999999) QSVCIEV(NONE)
DISTL(NO) NPMCLASS(NORMAL)
DEFTYPE(PREDEFINED) TYPE(QLOCAL)
SCOPE(QMGR) DEFBIND(OPEN)
IPPROCS(1) OPPROCS(0)
CURDEPTH(0)
All failed messages are going to DEADQ of Gateway Queue Manager, and log file has 2001 error.
Let me know for any further information.
Thanks, and Regards,
Nina |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Oct 18, 2005 1:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Nina, What are you trying to do. All those queues show put(disabled)? Very strange for a gateway qmgr !!!
Enjoy  |
|
| Back to top |
|
|
|
|
