| Author |
Message
|
| troy |
 Posted: Thu Jan 21, 2010 11:09 am Post subject: MQ5.3 to MQ6.0.2.1 |
 |
|
Novice
Joined: 07 Jan 2009
Posts: 20
|
Hi,
I am going to upgrade the box from MQ5.3 to MQ6.0.2.1.
I have planned to run the saveqmgr utility to take the backup of existing queue manager configuration.
Now, which one is the better option to go ahead for the upgrade from the below two-.
1. Run the saveqmgr->uninstall5.3->install MQ6.0.2.1->run the saveqmgr to create the configuration.
2. Take the back up of the queue manager directories and log directories ->uninstall5.3->install MQ6.0.2.1->place the backup directories again.
Query regarding second option is ->Will the backup taken of directories at the time of ver5.3 be compatible with MQ6.0.2.1.
Please suggest.
Thanks!! |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jan 21, 2010 11:23 am Post subject: Re: MQ5.3 to MQ6.0.2.1 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| troy wrote: |
| I am going to upgrade the box from MQ5.3 to MQ6.0.2.1. |
What OS?
| troy wrote: |
| Now, which one is the better option to go ahead for the upgrade from the below two-. |
It depends if you have any messages sitting on any queues or not. If you do, option 1 will remove them.
Option 1 is however the better option if you have no messages on the queue, or add additional steps to unload & reload the queues at appropriate points.
If you're required to remove v5.3 before installing v6. It's not a technical requirement on all platforms. If you upgrade in place then the queue manager will convert the data on first start up. This should be true if you restore the directories but I'm not certain & I've never tried it. I've used the augmented Option 1 (save definition & queue contents) when I've not been able to upgrade in place.
Naturally a full system backup before you start remains a wise precaution no matter what you end up doing. You can't go wrong with a solid rollback plan. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| troy |
| Posted: Thu Jan 21, 2010 11:39 am Post subject: |
|
|
Novice
Joined: 07 Jan 2009
Posts: 20
|
Thanks a lot Vitor.
The OS is Solaris 5.9 Would you like to add on any pointers after knowing the OS. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 21, 2010 11:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| troy wrote: |
| The OS is Solaris 5.9 Would you like to add on any pointers after knowing the OS. |
Forget the upgrade in place, which isn't valid on Solaris. Follow the migration instructions like you're bolted to them & use Option 1, saving messages if appropriate.
Do that, works a treat, done it a hundred times.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| troy |
| Posted: Thu Jan 21, 2010 1:09 pm Post subject: |
|
|
Novice
Joined: 07 Jan 2009
Posts: 20
|
Thanks a lot Vitor. I will go ahead with the option 1.
Thanks again.  |
|
| Back to top |
|
|
| bbburson |
| Posted: Thu Jan 21, 2010 2:21 pm Post subject: Re: MQ5.3 to MQ6.0.2.1 |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
| troy wrote: |
| 1. Run the saveqmgr->uninstall5.3->install MQ6.0.2.1->run the saveqmgr to create the configuration. |
The highlighted parts of your step 1 do not remove the queue manager files. After installing v6.0.2.1 you just start up the queue manager(s) and MQ does the necessary conversions of objects in the background.
You definitely want to include saveqmgr (saving the authorizations as well) in case something goes bad along the way and you end up having to rebuild queue managers. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 21, 2010 2:58 pm Post subject: Re: MQ5.3 to MQ6.0.2.1 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bbburson wrote: |
| The highlighted parts of your step 1 do not remove the queue manager files. |
Really? I thought Solaris pkgrm cleared out /var/mqm?
My bad. Seen one Unix, seen them all.
Given that, then I agree that running the new configuration in is redundant for the reasons so clearly given.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
