To ensure a successful non-rolling patch, follow this rigorous checklist:
In rolling mode, opatchauto patches each node in a cluster one at a time while the other nodes remain online. This preserves full availability but takes longer and requires careful state management. opatchauto72030 execute in nonrolling mode high quality
In non-rolling mode:
Best suited for: Single-instance databases, 2-node clusters during maintenance windows, or any environment where downtime is already scheduled. To ensure a successful non-rolling patch, follow this
opatchauto typically runs datapatch automatically for database homes, but it is best practice to verify manually or run it if there are multiple databases. Best suited for : Single-instance databases, 2-node clusters
# Connect to the database
sqlplus / as sysdba
-- Check current state
select patch_id, action, status, action_time from dba_registry_sqlpatch order by action_time;
-- If status is not 'SUCCESS', run manually:
cd $ORACLE_HOME/OPatch
./datapatch -verbose
# For Oracle Grid Infrastructure home (RAC or standalone)
$ORACLE_HOME/OPatch/opatchauto apply <patch_location> -nonrolling
cd /softwares
unzip p36182763_190000_Linux-x86-64.zip
cd 36182763