In this guide, we will install the latest Oracle 19c Update Patches which is the Jan 2022 patches as of this writing.
For the purpose of this guide, note the following:
-To make following this guide easier, put all your zip files in /usr/software/oracle.
-GI stands for Grid Infrastructure, also known as Oracle Restart.
-DB stands for Database.
-DB Home owner is Linux OS user “oracle”.
-DB Home: /oracle/oraBase/oracle/19.0.0/database
-GI Home owner is Linux OS user “grid”.
-GI Home: /oracle/oraBase/19.0.0/grid
-ALWAYS make a backup of the database and the oracle software before you start.
Preparations
Download the following patches from https://support.oracle.com:
OPatch – Download the latest OPatch. We are using OPatch Version 12.2.0.1.28 in this excercise. (Hint: Search for Doc ID 274526.1)
OJVM + GI PSU – includes updates for OJVM/GI/DB. We will be using p33567274_190000_Linux-x86-64.zip. (Hint: Search for Doc ID 2118136.2)
JDK – Download the latest JDK for GI/DB Homes. Jan/2022 Release is p33497160_190000_Linux-x86-64.zip. (Hint: Search for Doc ID 2118136.2)
As oracle user, unzip the OJVM/GI/DB PSU and the JDK Patch.
$ cd /usr/software/oracle
$ unzip -q p33567274_190000_Linux-x86-64.zip
$ unzip -q p33497160_190000_Linux-x86-64.zip
$ ls -ld 33497160
drwxr-xr-x 1 oracle oinstall 58 Dec 22 21:34 33497160 <-- JDK for GI/DB Homes
$ ls -l 33567274
total 32
drwxr-xr-x 1 oracle oinstall 162 Mar 14 14:04 33509923 <-- GI/DB PSU
drwxr-xr-x 1 oracle oinstall 58 Jan 5 08:13 33561310 <-- OJVM PSU
As root, chmod 777 on all the directories and chmod 775 on all files of the extracted patches. Both oracle and grid users need access to them.
# chmod 777 $(find /usr/software/oracle/33567274 -type d)
# chmod og+rw $(find /usr/software/oracle/33567274 -type f)
For this entire excercise, make sure your /tmp is executible. Otherwise, remount it as executible.
# mount|grep "/tmp"
/dev/mapper/rootvg-tmplv on /tmp type ext4 (rw,relatime,data=ordered)
# mount -o remount,exec /tmp
Alternatively, you can also specify it to be elsewhere.
Example of using a non-default temp location for DB Home patching.
# su - oracle
$ export TMP=/home/oracle/tmp
$ export TMPDIR=/home/oracle/tmp
Example of using a non-default temp location for GI Home patching.
# su - grid
$ export TMP=/home/grid/tmp
$ export TMPDIR=/home/grid/tmp
Verify all objects in all containers are valid before patching.
Note: In my database, I have 3 containers: CDB$ROOT (root container), PDB$SEED (seed database), PROD1PDB (my production pluggable database).
# su - oracle
$ sqlplus / as sysdba
SQL> show con_name
CON_NAME
------------------------------
CDB$ROOT
SQL> show pdbs
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 PROD1PDB READ WRITE NO
SQL> select count(*), status from dba_objects group by status;
COUNT(*) STATUS
---------- ---------------------
68061 VALID
SQL> alter session set container=PROD1PDB;
SQL> select count(*), status from dba_objects group by status;
COUNT(*) STATUS
---------- ---------------------
61772 VALID
6120 INVALID
If you have any invalid objects, recompile them.
SQL> @?/rdbms/admin/utlrp.sql
SQL> select count(*), status from dba_objects group by status;
COUNT(*) STATUS
---------- ---------------------
67918 VALID
SQL> alter session set container=PDB$SEED;
Session altered.
SQL> select count(*), status from dba_objects group by status;
COUNT(*) STATUS
---------- ---------------------
67128 VALID
The seed database is read only and should not have any invalid objects. But if it does have invalid objects and needs to be recompiled, we need to make it read-write, recompile the objects in it, then make it read-only again.
SQL> alter session set "_oracle_script" = true;
Session altered.
SQL> alter pluggable database pdb$seed close;
Pluggable database altered.
SQL> alter pluggable database pdb$seed open read write;
Pluggable database altered.
SQL> @?/rdbms/admin/utlrp.sql
SQL> alter pluggable database pdb$seed close;
Pluggable database altered.
SQL> alter pluggable database pdb$seed open read only;
Pluggable database altered.
1. Install the latest OPatch in DB Home.
Log in as the DB Home owner.
# su - oracle
Remove the old OPatch.
$ rm -rf $ORACLE_HOME/OPatch/*
Unzip the OPatch into DB Home.
$ unzip -q -od $ORACLE_HOME /usr/software/oracle/p6880880_210000_Linux-x86-64.zip
Check the OPatch version.
$ $ORACLE_HOME/OPatch/opatch version
OPatch Version: 12.2.0.1.28
OPatch succeeded.
Check current patches in the DB Home.
$ opatch lsinventory|grep -A3 "^Patch.*applied"
Patch 29585399 : applied on Thu Apr 18 00:21:33 PDT 2019
Unique Patch ID: 22840393
Patch description: "OCW RELEASE UPDATE 19.3.0.0.0 (29585399)"
Created on 9 Apr 2019, 19:12:47 hrs PST8PDT
--
Patch 29517242 : applied on Thu Apr 18 00:21:17 PDT 2019
Unique Patch ID: 22862832
Patch description: "Database Release Update : 19.3.0.0.190416 (29517242)"
Created on 17 Apr 2019, 23:27:10 hrs PST8PDT
Check current JDK version in DB Home.
$ $ORACLE_HOME/jdk/bin/java -version
java version "1.8.0_311"
Java(TM) SE Runtime Environment (build 1.8.0_311-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.311-b11, mixed mode)
2. Install the latest OPatch in GI Home.
Log in as the GI Home owner.
# su - grid
Remove the old OPatch.
$ rm -rf $ORACLE_HOME/OPatch/*
Unzip the latest OPatch into GI Home.
$ unzip -q -od $ORACLE_HOME /usr/software/oracle/p6880880_210000_Linux-x86-64.zip
Check the OPatch version.
$ $ORACLE_HOME/OPatch/opatch version
OPatch Version: 12.2.0.1.28
OPatch succeeded.
Check current patches in the GI Home.
$ opatch lsinventory|grep -A3 "^Patch.*applied"
Patch 29585399 : applied on Thu Apr 18 00:36:24 PDT 2019
Unique Patch ID: 22840393
Patch description: "OCW RELEASE UPDATE 19.3.0.0.0 (29585399)"
Created on 9 Apr 2019, 19:12:47 hrs PST8PDT
--
Patch 29517247 : applied on Thu Apr 18 00:36:02 PDT 2019
Unique Patch ID: 22840392
Patch description: "ACFS RELEASE UPDATE 19.3.0.0.0 (29517247)"
Created on 1 Apr 2019, 15:08:20 hrs PST8PDT
--
Patch 29517242 : applied on Thu Apr 18 00:35:39 PDT 2019
Unique Patch ID: 22862832
Patch description: "Database Release Update : 19.3.0.0.190416 (29517242)"
Created on 17 Apr 2019, 23:27:10 hrs PST8PDT
--
Patch 29401763 : applied on Thu Apr 18 00:35:16 PDT 2019
Unique Patch ID: 22759421
Patch description: "TOMCAT RELEASE UPDATE 19.0.0.0.0 (29401763)"
Created on 11 Apr 2019, 22:26:25 hrs PST8PDT
Check current JDK version in GI Home.
$ $ORACLE_HOME/jdk/bin/java -version
java version "1.8.0_311"
Java(TM) SE Runtime Environment (build 1.8.0_311-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.311-b11, mixed mode)
3. Apply the GI/DB (Patch 33509923) patch as root user. This will apply to both GI Home and the DB Home, including applying sql patch to the database.
Verify database is up. As oracle, run:
$ srvctl status database -d PROD
Database is running.
As root, execute:
# export PATH=$PATH:/oracle/oraBase/19.0.0/grid/OPatch
# opatchauto apply /usr/software/oracle/33567274/33509923
OPatchauto session is initiated at Fri Mar 18 14:51:41 2022
System initialization log file is /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2022-03-18_02-51-46PM.log.
Session log file is /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchauto/opatchauto2022-03-18_02-51-51PM.log
The id for this session is 6B75
Executing OPatch prereq operations to verify patch applicability on home /oracle/oraBase/oracle/19.0.0/database
Patch applicability verified successfully on home /oracle/oraBase/oracle/19.0.0/database
Executing patch validation checks on home /oracle/oraBase/oracle/19.0.0/database
Patch validation checks successfully completed on home /oracle/oraBase/oracle/19.0.0/database
Verifying SQL patch applicability on home /oracle/oraBase/oracle/19.0.0/database
SQL patch applicability verified successfully on home /oracle/oraBase/oracle/19.0.0/database
Executing OPatch prereq operations to verify patch applicability on home /oracle/oraBase/19.0.0/grid
Patch applicability verified successfully on home /oracle/oraBase/19.0.0/grid
Executing patch validation checks on home /oracle/oraBase/19.0.0/grid
Patch validation checks successfully completed on home /oracle/oraBase/19.0.0/grid
Preparing to bring down database service on home /oracle/oraBase/oracle/19.0.0/database
Successfully prepared home /oracle/oraBase/oracle/19.0.0/database to bring down database service
Bringing down database service on home /oracle/oraBase/oracle/19.0.0/database
Following database has been stopped and will be restarted later during the session: prod
Database service successfully brought down on home /oracle/oraBase/oracle/19.0.0/database
Performing prepatch operations on CRS - bringing down CRS service on home /oracle/oraBase/19.0.0/grid
Prepatch operation log file location: /oracle/oraBase/grid/crsdata/oraserv1/crsconfig/hapatch_2022-03-18_02-55-17PM.log
CRS service brought down successfully on home /oracle/oraBase/19.0.0/grid
Start applying binary patch on home /oracle/oraBase/oracle/19.0.0/database
Binary patch applied successfully on home /oracle/oraBase/oracle/19.0.0/database
Start applying binary patch on home /oracle/oraBase/19.0.0/grid
Binary patch applied successfully on home /oracle/oraBase/19.0.0/grid
Performing postpatch operations on CRS - starting CRS service on home /oracle/oraBase/19.0.0/grid
Postpatch operation log file location: /oracle/oraBase/grid/crsdata/oraserv1/crsconfig/hapatch_2022-03-18_03-16-28PM.log
CRS service started successfully on home /oracle/oraBase/19.0.0/grid
Starting database service on home /oracle/oraBase/oracle/19.0.0/database
Database service successfully started on home /oracle/oraBase/oracle/19.0.0/database
Preparing home /oracle/oraBase/oracle/19.0.0/database after database service restarted
No step execution required.........
Trying to apply SQL patch on home /oracle/oraBase/oracle/19.0.0/database
SQL patch applied successfully on home /oracle/oraBase/oracle/19.0.0/database
OPatchAuto successful.
--------------------------------Summary--------------------------------
Patching is completed successfully. Please find the summary as follows:
Host:oraserv1
SIDB Home:/oracle/oraBase/oracle/19.0.0/database
Version:19.0.0.0.0
Summary:
==Following patches were SKIPPED:
Patch: /usr/software/oracle/33567274/33509923/33534448
Reason: This patch is not applicable to this specified target type - "oracle_database"
Patch: /usr/software/oracle/33567274/33509923/33575402
Reason: This patch is not applicable to this specified target type - "oracle_database"
Patch: /usr/software/oracle/33567274/33509923/33239955
Reason: This patch is not applicable to this specified target type - "oracle_database"
==Following patches were SUCCESSFULLY applied:
Patch: /usr/software/oracle/33567274/33509923/33515361
Log: /oracle/oraBase/oracle/19.0.0/database/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-18_14-55-44PM_1.log
Patch: /usr/software/oracle/33567274/33509923/33529556
Log: /oracle/oraBase/oracle/19.0.0/database/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-18_14-55-44PM_1.log
Host:oraserv1
SIHA Home:/oracle/oraBase/19.0.0/grid
Version:19.0.0.0.0
Summary:
==Following patches were SUCCESSFULLY applied:
Patch: /usr/software/oracle/33567274/33509923/33239955
Log: /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-18_15-06-21PM_1.log
Patch: /usr/software/oracle/33567274/33509923/33515361
Log: /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-18_15-06-21PM_1.log
Patch: /usr/software/oracle/33567274/33509923/33529556
Log: /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-18_15-06-21PM_1.log
Patch: /usr/software/oracle/33567274/33509923/33534448
Log: /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-18_15-06-21PM_1.log
Patch: /usr/software/oracle/33567274/33509923/33575402
Log: /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-18_15-06-21PM_1.log
OPatchauto session completed at Fri Mar 18 15:32:51 2022
Time taken to complete the session 41 minutes, 10 seconds
4. Apply the OJVM patch (Patch 33561310) as root user. This will apply to both GI Home and the DB Home, including applying sql patch to the database.
Verify database is up. As oracle, run:
$ srvctl status database -d PROD
Database is running.
As root, execute:
# export PATH=$PATH:/oracle/oraBase/19.0.0/grid/OPatch
# opatchauto apply /usr/software/oracle/33567274/33561310
OPatchauto session is initiated at Fri Mar 18 15:56:35 2022
System initialization log file is /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2022-03-18_03-56-42PM.log.
Session log file is /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchauto/opatchauto2022-03-18_03-56-47PM.log
The id for this session is FP8G
Executing OPatch prereq operations to verify patch applicability on home /oracle/oraBase/oracle/19.0.0/database
Patch applicability verified successfully on home /oracle/oraBase/oracle/19.0.0/database
Executing patch validation checks on home /oracle/oraBase/oracle/19.0.0/database
Patch validation checks successfully completed on home /oracle/oraBase/oracle/19.0.0/database
Verifying SQL patch applicability on home /oracle/oraBase/oracle/19.0.0/database
SQL patch applicability verified successfully on home /oracle/oraBase/oracle/19.0.0/database
Executing OPatch prereq operations to verify patch applicability on home /oracle/oraBase/19.0.0/grid
Patch applicability verified successfully on home /oracle/oraBase/19.0.0/grid
Executing patch validation checks on home /oracle/oraBase/19.0.0/grid
Patch validation checks successfully completed on home /oracle/oraBase/19.0.0/grid
Preparing to bring down database service on home /oracle/oraBase/oracle/19.0.0/database
Successfully prepared home /oracle/oraBase/oracle/19.0.0/database to bring down database service
Bringing down database service on home /oracle/oraBase/oracle/19.0.0/database
Following database has been stopped and will be restarted later during the session: prod
Database service successfully brought down on home /oracle/oraBase/oracle/19.0.0/database
Performing prepatch operations on CRS - bringing down CRS service on home /oracle/oraBase/19.0.0/grid
Prepatch operation log file location: /oracle/oraBase/grid/crsdata/orasrv1/crsconfig/hapatch_2022-03-18_03-59-04PM.log
CRS service brought down successfully on home /oracle/oraBase/19.0.0/grid
Start applying binary patch on home /oracle/oraBase/oracle/19.0.0/database
Binary patch applied successfully on home /oracle/oraBase/oracle/19.0.0/database
Start applying binary patch on home /oracle/oraBase/19.0.0/grid
Binary patch applied successfully on home /oracle/oraBase/19.0.0/grid
Performing postpatch operations on CRS - starting CRS service on home /oracle/oraBase/19.0.0/grid
Postpatch operation log file location: /oracle/oraBase/grid/crsdata/orasrv1/crsconfig/hapatch_2022-03-18_04-02-20PM.log
CRS service started successfully on home /oracle/oraBase/19.0.0/grid
Starting database service on home /oracle/oraBase/oracle/19.0.0/database
Database service successfully started on home /oracle/oraBase/oracle/19.0.0/database
Preparing home /oracle/oraBase/oracle/19.0.0/database after database service restarted
No step execution required.........
Trying to apply SQL patch on home /oracle/oraBase/oracle/19.0.0/database
SQL patch applied successfully on home /oracle/oraBase/oracle/19.0.0/database
OPatchAuto successful.
--------------------------------Summary--------------------------------
Patching is completed successfully. Please find the summary as follows:
Host:orasrv1
SIDB Home:/oracle/oraBase/oracle/19.0.0/database
Version:19.0.0.0.0
Summary:
==Following patches were SUCCESSFULLY applied:
Patch: /usr/software/oracle/33567274/33561310
Log: /oracle/oraBase/oracle/19.0.0/database/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-18_15-59-34PM_1.log
Host:orasrv1
SIHA Home:/oracle/oraBase/19.0.0/grid
Version:19.0.0.0.0
Summary:
==Following patches were SUCCESSFULLY applied:
Patch: /usr/software/oracle/33567274/33561310
Log: /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-18_16-01-03PM_1.log
OPatchauto session completed at Fri Mar 18 16:12:22 2022
Time taken to complete the session 15 minutes, 47 seconds
5. Apply the JDK patch as root user. This will apply to both GI Home and the DB Home, including applying sql patch to the database.
Verify database is running. As oracle, run:
$ srvctl status database -d PROD
Database is running.
As root, execute:
# export PATH=$PATH:/oracle/oraBase/19.0.0/grid/OPatch
# opatchauto apply /usr/software/oracle/33497160
OPatchauto session is initiated at Fri Mar 18 16:25:39 2022
System initialization log file is /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2022-03-18_04-25-41PM.log.
Session log file is /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchauto/opatchauto2022-03-18_04-25-45PM.log
The id for this session is KPQH
Executing OPatch prereq operations to verify patch applicability on home /oracle/oraBase/oracle/19.0.0/database
Patch applicability verified successfully on home /oracle/oraBase/oracle/19.0.0/database
Executing patch validation checks on home /oracle/oraBase/oracle/19.0.0/database
Patch validation checks successfully completed on home /oracle/oraBase/oracle/19.0.0/database
Verifying SQL patch applicability on home /oracle/oraBase/oracle/19.0.0/database
No step execution required.........
Executing OPatch prereq operations to verify patch applicability on home /oracle/oraBase/19.0.0/grid
Patch applicability verified successfully on home /oracle/oraBase/19.0.0/grid
Executing patch validation checks on home /oracle/oraBase/19.0.0/grid
Patch validation checks successfully completed on home /oracle/oraBase/19.0.0/grid
Preparing to bring down database service on home /oracle/oraBase/oracle/19.0.0/database
Successfully prepared home /oracle/oraBase/oracle/19.0.0/database to bring down database service
Bringing down database service on home /oracle/oraBase/oracle/19.0.0/database
No step execution required.........
Performing prepatch operations on CRS - bringing down CRS service on home /oracle/oraBase/19.0.0/grid
Prepatch operation log file location: /oracle/oraBase/grid/crsdata/orasrv1/crsconfig/hapatch_2022-03-18_04-26-27PM.log
CRS service brought down successfully on home /oracle/oraBase/19.0.0/grid
Start applying binary patch on home /oracle/oraBase/oracle/19.0.0/database
Binary patch applied successfully on home /oracle/oraBase/oracle/19.0.0/database
Start applying binary patch on home /oracle/oraBase/19.0.0/grid
Binary patch applied successfully on home /oracle/oraBase/19.0.0/grid
Performing postpatch operations on CRS - starting CRS service on home /oracle/oraBase/19.0.0/grid
Postpatch operation log file location: /oracle/oraBase/grid/crsdata/orasrv1/crsconfig/hapatch_2022-03-18_04-29-35PM.log
CRS service started successfully on home /oracle/oraBase/19.0.0/grid
Starting database service on home /oracle/oraBase/oracle/19.0.0/database
No step execution required.........
Preparing home /oracle/oraBase/oracle/19.0.0/database after database service restarted
No step execution required.........
Trying to apply SQL patch on home /oracle/oraBase/oracle/19.0.0/database
No step execution required.........
OPatchAuto successful.
--------------------------------Summary--------------------------------
Patching is completed successfully. Please find the summary as follows:
Host:orasrv1
SIDB Home:/oracle/oraBase/oracle/19.0.0/database
Version:19.0.0.0.0
Summary:
==Following patches were SUCCESSFULLY applied:
Patch: /usr/software/oracle/33497160
Log: /oracle/oraBase/oracle/19.0.0/database/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-18_16-26-59PM_1.log
Host:orasrv1
SIHA Home:/oracle/oraBase/19.0.0/grid
Version:19.0.0.0.0
Summary:
==Following patches were SUCCESSFULLY applied:
Patch: /usr/software/oracle/33497160
Log: /oracle/oraBase/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2022-03-18_16-28-20PM_1.log
OPatchauto session completed at Fri Mar 18 16:31:51 2022
Time taken to complete the session 6 minutes, 12 seconds
6. Verify.
DB Home
As oracle, execute:
$ opatch lsinventory|grep -A3 "^Patch.*applied"
Patch 33497160 : applied on Fri Mar 18 16:28:05 PDT 2022
Unique Patch ID: 24561626
Patch description: "JDK BUNDLE PATCH 19.0.0.0.220118"
Created on 22 Dec 2021, 21:34:55 hrs PST8PDT
--
Patch 33561310 : applied on Fri Mar 18 16:00:30 PDT 2022
Unique Patch ID: 24538862
Patch description: "OJVM RELEASE UPDATE: 19.14.0.0.220118 (33561310)"
Created on 5 Jan 2022, 08:13:10 hrs UTC
--
Patch 33529556 : applied on Fri Mar 18 15:06:08 PDT 2022
Unique Patch ID: 24583351
Patch description: "OCW RELEASE UPDATE 19.14.0.0.0 (33529556)"
Created on 9 Jan 2022, 21:15:36 hrs PST8PDT
--
Patch 33515361 : applied on Fri Mar 18 15:00:49 PDT 2022
Unique Patch ID: 24589353
Patch description: "Database Release Update : 19.14.0.0.220118 (33515361)"
Created on 13 Jan 2022, 06:14:07 hrs UTC
[oracle@nmdpstest-ads201 ~]$
[oracle@nmdpstest-ads201 ~]$ $ORACLE_HOME/jdk/bin/java -version
java version "1.8.0_321"
Java(TM) SE Runtime Environment (build 1.8.0_321-b07)
Java HotSpot(TM) 64-Bit Server VM (build 25.321-b07, mixed mode)
Check JDK in DB Home
$ $ORACLE_HOME/jdk/bin/java -version
java version "1.8.0_321"
Java(TM) SE Runtime Environment (build 1.8.0_321-b07)
Java HotSpot(TM) 64-Bit Server VM (build 25.321-b07, mixed mode)
GI Home
As user grid, execute:
$ $ORACLE_HOME/OPatch/opatch lsinventory|grep -A3 "^Patch.*applied"
Patch 33497160 : applied on Fri Mar 18 16:29:22 PDT 2022
Unique Patch ID: 24561626
Patch description: "JDK BUNDLE PATCH 19.0.0.0.220118"
Created on 22 Dec 2021, 21:34:55 hrs PST8PDT
--
Patch 33561310 : applied on Fri Mar 18 16:01:52 PDT 2022
Unique Patch ID: 24538862
Patch description: "OJVM RELEASE UPDATE: 19.14.0.0.220118 (33561310)"
Created on 5 Jan 2022, 08:13:10 hrs UTC
--
Patch 33575402 : applied on Fri Mar 18 15:16:20 PDT 2022
Unique Patch ID: 24505881
Patch description: "DBWLM RELEASE UPDATE 19.0.0.0.0 (33575402)"
Created on 16 Nov 2021, 09:32:52 hrs PST8PDT
--
Patch 33534448 : applied on Fri Mar 18 15:15:36 PDT 2022
Unique Patch ID: 24485874
Patch description: "ACFS RELEASE UPDATE 19.14.0.0.0 (33534448)"
Created on 3 Nov 2021, 01:41:03 hrs PST8PDT
--
Patch 33529556 : applied on Fri Mar 18 15:14:35 PDT 2022
Unique Patch ID: 24583351
Patch description: "OCW RELEASE UPDATE 19.14.0.0.0 (33529556)"
Created on 9 Jan 2022, 21:15:36 hrs PST8PDT
--
Patch 33515361 : applied on Fri Mar 18 15:09:40 PDT 2022
Unique Patch ID: 24589353
Patch description: "Database Release Update : 19.14.0.0.220118 (33515361)"
Created on 13 Jan 2022, 06:14:07 hrs UTC
--
Patch 33239955 : applied on Fri Mar 18 15:06:36 PDT 2022
Unique Patch ID: 24385395
Patch description: "TOMCAT RELEASE UPDATE 19.0.0.0.0 (33239955)"
Created on 25 Aug 2021, 09:25:51 hrs PST8PDT
Check JDK in GRID Home
$ $ORACLE_HOME/jdk/bin/java -version
java version "1.8.0_321"
Java(TM) SE Runtime Environment (build 1.8.0_321-b07)
Java HotSpot(TM) 64-Bit Server VM (build 25.321-b07, mixed mode)
Database
SQL> show con_name
CON_NAME
------------------------------
CDB$ROOT
SQL> set line 180 pages 999
SQL> col ACTION_TIME for A30
SQL> col STATUS for A15
SQL> col DESCRIPTION for A65
SQL> select action_time,status,description from DBA_REGISTRY_SQLPATCH;
ACTION_TIME STATUS DESCRIPTION
------------------------------ --------------- -----------------------------------------------------------------
16-MAR-22 10.49.33.370451 AM SUCCESS Database Release Update : 19.3.0.0.190416 (29517242)
18-MAR-22 03.32.33.585448 PM SUCCESS Database Release Update : 19.14.0.0.220118 (33515361)
18-MAR-22 04.12.14.216850 PM SUCCESS OJVM RELEASE UPDATE: 19.14.0.0.220118 (33561310)
SQL> select dbms_java.get_jdk_version() JDK_VERSION from dual;
JDK_VERSION
---------------
1.8.0_321
SQL> alter session set container=PDB$SEED;
Session altered.
SQL> select action_time,status,description from DBA_REGISTRY_SQLPATCH;
ACTION_TIME STATUS DESCRIPTION
------------------------------ --------------- -----------------------------------------------------------------
16-MAR-22 11.38.10.268959 AM SUCCESS Database Release Update : 19.3.0.0.190416 (29517242)
18-MAR-22 03.32.37.001757 PM SUCCESS Database Release Update : 19.14.0.0.220118 (33515361)
18-MAR-22 04.12.14.336009 PM SUCCESS OJVM RELEASE UPDATE: 19.14.0.0.220118 (33561310)
SQL> select dbms_java.get_jdk_version() JDK_VERSION from dual;
JDK_VERSION
---------------
1.8.0_321
SQL> alter session set container=PROD1PDB;
Session altered.
SQL> select action_time,status,description from DBA_REGISTRY_SQLPATCH;
ACTION_TIME STATUS DESCRIPTION
------------------------------ --------------- -----------------------------------------------------------------
16-MAR-22 11.38.10.293902 AM SUCCESS Database Release Update : 19.3.0.0.190416 (29517242)
18-MAR-22 03.32.40.578226 PM SUCCESS Database Release Update : 19.14.0.0.220118 (33515361)
18-MAR-22 04.12.14.382948 PM SUCCESS OJVM RELEASE UPDATE: 19.14.0.0.220118 (33561310)
SQL> select dbms_java.get_jdk_version() JDK_VERSION from dual;
JDK_VERSION
---------------
1.8.0_321