Oracle January Patch 19 2023
Oracle Critical Patch Update on 19c - January 2023
Oracle Critical Patch Update (CPU)
Patch 34773504 - Combo of OJVM Component Release Update 19.18.0.0.230117 + Grid Infrastructure Jan 2023 Release Update 19.18.0.0.230117
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
Patch 34762026 - GI Release Update 19.18.0.0.230117 (REL-JAN230131)
1)
NOTE: IMPORTANT
GI Home:
You need to update first opatch to the higer or letest version.
You can download letest version from the following link.
For JAN CPU use latest OPatch Version "OPatch 12.2.0.1.36 for DB 19.0.0.0.0 (Jan 2023)".
Download Latest OPatch from "Download Latest OPatch"
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.
p34762026_190000_Linux-x86-64.zip
Check the conflict:
From Grid_Home
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/34762026/34765931
Oracle Interim Patch Installer version 12.2.0.1.29
Copyright (c) 2020, Oracle Corporation. All rights reserved.
PREREQ session
Oracle Home : /u02/oracle/app/home/product/19.0.0/grid_19
Central Inventory :$ORACLE_BASE/app/oraInventory
from :$GRID_HOME/oraInst.loc
OPatch version : 12.2.0.1.29
OUI version : 12.2.0.1.4
Log file location : $GRID_HOME/cfgtoollogs//opatch/opatchxxxx
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
OPatch succeeded.
Copyright (c) 2020, Oracle Corporation. All rights reserved.
PREREQ session
Oracle Home : /u02/oracle/app/home/product/19.0.0/grid_19
Central Inventory :$ORACLE_BASE/app/oraInventory
from :$GRID_HOME/oraInst.loc
OPatch version : 12.2.0.1.29
OUI version : 12.2.0.1.4
Log file location : $GRID_HOME/cfgtoollogs//opatch/opatchxxxx
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
OPatch succeeded.
I am not going to add output of all commands. The output should looks like as above.
$DOWNLOAD_PATCH is a directory where the patch is located.
$DOWNLOAD_PATCH is a directory where the patch is located.
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/34762026/34768559
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/34762026/34768569
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/34762026/34768569
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/34762026/34863894
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/34762026/33575402
For Database home, as home user
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/34762026/34765931
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/34762026/34768559
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir $DOWNLOAD_PATCH/34762026/34768559
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>/34762026 - oh <GI_HOME>
ii) To patch oracle_home
opatchauto apply <UNZIPPED_PATCH_LOCATION>/34762026 -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>/34762026
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/34762026
$GRID_HOME/OPatch/opatchauto apply $DOWNLOAD_PATCH/34762026
Post-Installation Instructions
For the both Single/Multitenant (CDB/PDB) DB required following steps.
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 34786990 - Oracle JavaVM Component Release Update 19.18.0.0.230117
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/34786990
Post installation Steps.
startup
alter pluggable database all open;
exit
cd $ORACLE_HOME/OPatch
./datapatch -verbose
sqlplus / as sysdba
cd $ORACLE_HOME/rdbms/admin
SQL> @utlrp.sql
$ORACLE_HOME/OPatch/opatch lspatches |sort
==== 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.