oracle叢集patching

$ORACLE_HOME/oui/bin/ -updateNodeList ORACLE_ HOME=
"CLUSTER_NODES={node1,node2,node3}"
-noClusterEnabled
-local

If you want to specify the local node or remote nodes of an Oracle Real Application Clusters setup to OPatch, you can use the LOCAL_NODE or REMOTE_NODESsession variable and specify the node name(s), as shown below:

$ORACLE_HOME/oui/bin/ ORACLE_HOME=
"REMOTE_NODES={node1,node2,node3}"  LOCAL_NODE=<nodelist If OPatch does not automatically detect Oracle Real Application Clusters or its nodes, you need to investigate the contents of the inventory and ensure that it is complete. You can patch Oracle Real Application Clusters in three different ways: 

• All Node Patching

• Rolling Patching

• Minimum Downtime Patching

The following sections provide detailed information for these types of Oracle Real Application Clusters patching.

All Node Patching

Figure 7–1 shows a basic example of All Node Patching. Figure 7-1 All Node Patching

Systems A, B, and C are nodes in this cluster. When you perform All Node Patching in this cluster, you bring down systems A, B, and C, apply patches to all these nodes, then bring systems A, B, and C back up again.

Rolling Patching

In Rolling Patching, you shut down each node, apply the patch, then bring up each node again. You do this separately for each node until you patch all nodes in the cluster. This is the most efficient method of applying an interim patch to an Oracle Real Application Clusters setup, because there is absolutely no downtime during the application of patches, as only one system is brought down at any given time. Only some patches can be applied in this mode. The type is generally specified in the patch metadata.

Figure 7–2 shows a basic example of Rolling Patching.

Figure 7-2 Rolling Patching

When you perform Rolling Patching in this cluster, the patches are applied in a rolling fashion. You initially bring down system A, apply a patch to it, then bring it back up. You do the same thing for systems B and C.

Minimum Downtime Patching

In Minimum Downtime Patching, the nodes are divided into sets. Initially, you shut down the first set and apply a patch to it. After this, you shut down the second set. You then bring up the first set and apply a patch to the second set. You now bring up the second set. All the nodes in the cluster are now patched. This method leads to less downtime for Oracle Real Application Clusters when both sets are brought down. This mode is executed by using -minimize_downtimecommand line option. You can also activate this option from the response file. In Minimum Downtime Patching, the nodes are divided into sets. Initially, you shut down the first set and apply a patch to it. After this, you shut down the second set. You then bring up the first set and apply a patch to the second set. You now bring up the second set. All the nodes in the cluster are now patched. This method leads to less downtime for Oracle Real Application Clusters when both sets are brought down. This mode is executed by using -minimize_downtimecommand line option. You can also activate this option from the response file. Figure 7–3 shows a basic example of Minimum Downtime Patching. Figure 7-3 Minimum Downtime Patching Systems A, B, and C are nodes in this cluster. It is divided into two sets: Set 1 contains systems A and B, and Set 2 contains system C. When you perform Minimum Downtime Patching in this cluster, you shut down Set 1 and apply a patch to it. You now shut down Set 2. Then, you bring up Set 1 and apply a patch to Set 2. After you apply the patch, you bring up Set 2 again. Now both Sets 1 and 2 are patched. PS:其實跟單節點都是一樣的，唯一的不同是全關還是留一個例項的問題。