Problems installing 2005 SP3 on Active-Active cluster

Last Post 17 Jul 2009 09:53 AM by mattfinner. 1 Replies.
AddThis - Bookmarking and Sharing Button
Author Messages
mattfinner
New Member
New Member

--
17 Jul 2009 05:01 AM
Hi,

Attempted to install SP3 on our cluster last night, and had a few problems. Any help/suggestions greatly appreciated...

Our cluster has two-nodes (widows 2003 SP2 64 bit), running one instance per node (SQL 2005 Enterprise SP2), in an active-active configuration.

I moved both instances (PROD01 and PROD02) onto a single node (called SRCSILVER) and installed SP3. The installer correctly picked up both instances, updated them, and updated the other components (Integration Services etc).

I then installed SP3 on the other node (called SRCGOLD), which successfully updated non-database engine components (Integration services etc). I then rebooted SRCGOLD and when it came back online, I moved the resources over to SRCGOLD (both instances and cluster group). I then rebooted SRCSILVER. When SRCSILVER came back online, I moved the cluster group and PROD02 back onto it.

When I came to check the versions PROD01 (on SRCGOLD) was showing 9.0.3042 (SP2) and PROD02 (on SRCSILVER) was showing 9.0.4035 (SP3). I then moved PROD01 back onto SRCSILVER, to see if I could, and it showed version 9.0.4035.

As a next step I thought i’d try to run SP3 on SRCGOLD, with both instances running on that node. When I did, the setup failed on the database engine components. Here is the relevant snippet from the hotfix log.

Attempting to pause the 32 bit ngen queue
07/16/2009 20:05:06.034 Attempting to pause the 64 bit ngen queue
07/16/2009 20:05:06.345 Installing product: SQL9
07/16/2009 20:05:06.345 Installing instance: MSSQLSERVER
07/16/2009 20:05:06.345 Enumerating passive cluster nodes
07/16/2009 20:05:06.363 Patching available passive node: SRCSILVER
07/16/2009 20:05:06.363 Waiting for first completed passive node
07/16/2009 20:05:06.363 Patching passive node: SRCSILVER
07/16/2009 20:05:06.655 Task Scheduler: Created remote folder for product instance target \\SRCSILVER
07/16/2009 20:05:14.632 Task Scheduler: Transferred payload to remote product instance target \\SRCSILVER
07/16/2009 20:05:14.632 Task Scheduler: Transferred payload to remote product instance target \\SRCSILVER
07/16/2009 20:05:14.668 Task Scheduler: Created new scheduled task for product instance target \\SRCSILVER
07/16/2009 20:05:14.668 Task Scheduler: SaveTaskToDisk(): Got task interface
07/16/2009 20:05:14.705 Task Scheduler: Saved new scheduled task for product instance target \\SRCSILVER
07/16/2009 20:05:14.705 Task Scheduler: Created scheduled task for product instance target \\SRCSILVER
07/16/2009 20:05:14.705 Task Scheduler: Started scheduled task for product instance target \\SRCSILVER
07/16/2009 20:05:14.705 Task Scheduler: Started scheduled task for product instance target \\SRCSILVER
07/16/2009 20:05:18.209 Task Scheduler: Scheduled task for product instance target has completed
07/16/2009 20:05:18.209 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\SRCSILVER
07/16/2009 20:05:24.050 Task Scheduler: Received exit code 11006 from scheduled task for product instance target \\SRCSILVER
07/16/2009 20:05:24.050 Task Scheduler: Result code for scheduled task for product instance target has been received
07/16/2009 20:05:24.050 Task Scheduler: Removed scheduled task for product instance target \\SRCSILVER
07/16/2009 20:05:24.178 Task Scheduler: Removed remote folder for product instance target \\SRCSILVER
07/16/2009 20:05:24.178 Remote process completed for product instance target
07/16/2009 20:05:24.178 Exit code for passive node: SRCSILVER = 11006
07/16/2009 20:05:29.727 The following exception occurred: No passive nodes were successfully patched Date: 07/16/2009 20:05:29.727 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\instance.cpp Line: 3510
07/16/2009 20:05:30.110 Watson: Param1 = Unknown
07/16/2009 20:05:30.110 Watson: Param2 = 0x2b01
07/16/20
mattfinner
New Member
New Member

--
17 Jul 2009 09:53 AM
Thanks for the reply

Yeah - tried just PROD01 on GOLD.

Though I think you might be right in making sure that SP3 only see's GOLD. Found this ...

http://www.mssqltips.com/tip.asp?tip=1668

... suggests temporarily limiting possible owners (to GOLD). Will post results :-)


Acceptable Use Policy
---