| Author |
Message
|
| STFO |
 Posted: Wed Nov 30, 2005 7:04 am Post subject: Installing MQ refresh pack 6.0.1.0 on Windows cluster |
 |
|
Newbie
Joined: 08 Aug 2002
Posts: 3
|
I'm attempting to install WebSphere MQ refresh pack 6.0.1.0 on a Windows 2003 active\passive cluster. Node 1 is the active node and Node 2 is the passive node. Here's the steps I'm taking:
1. Move all the active MQ cluster resources to Node 1 of the cluster and verify MQ is working.
2. Log into Node 2 and verify MQ is not active. I do this by right clicking the MQ icon on the task bar and click exit. I then verify that the IBM MQSeries service is not running. I check the task manager and verify there are no amq*.* processes active.
3. I begin the install of the CSD. When I click "Install" the installation comes back and says it is waiting for MQ to stop, even though I verified nothing was running. Eventually I get the message "IBM Websphere MQ files are in use. Stop activity and retry".
I used SysInternal's filemon utility to identify what might be causing the problem and it reported that the amqisdn.exe process has a sharing violation accessing amqxcs2.dll. This process is spawned when I click the install button and I get a dialog saying "waiting for MQ to stop". After I get the message that the files are in use and click the cancel button the amqisdn.exe process terminates. It looks to me like the installation program itself is locking the file and causing the installation to fail.
Anyone have any ideas on this? Anyone have any recommendations on how to apply maintenance on MQ running on a Windows cluster without causing an interruption in service? Thanks in advance for any input. |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Nov 30, 2005 7:35 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
|
| Back to top |
|
|
| STFO |
| Posted: Wed Nov 30, 2005 7:44 am Post subject: |
|
|
Newbie
Joined: 08 Aug 2002
Posts: 3
|
| Turns out it was ResrcMon.exe causing a conflict. Stopping the Cluster service on the inactive node eliminated the conflict and allowed the CSD to be installed. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Nov 30, 2005 7:51 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| STFO wrote: |
| Turns out it was ResrcMon.exe causing a conflict. Stopping the Cluster service on the inactive node eliminated the conflict and allowed the CSD to be installed. |
How did you detemine that? Did you use ProcExp or something else? That info might be useful for others.... 
_________________
-wayne |
|
| Back to top |
|
|
| STFO |
| Posted: Wed Nov 30, 2005 7:55 am Post subject: |
|
|
Newbie
Joined: 08 Aug 2002
Posts: 3
|
| Process Explorer did the trick. During the last part of the installation I got a dialog box that had a red X in it and an OK button. There was no text. This dialog box popped up twice during the installation, but the install says it finished successfully. I duplicated this behavior on a single node server running MQ v6 and Windows 2003. Anyone seen this before? |
|
| Back to top |
|
|
| msantos007 |
| Posted: Mon Jan 30, 2006 9:13 am Post subject: |
|
|
Voyager
Joined: 20 Dec 2004
Posts: 78
|
first... when you work with MQ in a MSCS, you cannot simply move the cluster to one node and update the inactive node... you'll always have to update the active node. why? because the data files and log files of the queue manager are in the cluster shared disk.
second point: never... stop the queue manager using MQExplorer ou endmqm, you'll have to deactivate the queue manager using the Cluster Administrator.
and finally... NEVER stop the Cluster Service.. this will cause a "move group" and you'll not be able to update the files
_________________
Maximiliano R. A. Santos
IBM Websphere MQ V6.0 Certified System Administrator
IBM Websphere MQ V5.3 Certified Solution Developer |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jan 30, 2006 9:23 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| msantos007 wrote: |
first... when you work with MQ in a MSCS, you cannot simply move the cluster to one node and update the inactive node... you'll always have to update the active node. why? because the data files and log files of the queue manager are in the cluster shared disk.
|
Not true.
IBM on its website even recommends upgrading the passive node, moving the QM over, and upgrading the other node, to minimize downtime.
Applying CSDs like this is no prob. Apparently a CSD does not muck with the data files that are on the share.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| msantos007 |
| Posted: Mon Jan 30, 2006 9:35 am Post subject: |
|
|
Voyager
Joined: 20 Dec 2004
Posts: 78
|
peter,
I guess if it's not true... why do we move the data and log files to the shared disk? if they don't need to be updated.
_________________
Maximiliano R. A. Santos
IBM Websphere MQ V6.0 Certified System Administrator
IBM Websphere MQ V5.3 Certified Solution Developer |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jan 30, 2006 9:39 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
they are on the share disk so they can be, shared, between Node1 and Node2.
The executable files don't change constantly, so they are installed locally on both nodes.
But the data files are in a constant state of change, so they are out on the share drive where the active node can get at them ASAP, whichever node happens to be active.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| msantos007 |
| Posted: Mon Jan 30, 2006 9:41 am Post subject: |
|
|
Voyager
Joined: 20 Dec 2004
Posts: 78
|
I mean... think that you're not using a cluster
then you'll update the WMQ instalation. What happens if you simply
open one of those files in exclusive mode, with any application.
you already stopped everything. but "MQ Files are still in use".
_________________
Maximiliano R. A. Santos
IBM Websphere MQ V6.0 Certified System Administrator
IBM Websphere MQ V5.3 Certified Solution Developer |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jan 30, 2006 9:45 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If Node1 is active, it has the running QM, as well as the shared drive, that has all the q and log files. You can't / shouldn't touch that node. Go apply the CSD to Node2. At this point Node2 only has the executable files on the local drive, and none of them are being used, because the QM is running on the other node. So its safe to upgrade Node2. Once complete, swing the QM over to Node2, and then upgrade Node1, which now has no files in use.
Apparently the CSD is not looking for any of the files on the share drive. It only wants to upgrade the executables on the local drive.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| msantos007 |
| Posted: Mon Jan 30, 2006 9:48 am Post subject: |
|
|
Voyager
Joined: 20 Dec 2004
Posts: 78
|
Well I'll believe in you... but I still prefer to update the local service, because of those arguments a said.. and because MS Cluster Service will be using the cluster resource DLL, on both nodes.
_________________
Maximiliano R. A. Santos
IBM Websphere MQ V6.0 Certified System Administrator
IBM Websphere MQ V5.3 Certified Solution Developer |
|
| Back to top |
|
|
|
|
