Author |
Message
|
jeevan |
Posted: Fri Feb 19, 2010 2:45 pm Post subject: DSPMQVER does not show newly installed FP version |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
I had to install MQ fixpac 7.0.1.1 over 7.0.0.0 on windows. I did not reboot as the installation process because I was testing a script to be deployed in our stores server where we will not reboot the server immediatelly. However, I reboot manually when the script finished.
Afer reboot, when I ran the dspmqver, it was still showing 7.0.0.0
However, under program it has added -->Remove fixpac 7.0.1.1 correctly , and a directoy -->maint 1.1 was created under the websphere MQ directory.
What and Where does this command DSPMQVER check for fixpac installation? what could have gone wrong so that the dspmqver is still showing the old version still?
This is first time I am having this error.
Last edited by jeevan on Sun Feb 21, 2010 6:48 am; edited 5 times in total |
|
Back to top |
|
 |
Vitor |
Posted: Fri Feb 19, 2010 2:57 pm Post subject: Re: DSPMQVER does not show newly installed FP version |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
jeevan wrote: |
what could have gone wrong? ... This is first time I am having this error. |
Because this is the first time you've not got lucky because...
jeevan wrote: |
I did not reboot as the installation process |
So it's gone ok on all the other Windows servers you've done this on. It's probably not the first time you've seen something not happen on a Windows server (or happen on a Windows server) that's happened (or not happened) on 1-n identically configured Windows servers.
You can't expect consistent results if you don't follow the procedure. And you can't expect any installation or configuration action on Windows to work without a reboot.
It shouldn't be true. But this is the world we live in.  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri Feb 19, 2010 6:40 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
You must reboot after applying an MQ Fix Pack on Windows. A recent PMR I opened confirmed this. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
jeevan |
Posted: Sat Feb 20, 2010 8:06 pm Post subject: Re: DSPMQVER does not show newly installed FP version |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
Vitor wrote: |
So it's gone ok on all the other Windows servers you've done this on. It's probably not the first time you've seen something not happen on a Windows server (or happen on a Windows server) that's happened (or not happened) on 1-n identically configured Windows servers.
You can't expect consistent results if you don't follow the procedure. And you can't expect any installation or configuration action on Windows to work without a reboot.
It shouldn't be true. But this is the world we live in.  |
Vitor,
Thank you for the reply. Let me clarify a few points.
I made mistake in my first post when I said i did not reboot the server. In fact, I reboot the server but after the installation was finished. I did not reboot as a process because I was testing a script to be deployed in thousand of servers.
So, computer was rebooted after the installation. So, I was follwoing the procedure.
dspmqver did not show the version changed after reboot.
Second question, lets say for whatever reasons it did not show the version, is there any other way to check actually the fixpac is applied?
Thanks as usual.
Last edited by jeevan on Sun Feb 21, 2010 6:50 am; edited 2 times in total |
|
Back to top |
|
 |
jeevan |
Posted: Sat Feb 20, 2010 8:08 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
PeterPotkay wrote: |
You must reboot after applying an MQ Fix Pack on Windows. A recent PMR I opened confirmed this. |
Peter,
it was my mistake in posting. In fact I rebooted the server. what I meant was I did not reboot inside the script(MQPREBOOT=0 ) but I rebooted when the script finished running.
I checked the version after the reboot not before the reboot. I know, in order to get the fixpac effective, the server has to be rebooted in case of windows.
Last edited by jeevan on Sun Feb 21, 2010 4:15 am; edited 1 time in total |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Feb 21, 2010 4:12 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
As this is windows ... are you sure you installed with the file in use ok flag?
I thought that was mandatory for a silent install...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jeevan |
Posted: Sun Feb 21, 2010 4:17 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
fjb_saper wrote: |
As this is windows ... are you sure you installed with the file in use ok flag?
I thought that was mandatory for a silent install...  |
Yes. I used the following script,
webSphereMQMDV7.0.1.1EnUs.exe -s -a MQPLOG="C:\WMQBACKUP\WM QUPDATEINSTALL.log" MQPSILENT=1 MQPREBOOT=0 MQPINUSEOK=1 |
|
Back to top |
|
 |
exerk |
Posted: Sun Feb 21, 2010 4:30 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
What do the values of HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\VRMF and HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Maintenance Applied\Shipped show?
I'm not sure that FixPack 7.0.1.1 will take effect unless you have applied RefreshPack 7.0.1 beforehand, or have WMQ 7.0.1 installed as base. _________________ 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 |
|
 |
jeevan |
Posted: Sun Feb 21, 2010 5:18 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
exerk wrote: |
What do the values of HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\VRMF and HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Maintenance Applied\Shipped show?
I'm not sure that FixPack 7.0.1.1 will take effect unless you have applied RefreshPack 7.0.1 beforehand, or have WMQ 7.0.1 installed as base. |
We have thought about this but when we re-checked the IBM site -->http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24024528 for prerequisite, says very clearly that :
Prerequisites
Install this fix pack on top of IBM WebSphere MQ V7.0.0.0, WMQ V7.0.0.1, WMQ V7.0.0.2 or WMQ V7.0.1.0. The links below give the supported environments for WebSphere MQ V7.0.
I am planning to do a few tests: install it manually, install fixpac 7.0.1.0 and install 7.0.1.1 over it and /or open a PMR to IBM. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Sun Feb 21, 2010 5:23 am Post subject: Re: DSPMQVER does not show newly installed FP version |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
jeevan wrote: |
Second question, lets say for wtatever reasons it did not show the version, is there any other way to check actually the fixpac is applied?
|
Doesn't matter. If dspmqver is not showing the correct version, I don't care what else maybe showing a different version #. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
exerk |
Posted: Sun Feb 21, 2010 5:25 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
jeevan wrote: |
...We have thought about this but when we re-checked the IBM site -->http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24024528 for prerequisite, says very clearly that :
Prerequisites
Install this fix pack on top of IBM WebSphere MQ V7.0.0.0, WMQ V7.0.0.1, WMQ V7.0.0.2 or WMQ V7.0.1.0. The links below give the supported environments for WebSphere MQ V7.0.
... |
Another of my doh! moments  _________________ 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 |
|
 |
Vitor |
Posted: Sun Feb 21, 2010 8:41 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
jeevan wrote: |
webSphereMQMDV7.0.1.1EnUs.exe -s -a MQPLOG="C:\WMQBACKUP\WM QUPDATEINSTALL.log" MQPSILENT=1 MQPREBOOT=0 MQPINUSEOK=1 |
So just to be clear, and remove confusion:
You put the fix pack on a server running 7.0.0.0;
You executed the above script;
At a later point the server was rebooted;
You did a dspmqver & it still showed 7.0.0.0
Or
You put the fix pack on a server running 7.0.0.0;
You executed the above script;
You ran dspmqver to see if the script had worked & it still showed 7.0.0.0
The first indicates a failed install, the second is as expected. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
jeevan |
Posted: Sun Feb 21, 2010 10:28 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
Vitor wrote: |
jeevan wrote: |
webSphereMQMDV7.0.1.1EnUs.exe -s -a MQPLOG="C:\WMQBACKUP\WM QUPDATEINSTALL.log" MQPSILENT=1 MQPREBOOT=0 MQPINUSEOK=1 |
So just to be clear, and remove confusion:
You put the fix pack on a server running 7.0.0.0;
You executed the above script;
At a later point the server was rebooted;
You did a dspmqver & it still showed 7.0.0.0
Or
You put the fix pack on a server running 7.0.0.0;
You executed the above script;
You ran dspmqver to see if the script had worked & it still showed 7.0.0.0
The first indicates a failed install, the second is as expected. |
I did the first one but also issued dspmqver before reboot. That means
I put the fix pack on a server running 7.0.0.0;
I executed the above script;
I ran dspmqver to see if the script had worked & it still showed 7.0.0.0
I, at a later point, rebooted the server;
I ran a dspmqver & it still showed 7.0.0.0
I ran the first dspmqver out of my curiosity. I knew server reboot is required to get the fixpac into effect.
Also, I treid this two times, unstall and reintall but the same result.
This is our requirement as our server are running mq 7.0.0.0 and we are planning to update with latest fixpac 7.0.1.1. |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Feb 21, 2010 2:06 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Check in the install log why the upgrade failed...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
Vitor |
Posted: Sun Feb 21, 2010 2:39 pm Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
fjb_saper wrote: |
Check in the install log why the upgrade failed...  |
As I said above, this indicates the install has failed.
As I said further above, it doesn't matter if it's worked on 1-n identically configured Windows servers. It's failed on this one. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|