Oracle Critical Patch Update on 19c - January 2025
Oracle Critical Patch Update (CPU)
19.27.0.0.250415 GI RU Combo:
Patch 37591516 - Combo of OJVM Component Release Update 19.27.0.0.250415 + Grid Infrastructure Apr 2025 Release Update 19.27.0.0.25041
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
Oracle® Database Patch 37641958 - GI Release Update 19.27.0.0.250415
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.
cd $GRID_HOME
mv OPatch OPatch_old
cd $DOWNLOAD_PATCH/OPatch
cp -r OPatch $GRID_HOME
You Need to do the same on ORACLE_HOME
Oracle ORACLE_HOME
Latest OPatch copy files
cd $ORACLE_HOME
mv OPatch OPatch_old
cd $DOWNLOAD_HOME/OPatch
cp -r OPatch $ORACLE_HOME
Unzip January patch file downloaded.
unzip p37641958_190000_<platform>.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/37641958/37642901
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/37641958/37654975
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/37641958/37643161
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/37641958/37762426
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -
phBaseDir $DOWNLOAD_PATCH/37641958/36758186
For Database home, as home user
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/37641958/37642901
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/37641958/37654975
2)
Shut down all instances and listeners associated with the Oracle home that you are updating.
Stop a 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
srvctl stop asm -f
srvctl status asm
ASM is not running.
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>/37641958 - oh <GI_HOME>
ii) To patch oracle_home
opatchauto apply <UNZIPPED_PATCH_LOCATION>/37641958 -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>/37641958
I am going to apply the path for both grid home and oracle home together.
NOTE: make sure that the Clusterware is running:
crsctl status has
If it is not running, you need to start it as follow.
crsctl start has
export PATH=$PATH:$GRID_HOME/OPatch
$GRID_HOME/OPatch/opatchauto apply $DOWNLOAD_PATCH/37641958
$GRID_HOME/OPatch/opatchauto apply $DOWNLOAD_PATCH/37641958
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
Patch 37499406 - Oracle JavaVM Component Release Update 19.27.0.0.250415
For a Non Oracle RAC environment, shut down all databases and listeners associated with the Oracle home that you are updating.
From Oracle_home.
Normally no need to stop ASM. You need to just stop the DB and Listener
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/37499406
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;
cd $ORACLE_HOME/rdbms/admin
SQL> @utlrp.sql
==== DONE ====
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 ;
Enjoy !
Your comments are most valuable and it would help me to come up with better posts.
