| Author |
Message
|
| bdrummond |
 Posted: Fri Jul 23, 2010 12:05 am Post subject: Problem removing MQ v7 |
 |
|
Disciple
Joined: 06 May 2004
Posts: 164
|
I am trying to remove WMQ v7.0.1.1 from my windows box and have come up against a problem that is rather confusing.
When removing the fixpack, an error occurred and my pc restarted.
Now when trying to remove the product, I am unable to do so.
dspmqver shows v7.0.1.1.
Removing fixpack through start>programs<IBM Websphere MQ>Remove Fix Pack 7.0.1.1 gives an error stating "No maintenance is installed (AMQ4762)
Removing the base product through setup.exe gives an error stating: "Cannot overwrite Websphere MQ Version 7.0.1.1 with vVersion 7.0.0.0 (AMQ4763)
IBM Websphere MQ DOES NOT appear in the "Add/Remove Programs list"
I am also unable to remove MQ using the msiexec program.
So basically, my windows box doesn't have a clue which version (if any) of MQ is installed.
Is there any way I can resolve this issue (Registry/File System settings perhaps..?) without rebuilding my PC..?
Any help would be greatly appreciated
Thanks in advance. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Jul 23, 2010 2:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Yes, it's pretty much just that.
Delete the files, delete the registry entries.
If you want to retain the queue managers, you need to be a bit selective about the files you delete.
Are you trying to remove 7.0.1.1 and roll back to 7.0.0.0?
Or... ? |
|
| Back to top |
|
|
| bdrummond |
| Posted: Fri Jul 23, 2010 2:20 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
Hi Jeff,
I am trying to remove v7 completely and move back to v6.
Ideally I want to keep the queue managers but it won't be the end of the day if I have to recreate them.
Cheers. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 23, 2010 2:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Well, then delete any registry entries you find for MQSeries - start with HKLM-Software-IBM-MQSeries.
And don't delete anything in the file system that on unix would be in /var/mqm rather than in /opt/mqm (i.e. <program install>/qmgrs) |
|
| Back to top |
|
|
| bdrummond |
| Posted: Fri Jul 23, 2010 2:31 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
Thanks Jeff, I'll give that a go and will let you know how I get on.
Cheers. |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Jul 23, 2010 3:05 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| bdrummond wrote: |
Hi Jeff,
I am trying to remove v7 completely and move back to v6.
Ideally I want to keep the queue managers but it won't be the end of the day if I have to recreate them.
Cheers. |
I think you'll have to anyway due to the differences in queue manager objects etc., but will be interested in the results - always happy to be proved wrong 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bdrummond |
| Posted: Fri Jul 23, 2010 6:56 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
| exerk wrote: |
| bdrummond wrote: |
Hi Jeff,
I am trying to remove v7 completely and move back to v6.
Ideally I want to keep the queue managers but it won't be the end of the day if I have to recreate them.
Cheers. |
I think you'll have to anyway due to the differences in queue manager objects etc., but will be interested in the results - always happy to be proved wrong |
Unfortunately (for me) you are correct. Have managed to install MQ but have had to recreate all of the queue managers.  |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Aug 10, 2010 12:02 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
A related question
Upgrade existing QMs from MQ v6 to MQ v7 on AIX
If we decide to revert to v6 after the upgrade. We can use SMIT to remove the applied v7 software.
Do we then have to restore the queue manager data files (/var/mqm) from a pre-upgrade copy or will the "updated" queue manager data files also work with MQ v6?
Last edited by zpat on Tue Aug 10, 2010 12:17 am; edited 1 time in total |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Aug 10, 2010 12:16 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
You'll have to use the pre-upgrade copy, or recreate the queue manager(s). And don't forget the pre-upgrade mqs.ini file (just in case you've made some custom changes).
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Aug 10, 2010 12:18 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Are you saying the mqs.ini file is changed back to a default version by the V7 upgrade?
Is anything else regressed (exits64 for example)? |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Aug 10, 2010 12:59 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| zpat wrote: |
Are you saying the mqs.ini file is changed back to a default version by the V7 upgrade?
Is anything else regressed (exits64 for example)? |
To be honest, I'm not sure. We hit a few issues at the shop where I am currently, but regression for us meant going back a version further than you are. As such, we made the decision to safeguard anything that could potentially be changed, and restore all WMQ-related files back to their original pre-migration configuration. What I stated may not be applicable to you, but I high-light it as a potential gotcha.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Aug 10, 2010 5:04 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| zpat wrote: |
Are you saying the mqs.ini file is changed back to a default version by the V7 upgrade?
Is anything else regressed (exits64 for example)? |
I'd be very surprised if an MQ upgrade took out things of the ini file. Although its more likely it may add new things that only apply in the newer version and cause grief in the older version if you roll back.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Aug 10, 2010 9:58 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I don't think this downgrade process is very slick. It would be better if IBM allowed the updating of the queue manager data to be independent of the software level.
This would then be a bit like RACF, you apply the new templates to the RACF database but it works with both software levels, simply ignoring anything in the data that is not applicable.
Having to restore the queue manager data would mean a horrendous outage if we decided to back out after having run some production work. We would have to backup every queue separately, restore the old filesystem, remove all the old messages and restore the latest messages. All this as well as restoring the actual software version. Talk about stress! |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Aug 10, 2010 10:43 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| PeterPotkay wrote: |
| I'd be very surprised if an MQ upgrade took out things of the ini file. Although its more likely it may add new things that only apply in the newer version and cause grief in the older version if you roll back. |
A very valid point, and well made. I didn't get the chance to do a before-and-after compare, not on the candidate systems anyway, but hopefully I will when we actually start to roll the upgrade. Our focus was to ensure a smooth-as-possible roll-back (if necessary) as we are approaching being three years out-of-service.
| zpat wrote: |
| Having to restore the queue manager data would mean a horrendous outage if we decided to back out after having run some production work. We would have to backup every queue separately, restore the old filesystem, remove all the old messages and restore the latest messages. All this as well as restoring the actual software version. Talk about stress! |
I feel your pain. Luckily for us the bulk of the applications here are time-dependent so we will not be worrying about any unprocessed messages, and as for the rest we have made it a dependency that applications drain their queues or we will and reload them after the upgrade.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Aug 10, 2010 11:18 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Yes, but the point is that problems may only be evident after the new version has been in use for a while and queue have fresh data on them.
Even a HA failover (to a side with V6 installed) won't really help because the data restore would still be necessary.
The ideal would be to allow multiple versions of MQ to run at the same time and to move queue managers easily between the versions without the need to restore data. |
|
| Back to top |
|
|
|
|
