| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Upgrade MQ Series on WIN2k to 5.3 |
« View previous topic :: View next topic » |
| Author |
Message
|
| noc@visionweb.com |
 Posted: Tue Jan 06, 2004 9:02 am Post subject: Upgrade MQ Series on WIN2k to 5.3 |
 |
|
Novice
Joined: 24 Nov 2003
Posts: 14
|
Hi, I need to upgrade my MQ Series 5.2 to 5.3. Any recommendations? Ive people talking about just upgrading? Does that work? Or should I backups queue managers, uninstall, install 5.3 and then restore? If so, how do I backup properly all the queue managers, queue's and channels on MQ?
Thanks in advance... |
|
| Back to top |
|
 |
| Prahasith |
| Posted: Tue Jan 06, 2004 9:50 am Post subject: |
|
|
Disciple
Joined: 16 May 2003
Posts: 184
Location: Kansas City
|
|
| Back to top |
|
|
| offshore |
| Posted: Tue Jan 06, 2004 9:58 am Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
Noc,
From my experience <for me anyways> it was easier to remove the old version and install the new version. Mostly because some performance monitoring software had a hold of some of the mq system files.
If you choose to remove/uninstall there is an option to keep all the data files. This includes your channels, queues and other mq definitions. Then when you goto install the new version, just point to that path and all the old definitions will be there.
------------------------------------------------------------------------------------
I think 5.2.1 installed to x:\Program Files\IBM\MQ Series\. MQ 5.3 wants to point to x:\Program Files\IBM\WebSphere MQ\.
------------------------------------------------------------------------------------
For backing up, you could use the saveqmgr support pac from IBM. I believe its support pac MS03. This will backup all your mq definitions(channels, queues, process....) Once MQ is installed, you can issue a runmqsc command to recreate all the definitions.
Or, you could always try to upgrade one and see if it goes smoothly. |
|
| Back to top |
|
|
| RatherBeGolfing |
| Posted: Tue Jan 06, 2004 12:04 pm Post subject: |
|
|
Centurion
Joined: 12 Nov 2002
Posts: 118
Location: Syracuse, NY, USA
|
I recently tried upgrading directly from V5.2 (csd4) to V5.3 (csd4) and found that while the upgrade of the base product seemed to go smoothly, the application of csd4 was difficult. Locked files were a big headache - I ended up getting it to work finally on 1 box (using listdlls utility from www.sysinternals.com to help me identify which services were holding mq resources), but I had to stop/disable so many Windows services, it wasn't worth it.
So, I ended up uninstalling and reinstalling MQ. Before anything, run saveqmgr to copy all your object definintions off to a tst file. Make sure you put it somewhere other than in the MQSeries file structure! Next, I carefully suspended my Queue Manager from the cluster, then I stopped the QMgr, deleted the QMgr and stopped the MQSeries service. At this point, I found it was useful to put the MQSeries service in manual mode and reboot the box. After it came back, I used listdlls to ensure no amq processes were running.
Next, I uninstalled the lastest CSD by selecting Start-Programs-IBM MQSeries-Remove Latest CSD. Then, using the MQ V5.2 install disk, I removed MQSeries. On the 2nd or 3rd prompt it detects you already have MQ installed and will ask if you want to delete MQ. I have also tried using Add/Remove programs, but have found that that can leave stuff behind in the file system and registry.
Anyway, after you think you have uninstalled, go back into the file system and delete the file system stuff left behind under x:\Program Files\IBM\MQSeries
At this point, there is a gotcha that got us on a few servers. Check your PATH statement to see if it is nearing the 1024 byte limit. If you think it is, edit in to shrink down some of the longer names (like \Program Files\ can become \Progra~1\. If you exceed the max, your new long entries for x:\Program Files\IBM\WebSphere MQ\bin\ may be truncated.
We ALWAYS rebooted the box at this point, just to refresh things that are cached.
Now, we reinstalled MQ, installed csd4, recreated the Queue manager (an excellent time to reconsider your logging options), rebuilt the MQ objects from the .tst file, regranted any MQ authorities, recreated trigger monitors, etc, etc.
This strategy worked well for us on about 22 servers.
Good luck!
Larry
Certifiably MQ |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Tue Jan 06, 2004 2:47 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
don't forget to save the qmgr/queue authorities using:
amqoamd -m Qmgrname -s > saved-auth-Qmgrname.cmd
this will save your authorities in setmqaut format and can be run against the newly created Qmgr...
Michael |
|
| 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
|
|
|
|
