When maintaining Oracle Grid Infrastructure (GI) or RAC environments, you may encounter the requirement to use the -nonrolling opatchauto
opatchauto typically runs datapatch automatically for database homes, but it is best practice to verify manually or run it if there are multiple databases.
Look for messages like:
Since does not match a known Oracle patch, verify the patch number :
# As oracle (Grid Infrastructure owner) export ORACLE_HOME=/u01/app/12.2.0.2/grid $ORACLE_HOME/OPatch/opatchauto apply /stage/72030 -nonrolling
The core command to execute opatchauto in non-rolling mode for patch 72030 is:
When maintaining Oracle Grid Infrastructure (GI) or RAC environments, you may encounter the requirement to use the -nonrolling opatchauto
opatchauto typically runs datapatch automatically for database homes, but it is best practice to verify manually or run it if there are multiple databases.
Look for messages like:
Since does not match a known Oracle patch, verify the patch number :
# As oracle (Grid Infrastructure owner) export ORACLE_HOME=/u01/app/12.2.0.2/grid $ORACLE_HOME/OPatch/opatchauto apply /stage/72030 -nonrolling
The core command to execute opatchauto in non-rolling mode for patch 72030 is: