| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Queue Manager not starting after upgrade to version 8.0.0.4 |
« View previous topic :: View next topic » |
| Author |
Message
|
| 51392276 |
 Posted: Mon Sep 11, 2017 9:12 pm Post subject: Queue Manager not starting after upgrade to version 8.0.0.4 |
 |
|
Newbie
Joined: 11 Sep 2017
Posts: 2
|
Hi,
Recently we have upgraded queue manager for Solaris 10 (SPARC x64 bit).
Previous version <7.5.0.6>
Upgraded version <8.0.0.4>
Queue manager is under cluster resource. We are using Solaris Cluster version 3.3U2.
Before upgrade we delete the cluster resources responsible for managing queue manager , channel and listener.
Upgrade was successful.
After upgrade we again configure the resources using Solaris in built resource add command.
/opt/SUNWscmqs/mgr/util/mgr_register
/usr/cluster/bin/clrs enable <Resource Name>
But when tried to enable the cluster resource it did not became online. I checked the MQ error message and found
AMQ8597 was logged in the errors.
/opt/.../libmqmcs.so is not supported library.
I delete the soft links for libmqcs and libmqmzse and tried to again enable the cluster resource.
This time, AMQ8597 was not logged but somehow queue manager could not be started and cluster resource did not come online.
After this I checked the Solaris log messages and found the following.
Sep 12 10:57:40 G3TECP11 SC[SUNWscmqs.qmgr.start]:G3TECPV1-rgmq:G3TECPV1-rsmq: [ID 567783 daemon.notice] strmqm rc(0) - WebSph
ere MQ queue manager 'UMHCBRT1' starting.
Sep 12 10:57:40 G3TECP11 SC[SUNWscmqs.qmgr.start]:G3TECPV1-rgmq:G3TECPV1-rsmq: [ID 567783 daemon.notice] strmqm rc(0) - The qu
eue manager is associated with installation 'Installation3'.
Sep 12 10:57:40 G3TECP11 SC[SUNWscmqs.qmgr.start]:G3TECPV1-rgmq:G3TECPV1-rsmq: [ID 567783 daemon.notice] strmqm rc(0) - 5 log
records accessed on queue manager 'UMHCBRT1' during the log replay phase.
Sep 12 10:57:40 G3TECP11 SC[SUNWscmqs.qmgr.start]:G3TECPV1-rgmq:G3TECPV1-rsmq: [ID 567783 daemon.notice] strmqm rc(0) - Log re
play for queue manager 'UMHCBRT1' complete.
Sep 12 10:57:40 G3TECP11 SC[SUNWscmqs.qmgr.start]:G3TECPV1-rgmq:G3TECPV1-rsmq: [ID 567783 daemon.notice] strmqm rc(0) - Transa
ction manager state recovered for queue manager 'UMHCBRT1'.
Sep 12 10:57:40 G3TECP11 SC[SUNWscmqs.qmgr.start]:G3TECPV1-rgmq:G3TECPV1-rsmq: [ID 567783 daemon.notice] strmqm rc(0) - WebSph
ere MQ queue manager 'UMHCBRT1' started using V8.0.0.4.
Sep 12 10:57:48 G3TECP11 SC[SUNWscmqs.qmgr.test]:G3TECPV1-rgmq:G3TECPV1-rsmq: [ID 779412 daemon.notice] check_qmgr - <>
Sep 12 11:02:02 G3TECP11 last message repeated 118 times
Sep 12 11:02:04 G3TECP11 SC[SUNWscmqs.qmgr.test]:G3TECPV1-rgmq:G3TECPV1-rsmq: [ID 779412 daemon.notice] check_qmgr - <>
Sep 12 11:02:38 G3TECP11 last message repeated 16 times
Sep 12 11:02:39 G3TECP11 Cluster.RGM.global.rgmd: [ID 764140 daemon.error] Method <gds_svc_start> on resource <G3TECPV1-rsmq>,
resource group <G3TECPV1-rgmq>, node <G3TECP11>: Timeout.
So, I am not sure what is causing this problem.
We did the same procedure last year when we upgraded to version 7.5.0.6 and did not encounter such problem.
Any help is really appreciated.
Thanks,
Praveen |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Sep 12, 2017 6:07 am Post subject: Re: Queue Manager not starting after upgrade to version 8.0. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| 51392276 wrote: |
Sep 12 10:57:40 G3TECP11 SC[SUNWscmqs.qmgr.start]:G3TECPV1-rgmq:G3TECPV1-rsmq: [ID 567783 daemon.notice] strmqm rc(0) - WebSph
ere MQ queue manager 'UMHCBRT1' started using V8.0.0.4.
Sep 12 10:57:48 G3TECP11 SC[SUNWscmqs.qmgr.test]:G3TECPV1-rgmq:G3TECPV1-rsmq: [ID 779412 daemon.notice] check_qmgr - <>
Sep 12 11:02:02 G3TECP11 last message repeated 118 times
Sep 12 11:02:04 G3TECP11 SC[SUNWscmqs.qmgr.test]:G3TECPV1-rgmq:G3TECPV1-rsmq: [ID 779412 daemon.notice] check_qmgr - <>
Sep 12 11:02:38 G3TECP11 last message repeated 16 times
Sep 12 11:02:39 G3TECP11 Cluster.RGM.global.rgmd: [ID 764140 daemon.error] Method <gds_svc_start> on resource <G3TECPV1-rsmq>,
resource group <G3TECPV1-rgmq>, node <G3TECP11>: Timeout.
So, I am not sure what is causing this problem. |
It looks a lot to me like check_qmgr (which I theorize to be the cluster daemon that determines if the queue manger needs to fail over) is having trouble making that determination.
I would verify that the queue manager starts & operates normally if it's not under cluster control (that "queue manager started" message would imply that the queue manger did indeed start). If that's the case (and it looks like it is) then you need to troubleshoot that cluster service. Some security problem would be my first guess moving to v8, but that's just a guess.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| 51392276 |
| Posted: Wed Sep 13, 2017 6:55 pm Post subject: |
|
|
Newbie
Joined: 11 Sep 2017
Posts: 2
|
Hi,
Thank you for your reply. After lot of debugging, the problem was on the cluster side not MQ side.
Oracle has released a patch in 2014, for MQ-HA. After applying the cluster patch for MQ, everything works like a charm.
Thank you for help and information.
Thanks,
Praveen |
|
| 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
|
|
|
|
