| Author |
Topic |
|
DBADave
Constraint Violating Yak Guru
366 Posts |
 Posted - 2009-04-19 : 10:33:42
|
| I have an active/passive cluster. We added a new node and thought SP2 would automatically be applied since nodes 1 & 2 already had it. We found that SP2 had to be applied to the new node. Is this normal?SQL 2005 EE SP2 - 64bit / Windows 2003 EE SP2 64-bitThanks, Dave |
|
|
saurabhsrivastava
Posting Yak Master
216 Posts |
Posted - 2009-04-21 : 13:39:00
|
| Yes, you can apply patch on tools and other non-clustered components. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2009-04-21 : 14:39:47
|
| Tara,By reinstall I assume you are referring to Add/Remove programs where the installation of SQL Server is performed against the new node, but performed from the primary node. SQL Server is not being reinstalled on the existing nodes. From what Microsoft explained to me the installation process queries the registries of the existing nodes using the Remote Registry service and builds an XML configuration file. That information is used during the installation on the new node. I only know this because we encountered major installation problems this weekend. The install appeared to work, but SQL Server would not failover. The problem may be due to having a server with 24 processors. There is a KB article about a bug when installing SQL Server 2005 on a server where the number of processors is not a multiple of 2. Despite following the work around we encountered strange behavior. The new node was added with SQL Server expecting the master log file to reside in the default location, despite the existing nodes knowing that the log file existed in a different location. We then encountered a permissions bug where the account used to add the node could not access the data drive where master was located. That account was a domain administrator and was a member of the local administrator's group. The group it belonged to had full access to the DATA folder. The existing nodes used that same account and had no problem accessing the DATA folder. Based upon a similar problem someone reported on an MSDN forum we had to grant the id FULL access, despite the group having the correct permissions. Very strange, but it worked. We then were able to apply SP2 directly to the new node and failover successfully, but later found that the SQL installation caused the new node to revert to Windows Authentication Mode and not mixed mode. The SQL Server Agent history was also lost and various SQL Server Agent setting were reset to the default installation values. Locked Pages in Memory was also not automatically enabled for the service account. It was a bit of a mess that Severity 1 MS support could not explain. Just thought I would share. I hope nobody ever has to experience this.Thanks, Dave |
|
|
|
saurabhsrivastava
Posting Yak Master
216 Posts |
Posted - 2009-04-21 : 15:23:50
|
| Good info. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2009-04-22 : 08:46:53
|
| 22 times. Ouch. Any problems with the installs? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2009-04-22 : 14:08:13
|
| I had to open a Sev 1 call, which was lots of fun. I'm sure the primary engineer tried his best, but there was a lot of guess work being performed after reviewing the logs. We never determined the cause. The TAM tried saying it was a matter of not adding a node with the correct account, but we shot that down because we used the service account which is a domain admin (I know, shame on me for making it domain admin) and a member of the local admin group. Not to mention the existing nodes were setup using that same account and they don't have problems. Very strange. The good news is this opened some eyes to the need for a test SAN. Dave |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2009-04-22 : 17:01:41
|
| We constantly have issues with PSS and need to escalate to a higher engineer. After spinning your wheels without a resolution from MS, I would highly recommend that you request someone higher as the first person you get is typically not very high. We had to do that on Monday. The original engineer stayed on the phone while the higher engineer worked to resolve the issue.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog"Let's begin with the premise that everything you've done up until this point is wrong." |
|
|
|
|
Do I need to apply SP to new node added to cluster