You find SP is not applied to all the nodes across the cluster. How to

1.	You find SP is not applied to all the nodes across the cluster. How to apply SP only on the required nodes?
Answer» If you find that the product level is not consistent across all the nodes, you will need to fool the 2005 patch INSTALLER into only patching the nodes that need updating. To do so, you will have to perform the following STEPS: Fail Instance, Cluster, and MSDTC groups to an UNPATCHED node Remove any SUCCESSFULLY patched nodes from failover candidates of the SQL Server Service of the instance GROUP (do this using Cluster Admin tool) Run the patch After the patch installs successfully, add the Nodes removed in Step 2 back to the SQL Server Service of the Instance group Why do you need to do this? Well when the patch installer determines that not all nodes in the cluster are at the same patch level, a passive node operation will fail and will prevent you from moving forward with any further patching.

You find SP is not applied to all the nodes across the cluster. How to apply SP only on the required nodes?

Answer»

If you find that the product level is not consistent across all the nodes, you will need to fool the 2005 patch INSTALLER into only patching the nodes that need updating. To do so, you will have to perform the following STEPS:

Fail Instance, Cluster, and MSDTC groups to an UNPATCHED node
Remove any SUCCESSFULLY patched nodes from failover candidates of the SQL Server Service of the instance GROUP (do this using Cluster Admin tool)
Run the patch
After the patch installs successfully, add the Nodes removed in Step 2 back to the SQL Server Service of the Instance group

Why do you need to do this? Well when the patch installer determines that not all nodes in the cluster are at the same patch level, a passive node operation will fail and will prevent you from moving forward with any further patching.

Discussion

No Comment Found

Related InterviewSolutions

What is .TUF file? What is the significance of the same? Any implications if the file is deleted?
Full backup size is 300 GB, usually my diff backup size varies between 300 MB and 5 GB, unfortunately, one-day diff backup size was increased to 250 GB? What might be the reason any idea?
See I have an environment, Sunday night full backup, everyday night diff backup, and every 45 min a transactional backup. The disaster happened at 2:30 PM on Saturday. You suddenly found that the last Sunday backup has been corrupted. What’s your recovery plan?
I wanted to know what are the maximum worker threads setting and active worker thread count on SQL server. Can you tell me how to capture this info? What’s the default value for the max thread count?
How distributed transactions work in SQL Server?
Can we add an article to the existing publication without generating a snapshot with all articles?
Consider a situation where publisher database log file has been increasing and there is just a few MB available on disk. As an experienced professional how do you react to this situation? Remember no disk space available and also we can’t create a new log file on another drive
When should a developer use the NOLOCK hint? What problems can happen when using this hint and how can these problems be addressed?
What is an optimistic and pessimistic lock in SQL?
What is Lock escalation in SQL

You find SP is not applied to all the nodes across the cluster. How to apply SP only on the required nodes?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment