Oracle Critical Patch Update on 19c - April 2026
GI RU Combo:
Patch 39062956 - Combo of OJVM Component Release Update 19.31.0.0.260421 + Grid Infrastructure Apr 2026 Release Update 19.31.0.0.260421 (REL-APR2026)
PURPOSE: All documents are provided on this Blog just for educational purposes only. Please make sure that you run it in your test environment before to move on to production environment.
Execute the following commands:
STEP 1
GI RELEASE UPDATE 19.31.0.0.0 (REL-APR2026)
1)
NOTE:
GI Home:
You need to update first opatch to the higher or latest version.
You can download latest version from the following link.
For April CPU is required OPatch latest version. It can be downloaded by the following link
Download lest OPatch from "https://updates.oracle.com/download/6880880.html"
Latest OPatch copy files.
Grid_home
Als root user:
cd /oracle19/gridbase/grid
unalias mv
cd /oracle19/gridbase/grid
mv OPatch OPatch_OLD
cd $DOWNLOAD_HOME/OPatch_12.2.0.1.51
cp -r OPatch /oracle19/gridbase/grid
cd /oracle19/gridbase/grid
chown -R oracle:dba OPatch/
su - oracle
. set_home_env +ASM
$ORACLE_HOME/OPatch/opatch version
You Need to do the same on ORACLE_HOME
Oracle ORACLE_HOME
Latest OPatch copy files
Oracle_home:
Als root user:
cd /oracle19/support/download/OPatch_12.2.0.1.51
cd /oracle19/dbbase/db
unalias mv
mv OPatch OPatch_OLD
cd /oracle19/support/download/OPatch_12.2.0.1.51
cp -r OPatch /oracle19/dbbase/db
cd /oracle19/dbbase/db
chown -R oracle:dba OPatch
su - oracle
. set_home_env ${ORACLE_SID}
$ORACLE_HOME/OPatch/opatch version
Unzip April 2026 combo patch file downloaded.
p39062956_190000_Linux-x86-64.zip
Check the conflict:
From Grid_Home
$DOWNLOAD_PATCH is a directory where the patch is located.
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/39062956/39036936/39034528
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/39062956/39036936/39039430
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/39062956/39036936/39055473
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/39062956/39036936/39107855
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -
phBaseDir $DOWNLOAD_PATCH/39062956/39036936/39107825
For Database home, as home user
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/39062956/39036936/39034528
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/39062956/39036936/39039430
2)
Shut down all instances and listeners associated with the Oracle home that you are updating.
NOTE:
If you have standby DB. Stop them first and keep it for fallback:
On Standby:
select name, open_mode, database_role from v$database;
select process, status, sequence# from v$managed_standby;
alter database recover managed standby database cancel;
On Primary:
show parameter log_archive_dest_state_2;
alter system set log_archive_dest_state_2=DEFER SCOPE=BOTH;
On Standby:
shutdown immediate;
srvctl stop asm -f
On Primary:
STOP DB and PDB from Oracle home:
alter pluggable database KARDBPDB close immediate;
srvctl stop database -d KARDBTST
srvctl status database -d KARDBTST
Database is not running.
Stop Listener from GI Home
srvctl stop listener -l LISTENER
srvctl status listener -l LISTENER
Listener LISTENER is enabled
Listener LISTENER is not running
Stop ASM
3)
As root user execute the following command.
You have following options
i) To patch only the GI Home
<GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/patchid - oh <GI_HOME>
ii) To patch oracle_home
opatchauto apply <UNZIPPED_PATCH_LOCATION>/patchid -oh <oracle_home1_path>
iii) Patching Oracle Home and Grid Home togather:
As root user, execute the following command on each node of the cluster:
# <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/patchid
I am going to apply the path for both grid home and oracle home together.
Oracle Document:
https://updates.oracle.com/Orion/Services/download?type=readme&aru=28686071
NOTE: make sure that the Clusterware has is running:
As root user:
cd /users/oracle
. set_home_env +ASM
export PATH=$PATH:$GRID_HOME/OPatch
$GRID_HOME/OPatch/opatchauto apply $DOWNLOAD_PATCH/39062956/39036936
$GRID_HOME/OPatch/opatchauto apply $DOWNLOAD_PATCH/39062956/39036936
As Grid_Home:
crsctl start res -all
or
srvctl start asm
srvctl start database -db ${ORACLE_SID}
Post-Installation Instructions
Single/Multitenant (CDB/PDB) DB
sqlplus / as sysdba
startup
alter pluggable database all open;
quit
cd $ORACLE_HOME/OPatch
./datapatch -verbose
Any databases that have invalid objects need to execute utlrp.sql run
For example:
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
-- You can check valid or invalid objects with the following command.
set pagesize 250;
col STATUS format a20;
col COMP_NAME format a35;
select COMP_NAME, version, status from dba_registry;
STEP 2
OJVM RELEASE UPDATE 19.31.0.0.0
For a Non Oracle RAC environment, shut down all databases and listeners associated with the Oracle home that you are updating.
From Oracle_home.
Stop DB - no need to stop ASM
alter pluggable database KARDBPDB close immediate;
srvctl stop database -d KARDBTST
srvctl stop listener -l LISTENER
export PATH=$PATH:/usr/ccs/bin
#$ORACLE_HOME/OPatch/opatch apply $DOWNLOAD_PATCH/39062956/38906621
Post installation Steps.
startup upgrade
alter pluggable database all open upgrade;
exit
cd $ORACLE_HOME/OPatch
./datapatch -verbose
sqlplus / as sysdba
shutdown
startup
alter pluggable database all open;
SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
NOTE: If need Roolback the patch:
opatch rollback -id 38906621
startup
cd $ORACLE_HOME/OPatch
./datapatch -verbose
## Roolback End --
Verify the patch Version and Status of the patch:
col ID format a5
col COMMENTS format a20
col VERSION format a12
col BUNDLE format a5
col ACTION_TIME format a30
col ACTION format a10
set linesize 150
select substr(action_time,1,30) action_time, substr(id,1,8) id, substr(action,1,10) action, substr(version,1,8) version, substr(comments,1,20) comments from sys.registry$history ;
set pagesize 20;
set linesize 200;
col ACTION_TIME format a30;
col DESCRIPTION format a50;
select PATCH_ID,ACTION,ACTION_TIME,DESCRIPTION,STATUS from registry$sqlpatch order by ACTION_TIME ;
select PATCH_ID,DESCRIPTION,STATUS from registry$sqlpatch order by ACTION_TIME ;
OR
GRID_HOEM:
$ORACLE_HOME/OPatch/opatch lspatches -oh ${ORACLE_HOME}
ORACLE_HOME
$ORACLE_HOME/OPatch/opatch lspatches -oh ${ORACLE_HOME}
Patch Apply on Standby DB - Just in case if you have one:
Aapply a patch you might need to execute ONE or TWO steps
== > Patch Oracle binaries < == On BOTH databases : Primary AND Standby
== > Execute post patching step(s) < == On the Primary ONLY
== > A Physical Standby can NOT be modified DIRECTLY == > Only by applying changes received from the Primary database via redo log files
select name, open_mode, database_role from v$database;
select process, status, sequence# from v$managed_standby;
ALTER DATABASE RECOVER managed standby database cancel;
shutdown immediate;
srvctl stop asm -f
Patch 1: on binary level
root user:
cd /users/oracle
. set_home_env +ASM
export PATH=$PATH:$GRID_HOME/OPatch
$GRID_HOME/OPatch/opatchauto apply $DOWNLOAD_PATCH/39062956/39036936
start asm
startup mount;
Patch 2: on Standby:
Stop DB - no need to stop ASM
remove alert log
From ORACLE_HOME
export PATH=$PATH:/usr/ccs/bin
$ORACLE_HOME/OPatch/opatch apply $DOWNLOAD_PATCH/39062956/38906621
Starting logapply on standby:
alter database recover managed standby database disconnect from session;
On Primary:
alter system set log_archive_dest_state_2='ENABLE' scope=both;
Your comments are most valuable and it would help me to come up with better posts.
No comments:
Post a Comment