| Author |
Message
|
| hin3407 |
 Posted: Mon Mar 17, 2008 7:13 am Post subject: Upgrading from WMQv5.3 to WMQv6.x & High Availibity of W |
 |
|
Centurion
Joined: 17 Oct 2006
Posts: 120
|
We are looking to upgrade WMQ on a SUN server that currently has WMQv5.3 to WMQv6.0.2.2.
This SUN server participates in High Availability for Websphere WMQ with another passive SUN server utilizing the MC91 Support Pac (http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24011869&loc=en_US&cs=utf-8&lang=en)
Are there any important considerations to consider when upgrading from WMQv5.3 to WMQv6.x since MC91 is installed.
Thanks. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Mon Mar 17, 2008 8:53 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
| KramJ |
| Posted: Mon Mar 17, 2008 9:38 am Post subject: |
|
|
Voyager
Joined: 09 Jan 2006
Posts: 80
Location: Atlanta
|
I've upgrade several AIX HACMP clusters from 5.3 to 6.0.2.2. I've got just a couple of tips that may be obvious.
Be sure to upgrade both nodes at the same time. If you upgrade one to 6.0.2.2 and leave the other at 5.3 and you need to fail over from the node running version 6 to the node running version 5.3 you won't be able to bring up MQ since the objects will have been upgraded to version 6 objects.
Also make sure to start up your queue manager after the upgrade to the base 6.0 version and let it convert the MQ objects before upgrading to 6.0.2.2.
Most everything else is pretty straight forward. |
|
| Back to top |
|
|
| hin3407 |
| Posted: Mon Mar 17, 2008 9:42 am Post subject: |
|
|
Centurion
Joined: 17 Oct 2006
Posts: 120
|
| Thanks for that last response. That is very helpful. I will make sure to start WMQ after the base install. I will upgrade the passive server first, and then start WMQ, and then go to the fix patches/packs, and then go to the active server and upgrade WMQ there. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Mar 17, 2008 12:04 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| KramJ wrote: |
Also make sure to start up your queue manager after the upgrade to the base 6.0 version and let it convert the MQ objects before upgrading to 6.0.2.2. |
This was an issue related to upgrading MQ where SSL channels were involved. At the latest version of MQ, 6.0.2.3, this is not a problem.
A collegue on the list serve wrote:
| Quote: |
| When I raised a PMR to ask the question of correct migration technique, the recommendation from IBM was that installing the latest fix pack before restarting the queue manager was the best technique, as it would have the lowest probability of introducing problems. However, this was providing you either did not have SSL issues, or could use a software level which did not have the SSL migration problem (6.0.2.3). If you did not fit in that category, you had to restart the queue manager at 6.0.0.0 in order to avoid the migration bug. |
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
