|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQ error opening topic handle, 2035 after MQ/MB Migration... |
« View previous topic :: View next topic » |
Author |
Message
|
prat31 |
Posted: Thu Sep 12, 2013 4:19 am Post subject: MQ error opening topic handle, 2035 after MQ/MB Migration... |
|
|
Apprentice
Joined: 01 Feb 2013 Posts: 30
|
Hi All,
Recently we upgraded from MQ6 to MQ7 and on the next day from MB6 to MB8.
During the activity of MQ 7 upgrade we migrated the pub sub details from Broker database to MQ by using the below commands:-
migmbbrk -t -b PRD2.GEN.BRK
migmbbrk -c -b PRD2.GEN.BRK
After this the MB was in version 6 and MQ in version 7 and the Pub sub interfaces were working fine.
On the next day we migrated the Brokers from MB 6 to MB8. But after this apart from the 2 pub sub flows the other pub sub flows were working fine. For the two pub sub flows which publish the messages we were getting the below error.
"Exception, MQ error opening topic handle, 2035, LDMPub, 2"
Where LDMPub is the Topic Name in the Pub SUb Flow.
The OS is Solaris SPARC.
Request you to help in getting the exact reasons for only the 2 pub sub flows giving this errors and the remaining working fine.
Thanks. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Thu Sep 12, 2013 4:25 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
|
Back to top |
|
 |
prat31 |
Posted: Thu Sep 12, 2013 4:34 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013 Posts: 30
|
Hi,
Ya I got the reason MQRC_NOT_AUTHORIZED... But it is throwing this error only for two pub sub flows and remaining are working fine in the same Broker... |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 12, 2013 4:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
prat31 wrote: |
But it is throwing this error only for two pub sub flows and remaining are working fine in the same Broker... |
Firstly, don't double post. If you think you've posted in the wrong section ask a moderator to move it.
Secondly, if you only have 2 flows throwing 2035 errors then only those flows are not getting the authorization they need and the other flows are. Locate the missing authorizations & either add them, or modify the flows to not need them. Simple. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Sep 12, 2013 5:52 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
It's almost like there wasn't a recent post discussing security and publish/subscribe with the Broker Publication node. |
|
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
|
|
|
|