|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
5.3 to 6.0.2 upgrade on Solaris + Veritas cluster |
« View previous topic :: View next topic » |
Author |
Message
|
Cliff |
Posted: Thu Feb 15, 2007 4:08 am Post subject: 5.3 to 6.0.2 upgrade on Solaris + Veritas cluster |
|
|
Centurion
Joined: 27 Jun 2001 Posts: 145 Location: Wiltshire
|
Folks,
my client has a pair of Solaris 9 machines hardware clustered with Veritas, and runs clustered queue managers on them. They also have a couple of qmgrs in the mq cluster but on non-h/w clustered Solaris boxes. They have no SSL, user exits or anything that might give 64-bit addressability problems to my knowledge.
Having checked the docs and various threads here, I reckon the upgrade process is this:
Backup the queue managers’ configuration using saveqmgr.
If the queue manager is on a high availability cluster:
Download and install the MC91 (High Availability for WebSphere MQ) Support Pac.
Run the hamigmqm script for all queue managers defined on each node of the cluster, irrespective of whether they’re active.
Disable failover for the HA cluster, then for each node continue with the upgrade steps below, but where indicated only start the queue managers that were active prior to the upgrade.
Stop all queue managers on the node.
Stop all listeners via endmqlsr or if inetd is being used, kill all the amqcrsta processes.
Check that no amq* and runmq* processes are running.
Backup the queue managers’ log and data file systems.
Uninstall WMQ 5.3 and any CSDs.
Install WMQ 6.
Start and stop each queue manager.
Install Refresh Pack 6.0.2.0
Start all queue managers and listeners.
Have I missed anything? Thanks all -
Cliff |
|
Back to top |
|
 |
HubertKleinmanns |
Posted: Thu Feb 15, 2007 4:31 am Post subject: |
|
|
 Shaman
Joined: 24 Feb 2004 Posts: 732 Location: Germany
|
Cliff,
you should have a to your cluster scripts. When you migrate to version 6 the command server will be started automatically. If you want to control this by cluster scripts or you do not want the command server, to become active, you should change the new QMgr attribute SCMDSERV to MANUAL. _________________ Regards
Hubert |
|
Back to top |
|
 |
Cliff |
Posted: Thu Feb 15, 2007 4:34 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001 Posts: 145 Location: Wiltshire
|
Well, that's one thing I missed! Hope there's not too much more ...
Thank, Hubert. |
|
Back to top |
|
 |
HubertKleinmanns |
Posted: Thu Feb 15, 2007 4:50 am Post subject: |
|
|
 Shaman
Joined: 24 Feb 2004 Posts: 732 Location: Germany
|
In version 6 you will have additional methods, to start a listener or trigger monitor, but the 5.3 procedures still work.
But there is one difference: The endmqlsr commands now works also, when the QMgr is running (in version 5.3 you had to use the - undocumented - flag "-f" therefore). _________________ Regards
Hubert |
|
Back to top |
|
 |
VCSIPMQ |
Posted: Thu Jul 31, 2008 1:37 pm Post subject: |
|
|
Newbie
Joined: 24 Jul 2008 Posts: 4
|
Hi Cliff,
Do you had Active/passive or Active/Active configuration in your environment ?
Could you please give us a little technical details how you did this configuration either Active/Active or Active/Passive.
Thanks a lot |
|
Back to top |
|
 |
Cliff |
Posted: Fri Aug 01, 2008 12:58 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001 Posts: 145 Location: Wiltshire
|
Sorry, but this was back in February last year and I have been working on other clients' sites since then, so I really can't be sure, but I believe it was active/passive.
Good luck -
Cliff |
|
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
|
|
|
|