| Author |
Message
|
| saurabh25281 |
 Posted: Wed May 30, 2007 3:24 am Post subject: Upgrading to MQ 6.0.2 - AMQ4760 |
 |
|
Centurion
Joined: 05 Nov 2006
Posts: 108
Location: Bangalore
|
Hi All,
I have been trying to upgrade our MQ systems to 6.0.2, we are currently running on 6.0.1.1
while installing the refresh pack i keep getting this error AMQ4760. I have tried installing with amqicsdn MQPINUSEOK=1 option, but it was of no help.
The error message also points to look at amqicsdn.txt, but what specifically to look for.
Can someone suggest any solution.  |
|
| Back to top |
|
 |
| dgolding |
| Posted: Wed May 30, 2007 4:30 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
- Look for "**Target file is in use" in the log file.
- Use the process explorer from www.sysinternals.com to find out what is using the DLLs.
- Put the MQSeries service on manual startup and reboot, then try the reinstallation again |
|
| Back to top |
|
|
| saurabh25281 |
| Posted: Wed May 30, 2007 7:55 am Post subject: |
|
|
Centurion
Joined: 05 Nov 2006
Posts: 108
Location: Bangalore
|
Sorry i forgot to mention, the installation i was trying out was on a MSCS Cluster. Does anything change for this.
As suggested i set the MQ services to manual and restarted the server, but still got the same error. On using the processexplorer it shows the following DLLs in use
amqmclrn.dll ResrcMon.exe
amqxcsn.dll ResrcMon.exe, procexp.exe, [System Process]
amqxcs2.dll ResrcMon.exe, procexp.exe, [System Process]
The procexp.exe being the processexplorer tool itself. I guess the only process holding the DLLs up is ResrcMon.exe.
What should we do next?
Thanks in Advance |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 30, 2007 8:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| saurabh25281 |
| Posted: Wed May 30, 2007 8:53 am Post subject: |
|
|
Centurion
Joined: 05 Nov 2006
Posts: 108
Location: Bangalore
|
After going through the link, there is only two ways which i havn't tried out yet
1. Stop the windows intrumentation management services
2. Stop the process which holds up the DLL i.e ResrcMon.exe manually from the Task Manager.
Let me try it out. |
|
| Back to top |
|
|
| saurabh25281 |
| Posted: Wed May 30, 2007 9:16 am Post subject: |
|
|
Centurion
Joined: 05 Nov 2006
Posts: 108
Location: Bangalore
|
Hi All,
I have tried the last 2 options as well, but with no results.
1. Even stopping the windows instrumentation management services didn't work.
2. Killing the process ResrcMon.exe would move the Cluster Group which contains the Shared Drive to the other node in the Cluster. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 30, 2007 9:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So you're only now deciding to mention that you're running the machine under MSCS clustering?
Remove the node from the cluster.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed May 30, 2007 5:44 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I don't think you need to be as drastic as removing the node from the cluster.
Fail the QM and its group over to Node B.
On Node A, make sure MQServices is stopped. Hide the little MQ system tray icon if its still there. Make sure there are no more amq* or runmq* processes left in task manager.
In this link I list some executables that commonly give MQ upgrades a problem:
http://www.mqseries.net/phpBB2/viewtopic.php?t=11426&highlight=files+csd
Try stopping them if it complains, If still a problem, with the QM on Node B and MQ set to Manual on Node A, reboot Node A and try again.
Although that MQPINUSEOK switch in 6.0 has proven to get around all problems for me anyway.
I would upgrade to 6.0.2.1, not 6.0.2.0.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| saurabh25281 |
| Posted: Thu May 31, 2007 4:03 am Post subject: |
|
|
Centurion
Joined: 05 Nov 2006
Posts: 108
Location: Bangalore
|
Here is the response that i got from IBM Global support after sending them the amqicsdn.txt file generated after the installation failure.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
It is showing that there a number of files on the system which are newer
than those being installed. Can you try renaming the following files :
M:\MQData\conv\table\amqver.dll
M:\MQData\conv\table\amqverc.dll
M:\MQData\exits\amqrspin.dll
The following technote gives a bit more information about this error :
http://www-1.ibm.com/support/docview.wss?rs=171&context=SSFKSJ&context=SSWHKB&q1=AMQ4760&uid=swg21177491&loc=en_US&cs=utf-8&lang=en
It is showing that there a number of files on the system which are newer
than those being installed. Can you try renaming the following files :
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I renamed the above DLLs and it worked fine after that.
Thanks for all your help |
|
| Back to top |
|
|
| kababoom |
| Posted: Mon Aug 27, 2007 6:40 pm Post subject: |
|
|
Newbie
Joined: 26 Aug 2007
Posts: 4
|
| saurabh25281 wrote: |
Here is the response that i got from IBM Global support after sending them the amqicsdn.txt file generated after the installation failure.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
It is showing that there a number of files on the system which are newer
than those being installed. Can you try renaming the following files :
M:\MQData\conv\table\amqver.dll
M:\MQData\conv\table\amqverc.dll
M:\MQData\exits\amqrspin.dll
The following technote gives a bit more information about this error :
http://www-1.ibm.com/support/docview.wss?rs=171&context=SSFKSJ&context=SSWHKB&q1=AMQ4760&uid=swg21177491&loc=en_US&cs=utf-8&lang=en
It is showing that there a number of files on the system which are newer
than those being installed. Can you try renaming the following files :
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I renamed the above DLLs and it worked fine after that.
Thanks for all your help |
But will there be any implication if the patches are applied in windows safe mode as this would likely remove any file sharing issues as mentioned above |
|
| Back to top |
|
|
| UglyAngelX |
| Posted: Tue Aug 28, 2007 3:37 am Post subject: |
|
|
Voyager
Joined: 04 Dec 2001
Posts: 90
Location: BEARS FAN IN STEELER COUNTRY
|
For future reference, here is something I got from IBM a few weeks back. We followed these instructions as well as our normal routine of setting MQ to manual and rebooting.
Below are instructions for migrating qmgrs under MSCS from 5.3 to 6.0:
-------------------------------------------------------------------------
This document gives a broader view of the steps required for migrating WebSphere MQ from version 5.3 to version 6.* where the existing installation is in an MSCS environment which needs to be preserved with the migration.
Assumptions: The MSCS set up consist of two nodes Node1 running qmgr QM1 and Node2 running qmgr QM2 as in Active/Active configuration. Existing WebSphere MQ 5.3 installation is at the latest available maintenance level and the migration is to version 6.0 followed by the required level of maintenance update. If the configuration is Active/Passive, then you will have the same qmgr on both the nodes which makes it 1 qmgr less to move back and forth. In such a situation, the same procedure below applies if you remove all references to qmgr QM2
1. Using Cluster Administrator, initiate the failover of qmgr QM1 from Node1 to Node2
2. Stop MQ on Node1
Stop the WebSphere MQ service using the command net stop "IBM MQSeries Services"
Stop the cluster service using the command net stop clussvc
Check and ensure that no MQ processes are running
3. Upgrade WebSphere MQ on Node1
Upgrade existing MQ 5.3 installation to MQ V6 base version
Bring down MQ Series Service and ensure that no MQ processes are running
Apply the required MQ V6 maintenance level (eg: 6.0.2.0)
Restart the Cluster Service and MQSeries Service
Ensure that WebSphereMQ Explorer is not running
4. Fail qmgrs QM1 and QM2 over to the upgraded Node1. The qmgrs will be automatically migrated during this failover.
5. Stop MQ on Node2 by following the steps under point # 2 above
6. Upgrade WebSphere MQ on Node 2 by following the steps under Point #3 above
7. After upgrade, failover both qmgrs over to the upgraded Node 2 and ensure that both the qmgrs run on the upgraded Node2
8. Fail QM1 back from Node2 to Node1, where it was originally running before upgrade
This should bring back the original MSCS setup at the upgraded MQ level.
-------------------------------------------------------------------------------- |
|
| Back to top |
|
|
|
|
