Oracle database patching - Windows Database Apr2025 Bundle Patch 19.27.0.0.250415

 

Description:-

Step by Step Applying PSU Patch in Oracle 19c in Windows Environment

Prerequisites to Apply Patch:-Database Release Update 19.27.0.0.250415

1.Shutdown Database Services and Listener

2.Upgrade OPatch Tool

3.Apply PSU patch on ORACLE_HOME in Windows Environment (p37486199_190000_MSWIN-x86-64)

4.Execute Post installation Scripts (datapatch)

5.Check invalid objects 

Patches Details:-

Install Oracle 19c Windows patch

This section includes the following patches:

Patch p37532350 - Windows Database Apr2025 Bundle Patch 19.27.0.0.250415

p6880880_190000_MSWIN-x86-64.zip - (OPatch Utlity)

p37532350_190000_MSWIN-x86-64.zip - (Database Bundle Patch)

p37499406_190000_MSWIN-x86-64.zip (OJVM Patch)

p37542054_190000_MSWIN-x86-64.zip (JDK Bundle Patch)

Note:

Verify that the Oracle OPatch utility version is latest.

We include 4 files and the following are the steps to install and verify the patches which needs to be executed in the order they are specified.

1. Download the patch files and follow the pre-install setup.

2. Upgrade OPatch.

3. Install the patches.

4. Verify the database and OJVM patch.

5. Verify the JDK version updates.

OJVM Patch download:- 37499406

JDK Bundle Patch download:- 37542054

Download the Opatch utility version:-

VIMP:-

Note:-

Pre-install setup

1. Make a note of the latest Oracle OJVM patch installed from the System Health Check report in the section Oracle Patch History.

Note:

If you have applied any of the OJVM patches before, then you will have to roll back the previous OJVM patch. Example the last applied OJVM patch was p37499406_190000_MSWIN-x86-64.zip , then it needs to be rolled back and the instruction to rollback is provided later under section Installing the Oracle patches step -7. If no prior OJVM patch found or if it is not 35648110 patch, then no rollback is needed.

2. Log in to the virtual machine or Server where NetBackup IT Analytics is installed.

3. Download the following files from the product download area of the website and save to C:\temp folder.

p6880880_190000_MSWIN-x86-64.zip - (OPatch Utlity)

p37532350_190000_MSWIN-x86-64.zip - (Database Bundle Patch)

p37499406_190000_MSWIN-x86-64.zip (OJVM Patch)

p37542054_190000_MSWIN-x86-64.zip (JDK Bundle Patch)

4. Access the command prompt as an Administrator.

5. Verify %ORACLE_HOME%\perl\bin is displayed in your PATH setting.

Note:

If not displayed in your PATH setting, enter the following:

set PATH=%ORACLE_HOME%\perl\bin;%PATH%

Set the Perl library path to empty.

set perl5lib=

OPatch installation

1. Change directory to the Oracle home directory.

2. Execute command cd C:\opt\oracle.

3. Rename the existing OPatch directory using the following command.

rename Opatch Opatch_old

4. Unzip the file p6880880_190000_MSWIN-x86-64.zip in C:\opt\oracle.

5. Execute the following command to verify the opatch version.

C:\opt\oracle\OPatch>opatch version.

OPatch Version: 12.2.0.1.45

Installing the patches

1.Stop the Listener and Shutdown Database Services 

listener stop

Database Stop:-

SQL> shut immediate;

2.  Stop - Distributed Transaction Coordinator service

c:\> sc query msdtc

sc query msdtc is a Windows command used to check the status of a Windows service named MSDTC (Microsoft Distributed Transaction Coordinator).

What this command does

• sc → Service Controller utility

• query → Asks for the current status of a service

• msdtc → The name of the service (Microsoft Distributed Transaction Coordinator)

Note:- As we have stopped the DB so disable the Database services from Windows Service like below

Note:

Verify that all the NetBackup IT Analytics services are stopped by checking in services. If services are still running, the patch installation will not be successful and will cause issues.

Explicitly stop the Distributed Transaction Coordinator service (which is not an Oracle service) if it is running using the following command.

net stop msdtc.

3. Rollbacking the overlay patches [37102264,37213431] 

The details are:

Reason -

Superset Patch 37532350 has Subset Patch 37486199 which has overlay patches [37102264,37213431] and these overlay patches conflict with Superset Patch or are not included in Superest Patch

If the last OJVM patch, for example, was p37499406_190000_MSWIN-x86-64.zip (OJVM Patch) then rollback by executing the

opatch rollback -id 37499406 command and follow the steps to rollback.

Rollback OJVM patch:-

c:\Oracle19c\OPatch> opatch rollback -id 37102264

Rollback JDK patch:-

c:\Oracle19c\OPatch> opatch rollback -id 37213431

Before Patch Need to set:

set ORACLE_HOME=C:\Oracle19c

set PATH=%ORACLE_HOME%\perl\bin;%PATH%

set ORACLE_SID=ORCL

set PERL5LIB=

a. Applying Database Bundle Patch Below patch 

p37532350_190000_MSWIN-x86-64.zip - (Database Bundle Patch)

b.  Applying OJVM Patch 

p37499406_190000_MSWIN-x86-64.zip (OJVM Patch)

c. Applying JDK Bundle Patch

p37542054_190000_MSWIN-x86-64.zip (JDK Bundle Patch) 

After patching services setting  need to set as before and also need to start the services

Verify OPatch succeeded using the following commands which will show the OPatch application results of database, OJVM and JDK patches:

C:\opt\oracle\OPatch\opatch lsinventory -detail

Re-start the Distributed Transaction Coordinator service, which is not an Oracle service, using the following command.

net start msdtc

Connect to SQL Plus using the following command:

sqlplus / as sysdba

SQL> startup 

Execute the following command to complete the post-install SQL deployment for the patch being installed. This data patch command applies the patch to the database.

C:\opt\Oracle\Opatch\datapatch -verbose

Validating the database and OJVM Patches

1. Connect to SQL Plus using the following command.

   sqlplus / as sysdba

2. Query to check registry for patch history.

   SQL>select * from sys.registry$history;

3. Query to check registry for installed patch.

   SQL>select * from sys.registry$sqlpatch ;

4. Report output with patch details:

   SQL> set serveroutput on

   SQL> exec dbms_qopatch.get_sqlpatch_status;