April CPU JDK Upgrade on DB and Grid Homes in Oracle 19c Real Application Cluster Setup

 

Current Version:-

GRID HOME:-

grid> cd $GRID_HOME/jdk/bin

grid> ./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)

 

ORACLE_HOME:-

oracle> $ORACLE_HOME/jdk/bin

oracle> ./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)

 

grid>$GRID_HOME/Opatch

grid>./opatch lspatches

33575402;DBWLM RELEASE UPDATE 19.0.0.0.0 (33575402)

33534448;ACFS RELEASE UPDATE 19.14.0.0.0 (33534448)

33529556;OCW RELEASE UPDATE 19.14.0.0.0 (33529556)

33515361;Database Release Update : 19.14.0.0.220118 (33515361)

33239955;TOMCAT RELEASE UPDATE 19.0.0.0.0 (33239955)

OPatch succeeded.

 

Download the Latest patch and place it to the server from Oracle Support using the following Document “Critical Patch Update (CPU) Program Apr 2024 Patch Availability Document (DB-only) (Doc ID 3000005.1)”

Patch#= 36195552

Give rights to the Patch Dir:-

Root> chown -Rf grid:oinstall 36195552/

Root> chmod -Rf 777 36195552/

 

 

 

2.1 OPatch Utility

You must use the OPatch utility version 12.2.0.1.41 or later to apply this patch. Oracle recommends that you use the latest released OPatch version for 12.2 which is available for download from My Oracle Support patch 6880880 by selecting the 12.2.0.1.0 release.

 

Applying the Patch:-

Grid>export PATH=$PATH:/u01/app/grid/OPatch

Go to the patch location

[grid@rac1 36195552]$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./=

 

Stop the database instance on Node2  :-

oracle> srvctl stop instance –i test2 –d test

Analyzing the patch

su – root

Root> opatchauto apply 36195552 -analyze -oh $GRID_HOME

 

Once the analyses is completed successfully, apply the patch on the Grid infrastructure of NODE2

 

Su – root

Cd /home/patches/update_patch/36195552       à patch Directory

opatchauto apply 35642822 -oh $GRID_HOME

 

Start the Database services on Node 2

Oracle> srvctl start instance –i test2 –d test

Now perform the same procedure for Node1 to apply the Patch.

 

Now Apply the Patch on Oracle Database Home.

Shut down the Oracle Services on Node 2 first:-

srvctl stop instance –i test2 –d test

Validation of Oracle Inventory

su – oracle

cd $ORACLE_HOME/OPatch

./opatch lsinventory

Run OPatch Conflict Check

cd  /home/oracle/DB/19.0.0/db_home/OPatch

./opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /home/patches/update_patch/36195566     à Patch Location

 

Analyzing the patch application.

su – oracle

[oracle@rac1-test ~]$ export PATH=$ORACLE_HOME/OPatch:$PATH

[oracle@rac1-test ~]$ opatch version

OPatch Version: 12.2.0.1.40

OPatch succeeded.

 [oracle@rac1-test update_patch]# cd /home/patches/update_patch/36195566

[oracle@rac1-test 36195566]$ opatch apply

 

Patch 35643107 successfully applied.

Sub-set patch [29517242] has become inactive due to the application of a super-set patch [35643107].

Please refer to Doc ID 2161861.1 for any possible further required actions.

 

Start the Oracle Services on Node 2:-

srvctl start instance –i test2 –d test

Now perform the same procedure for Node1 to apply the Patch.

 

Updated Version:-

GRID HOME:-

grid> cd $GRID_HOME/jdk/bin

grid> ./java -version

java version “1.8.0_401”

Java(TM) SE Runtime Environment (build 1.8.0_311-b11)

Java HotSpot(TM) 64-Bit Server VM (build 25.311-b11, mixed mode)

 

ORACLE_HOME:-

oracle> $ORACLE_HOME/jdk/bin

oracle> ./java -version

java version “1.8.0_401”

Java(TM) SE Runtime Environment (build 1.8.0_311-b11)

Java HotSpot(TM) 64-Bit Server VM (build 25.311-b11, mixed mode)