Which statement is true about using OPatch to patch Oracle Grid Infrastructure 12c?
A.
All grid infrastructure patches may be applied in a rolling fashion with Opatch.
B.
Opatch can patch all cluster nodes simultaneously without stopping the clusterware on all nodes.
C.
Opatch can patch all cluster nodes simultaneously only for nonrolling patches.
D.
Applying patches with Opatch must be done in an out-of-place fashion.
Explanation:
As with standard upgrades to Oracle Grid Infrastructure, at any given point in time for normal operation of the cluster, all the nodes in the cluster must have the
same software release and patch level. Because one-off patches can be applied as rolling upgrades, all possible patch levels on a particular software release are
compatible with each other.
Note: Starting with Oracle Grid Infrastructure 12c Release 1 (12.1), a new cluster state called “Rolling Patch” is available. This mode is similar to the existing
“Rolling Upgrade” mode in terms of the Oracle ASM operations allowed in this quiesce state.
https://docs.oracle.com/database/121/CWLIN/procstop.htm#CWLIN528
Real Application Clusters can be patched in three different ways:
1- All Node Patching:In All Node Patching, all Oracle RAC nodes are initially brought down and the patch is applied on all the nodes, then all the nodes are brought back up
2- Rolling Patching:In Rolling Patching, each node is shut down, the patch is applied, then each node is brought back up again. This is done node by node separately until all nodes in Oracle RAC are patched. This is the most efficient mode of applying an interim patch to an Oracle RAC setup because this results in no downtime.
Only some patches can be applied in this mode. The type is generally specified in the patch metadata.
3- Minimum Downtime Patching:In Minimum Downtime Patching, the nodes are divided into sets. Initially, the first set is shut down and the patch is applied to it. After this, the second set is shut down. The first set is brought up and patch is applied to the second set. The second set is also brought up now.
A wrong because Only some (not all GI patches) patches can be applied in this mode rolling fashion. The type is generally specified in the patch metadata.
I think D the correct answer
I think that is “B”.
Patching Oracle RAC can be completed without taking the entire cluster down. In many
cases, patching can be performed with zero down time. This also allows for out-of-place
upgrades to the cluster software and Oracle Database, reducing the planned maintenance
down time required in an Oracle RAC environment.
OPatch can now apply patches in multinode, multipatch fashion. OPatch will not start up
instances that have a nonrolling patch applied to it if other instances of the database do not
have that patch. OPatch also detects whether the database schema is at an earlier patch
level than the new patch, and it runs SQL commands to bring the schema up to the new patch
level.
You can use srvctl to shut down the Oracle software running within an Oracle home, in
preparation for patching. Oracle Grid Infrastructure patching is automated across all nodes,
and patches can be applied in a multinode, multipatch fashion.
Patch sets are now installed as out-of-place upgrades to the Grid Infrastructure software
(Oracle Clusterware and Automatic Storage Management) and Oracle Database. This
reduces the down time required for planned outages for patching.
The correct answer by elimination is C. Check https://docs.oracle.com/database/121/TDPRC/softpatch2.htm#TDPRC603
A is wrong –
While most patches can be applied in a rolling fashion, some patches cannot be applied in this fashion. The README file for the patch indicates whether you can apply the patch using the rolling patch method. If the patch cannot be applied using the rolling patch method, then you must use either “Minimum Downtime Patching” or “All Node Patching” to apply the patch.
B is wrong –
Before you install a patch, you must stop all the applications running from the software directory that is being patched. In a cluster, you may have to shut down additional applications, depending upon which software is being patched. The following table lists the applications to stop when patching Oracle software.
D is wrong –
For standalone (single-instance) database targets, Oracle RAC database targets, Oracle Data Guard targets, and Oracle Grid Infrastructure targets (that may or may not be a part of Oracle Exadata), you can choose between out-of-place patching and in-place patching. For Oracle RAC database targets and Oracle Grid Infrastructure targets, you can choose to apply the patches in rolling or parallel mode in order to control the downtime of the system. https://docs.oracle.com/cd/E24628_01/em.121/e27046/pat_mosem_new.htm#EMLCM11472
C is correct
If you want to patch all the nodes of the target simultaneously, select Parallel. It involves downtime, as your entire system is shut down for a significant period. However, this process consumes less time, as all the target nodes are patched simultaneously. https://docs.oracle.com/cd/E24628_01/em.121/e27046/pat_mosem_new.htm#EMLCM11472
A is only the correct answer.
C is wrong – you can choose to apply the patches in rolling or parallel mode in order to control the downtime of the system.
D – wrong
B – would be right without the word simultaneously
so I’d go for A although it doesn’t seem clear. On one hand the documentation says
Oracle supports the application of patches to the nodes of a Real Application Cluster (RAC) system in a rolling fashion, maintaining the database available throughout the patching process. To perform the rolling upgrade, one of the instances is quiesced and patched while the other instance(s) in the server pool continue in service. This
process repeats until all instances are patched. The rolling upgrade method can be used for Patch Set Updates(PSUs), Critical Patch Updates (CPUs), one-off database and diagnostic patches using OPATCH, operating system upgrades, and hardware upgrade.
but then
When performing patching in Rolling mode, the ORACLE_HOME processes on a particular node are shut down, the patch is applied, then the node is brought back up again. This process is repeated for each node in the GI or RAC environment until all nodes are patched. This is the most efficient mode of applying an interim patch to an Oracle RAC setup because this results in no downtime. NOT ALL patches can be applied using Rolling mode
I think Nelz is right. I pick C.
Correct answer A
B is wrong
Opatch can not patch all cluster nodes simultaneously without stopping the clusterware on all nodes.
C is wrong
There are no such term as nonrolling patches.
D is wrong
Opatch will never use out-of-place fashion
Concepts of Multi-Node Patch Orchestration Using OPatchAuto:
OPatchAuto supports two modes of patching a GI or RAC Home – Rolling and Non-rolling.
even patch in non-rolling fashion, it is still patched one-by-one, and not all at the same time.
Agree A