0% found this document useful (0 votes)
102 views130 pages

DB Patching 19.x.x.x to 19.x.x.x

The document outlines the process and requirements for patching Oracle Database 19.x.x.x, emphasizing the necessity of a full backup and the supported upgrade paths. It details the steps for downloading patches, pre-patching tasks, and verifying database connectivity post-patch. Additionally, it includes information on patch release statuses and validation checks for applied patches.

Uploaded by

Nalwa Aatish
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
102 views130 pages

DB Patching 19.x.x.x to 19.x.x.x

The document outlines the process and requirements for patching Oracle Database 19.x.x.x, emphasizing the necessity of a full backup and the supported upgrade paths. It details the steps for downloading patches, pre-patching tasks, and verifying database connectivity post-patch. Additionally, it includes information on patch release statuses and validation checks for applied patches.

Uploaded by

Nalwa Aatish
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 130

DB Patching 19.x.x.x to 19.x.x.

x Current
Requirements and Assumptions
Backup Oracle Home
Upgrade Path
Download / Extract Patches
Pre Patching Tasks
Rollback Previous Applied OJVM, JDK & Perl
Upgrade 19.x Binary to latest Critical Patch
Patch Database
Verify & Test DB Connectivity

Requirements and Assumptions


Oracle Database 19.x is ONLY supported on OPERA 5.6.11 and above.

DO NOT ATTEMPT THIS UPGRADE WITHOUT A FULL LEVEL 0 BACKUP - Make sure to have a VALID BACKUP in place.

Backup is beyond the scope of the document. It is assumed the Level 0 backups have been done and is successful.

This document DOES NOT cover the installation of 19.x software or any other unspecified non standard patches.

Backup Oracle Home


Warning

Even if you DO NOT backup the full ORACLE_HOME folder - make sure the backup the .patch_storage folders BEFORE patching.
AND use 7-zip to Backup (Windows Zip will NOT work) D Drive may differ

%ORACLE_HOME%\.patch_storage

C:\Program Files\Oracle\Inventory

C:\Program Files (x86)\Oracle\Inventory

Upgrade Path
Latest PreUpgrade.jar file can be downloaded here.

How to Download and Run Oracle's Database Pre-Upgrade Utility (Doc ID 884522.1)

Following Direct Upgrade Paths to 19.x are supported


Download / Extract Patches
The OPERA DB Media (at the time of this document) comes with Oracle Database 19.7.0.0 April 2020 Patches Deployed

Use 7-ZIP to extract all PATCH files to D:\STAGE folder

Make sure to confirm which CPU Patches are to be deployed on site

For 19.x Database and Patches - Opera version limitations Apply

Opera version 5.6.11+ Supported

October 2024 (DB Layer)


Document Status

Image Legends

Patch ALL relevant Patches have been Released in MOS


Release Status
These patches are NOT YET certified for use in Prod/Live/On Premise environments

The patches have been internally tested for documentation purposes.

Deployment Status Below conditions also apply

Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY
Source CPU Alerts Released Oct 2024

Critical Patch Update (CPU) Program Oct 2024 Patch Availability Document (DB-only) (Doc ID 3036945.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Oracle Critical Patch Update (CPU) Oct 2024 for Oracle Java SE (Doc ID 3047853.1)

Primary Note DST FAQ : Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches
(Doc ID 412160.1)

Oracle Database (RDBMS) Releases Support Status Summary (Doc ID 161818.1)

Oracle Lifetime Support Policy (Database/Others)

Validation Oracle Hospitality OPERA 5 - Technology Components - Critical Patch Update (CPU) 2773929.1 - Search for DOC DOC2735 in
ICCP

Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1) - Search for DOC
DOC8165 in ICCP

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 15-Oct-24 - Initial Draft

16-OCT-24 - Work in progress / deployment steps documentation / Testing

30-Oct-24 - All Patches released in DB/Client/Pending Approval for deployment

Patch# Details Comments

6880880 x64 Bit OPatch 12.2.0.1.44 for DB 19.0.0.0.0 (Oct 2024) New

36878821 x64 Bit WINDOWS DATABASE BUNDLE PATCH New


19.25.0.0.241015 WIN BP

36878697 x64 Bit OJVM RELEASE UPDATE 19.25.0.0.241015 OJVM RU New

36866578 x64 Bit JDK 8u431 JDK BUNDLE PATCH 19.0.0.0.241015 New

Timezone DSTV43 - TZ43 TZDATA2024A

36260493 Not x64 Bit RDBMS - DSTV43 UPDATE - TZDATA2024A NOT REQUIRED Already included in OCT 2024 DB
Required Bundle Patch

36260537 Not x64 Bit DSTV43 UPDATE - TZDATA2024A - NEED OJVM FIX NOT REQUIRED Already included in OCT 2024 OJVM
Required Bundle Patch

Misc Notes and Comments

Applied Patches Known Issue

================

=======================================================
RDBMS Oracle Homes in this Host WFIVM10584
=======================================================
D:\ORACLE\1970 Found....

===========================
RDBMS Home : D:\ORACLE\1970
===========================

SQL*Plus: Release 19.0.0.0.0 - Production


Version 19.25.0.0.0

OPatch Version: 12.2.0.1.44

OPatch succeeded.

===========================
LSPatches Patch Listing
===========================
36866578;JDK BUNDLE PATCH 19.0.0.0.241015
36878697;OJVM RELEASE UPDATE: 19.25.0.0.241015 (36878697)
36878821;Windows Database Bundle Patch : 19.25.0.0.241015 (36878821)

36260493 Timezone Patch Picked from LSInventory

36260537 Timezone OJVMFix Patch Picked from LSInventory

===========================
LSInventory Patch Listing
===========================

Date Patch
Description
---- -----
-----------
Thu Oct 31 00:52:31 GMT 2024 36878821 "Windows Database Bundle Patch : 19.25.0.0.241015
(36878821)"
Thu Oct 31 01:00:50 GMT 2024 36878697 "OJVM RELEASE UPDATE: 19.25.0.0.241015
(36878697)"
Thu Oct 31 01:07:20 GMT 2024 36866578 "JDK BUNDLE PATCH
19.0.0.0.241015"

===================================================
Latest Timezone Files : D:\ORACLE\1970\oracore\zoneinfo
===================================================
Timezone timezone_43.dat Found in DB Home
Timezone timezlrg_43.dat Found in DB Home

==============================================
RDBMS/JDK Home : D:\ORACLE\1970\JDK\bin
==============================================
java version "1.8.0_431"
Java(TM) SE Runtime Environment (build 1.8.0_431-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.431-b10, mixed mode)

==============================================
RDBMS/JDK/JRE Home : D:\ORACLE\1970\JDK\JRE\bin
==============================================
java version "1.8.0_431"
Java(TM) SE Runtime Environment (build 1.8.0_431-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.431-b10, mixed mode)

==============================================
RDBMS/Perl Home : D:\ORACLE\1970\perl\bin
==============================================
This is perl 5, version 38, subversion 2 (v5.38.2) built for MSWin32-x64-multi-thread

==================================
Check Response / Message / Prompt
Confirm : Patch Listing Report of RDBMS Environment Completed
Default Reponse recorded : OK
** 31/10/2024 2:01:49.67 **
==================================

==================================================
Validate Applied Patch vs List of Patches Provided
RDBMS Home : D:\ORACLE\1970
==================================================

======================================
Verify Applied Patch 36878821
======================================
36878821;Windows Database Bundle Patch : 19.25.0.0.241015 (36878821)
Patch 36878821 Found / Applied in Oracle Home D:\ORACLE\1970 - Confirmed Applied OK

======================================
Verify Applied Patch 36878697
======================================
36878697;OJVM RELEASE UPDATE: 19.25.0.0.241015 (36878697)
Patch 36878697 Found / Applied in Oracle Home D:\ORACLE\1970 - Confirmed Applied OK

======================================
Verify Applied Patch 36866578
======================================
36866578;JDK BUNDLE PATCH 19.0.0.0.241015
Patch 36866578 Found / Applied in Oracle Home D:\ORACLE\1970 - Confirmed Applied OK

========================================
Verify Applied Patch 36260493 to D:\ORACLE\1970
========================================
36260493 Patch Picked from LSInventory
Patch 36260493 Found / Applied in Oracle Home D:\ORACLE\1970 - Confirmed Applied OK

========================================
Verify Applied Patch 36260537 to D:\ORACLE\1970
========================================
36260537 Patch Picked from LSInventory
Patch 36260537 Found / Applied in Oracle Home D:\ORACLE\1970 - Confirmed Applied OK

============================================================================================
Verify Patch 36260493 / File timezlrg_43.dat to D:\ORACLE\1970\oracore\zoneinfo
============================================================================================
Timezone Patch 36260493 / File timezlrg_43.dat found / Applied in Oracle Home D:\ORACLE\1970
- Confirmed Applied OK

================================
Check TNSPING for DB Connections
** 31/10/2024 2:03:11.85 **
================================
TNSPING Check / Connect completed sucessfully

==========================
Check OS Authentication
** 31/10/2024 2:03:12.11 **
==========================
Check OS Authentication completed sucessfully

==========================================================
Verify Bundle Patch 36878821 Applied to DB SQL/Registry
==========================================================
Bundle Patch 36878821 Found / Applied to DB Registry - Confirmed Applied OK

==========================================================
Verify OJVM Patch 36878697 Applied to DB SQL/Registry
==========================================================
OJVM Patch 36878697 Found / Applied to DB Registry - Confirmed Applied OK

==========================================================================================
Verify DB Timezone Patch 36260493 / File timezlrg_43.dat Applied to DB SQL/Registry
===========================================================================================
TZ Patch 36260493 / File timezlrg_43.dat / Applied to DB Registry - Confirmed Applied
OK

==========================================================================================
Verify Timezone Patch 36260493 / Version 43 Applied to DB SQL/Registry
==========================================================================================
TZ Patch 36260493 / Version 43 / Applied to DB Registry - Confirmed Applied OK

July 2024 (DB Layer)


Document Status

Image Legends

Patch Patches have been Released in MOS


Release Status
These patches are certified for use in Prod/Live/On Premise environments

Deployment Status
Below conditions also apply
The patches have been internally tested ONLY for documentation purposes.
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released July 2024

Critical Patch Update (CPU) Program Jul 2024 Patch Availability Document (DB-only) (Doc ID 3027813.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Oracle Critical Patch Update (CPU) Jul 2024 for Oracle Java SE (Doc ID 3031998.1)

Primary Note DST FAQ : Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches
(Doc ID 412160.1)
Validation Oracle Hospitality OPERA 5 - Technology Components - Critical Patch Update (CPU) 2773929.1 - Search for DOC DOC2735 in
ICCP

Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1) - Search for DOC
DOC8165 in ICCP

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 16-Jul-24 - Initial Draft

24-Jul-24- Prepare Steps - Doc preparations

28-Jul-24- Lab Testing and Approval based on DOC DOC2735 in ICCP

14-Aug-24 - Approved for on premise deployment

Patch# Details Comments

6880880 x64 Bit OPatch 12.2.0.1.43 for DB 19.0.0.0.0 (Jul 2024) New

36521936 x64 Bit WINDOWS DATABASE BUNDLE PATCH New


19.24.0.0.240716 WIN BP

36414915 x64 Bit OJVM RELEASE UPDATE 19.24.0.0.240716 OJVM RU New

36538667 x64 Bit JDK 8u421 JDK BUNDLE PATCH 19.0.0.0.240716 New

Timezone DSTV43 - TZ43 TZDATA2024A

36260493 Not x64 Bit RDBMS - DSTV43 UPDATE - TZDATA2024A NOT REQUIRED Already included in JULY 2024 DB
Required Bundle Patch

36260537 Not x64 Bit DSTV43 UPDATE - TZDATA2024A - NEED OJVM FIX NOT REQUIRED Already included in JULY 2024 OJVM
Required Bundle Patch

Misc Notes and Comments

Applied Patches Known Issue

================
OPATCH Version
RDBMS Home : D:\ORACLE\1970
================
OPatch Version: 12.2.0.1.43

OPatch succeeded.

===========================
OPATCH Listing - Full List
RDBMS Home : D:\ORACLE\1970
===========================
36538667;JDK BUNDLE PATCH 19.0.0.0.240716
36414915;OJVM RELEASE UPDATE: 19.24.0.0.240716 (36414915)
36521936;Windows Database Bundle Patch : 19.24.0.0.240716 (36521936)

36260493;Timezone Patch Picked from LSInventory

36260537;Timezone OJVMFIX Patch Picked from LSInventory

===================
Check Perl version
RDBMS Home : D:\ORACLE\1970
Perl Home : D:\ORACLE\1970\perl\bin
===================

This is perl 5, version 38, subversion 2 (v5.38.2) built for MSWin32-x64-multi-thread

Copyright 1987-2023, Larry Wall


Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on


this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at https://www.perl.org/, the Perl Home Page.

===================
Check D:\ORACLE\1970\jdk JDK version
RDBMS Home : D:\ORACLE\1970
JDK HOME : D:\ORACLE\1970\JDK
JAVA Home : D:\ORACLE\1970\JDK\bin
JAVA LOCATION : D:\ORACLE\1970\JDK\BIN
===================
java version "1.8.0_421"
Java(TM) SE Runtime Environment (build 1.8.0_421-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.421-b09, mixed mode)

===================
Check D:\ORACLE\1970\jdk\jre JDK/JRE version
RDBMS Home : D:\ORACLE\1970
JDK/JRE HOME : D:\ORACLE\1970\JDK\JRE
JAVA Home : D:\ORACLE\1970\JDK\JRE\bin
JAVA LOCATION : D:\ORACLE\1970\JDK\JRE\BIN
===================
java version "1.8.0_421"
Java(TM) SE Runtime Environment (build 1.8.0_421-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.421-b09, mixed mode)

=======================
Check Rollback Patches
RDBMS Home : D:\ORACLE\1970
=======================
======================================
Verify Rollback Patch 30805684
======================================
Patch 30805684 NOT found in Oracle Home D:\ORACLE\1970 - Rollback Sucessfull

=======================
Check Applied Patches
RDBMS Home : D:\ORACLE\1970
=======================
Jan 2023 and above Bundle Patches also included TZ Patches
Due to this the TZ Patch Number may not be visible
in opatch listing

======================================
Verify Applied Patch 36521936
======================================
36521936;Windows Database Bundle Patch : 19.24.0.0.240716 (36521936)
Patch 36521936 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 36414915
======================================
36414915;OJVM RELEASE UPDATE: 19.24.0.0.240716 (36414915)
Patch 36414915 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 36538667
======================================
36538667;JDK BUNDLE PATCH 19.0.0.0.240716
Patch 36538667 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

========================================
Verify Applied Patch 36260493 to D:\ORACLE\1970
========================================
36260493;Timezone Patch Picked from LSInventory
Patch 36260493 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

========================================
Verify Applied Patch 36260537 to D:\ORACLE\1970
========================================
36260537;Timezone Patch Picked from LSInventory
Patch 36260537 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

============================
Verify Timezone Patch applied to DB Home
36260493 / timezlrg_43.dat
============================
Timezone Patch 36260493 timezlrg_43.dat Found / Applied to DB Home - Confirmed Applied
OK

==========================================================
Verify Applied Bundle Patch 36521936 to DB Registry
==========================================================
Bundle Patch 36521936 Found / Applied to DB Registry - Confirmed Applied OK

==========================================================
Verify Applied OJVM Patch 36414915 to DB Registry
==========================================================
OJVM Patch 36414915 Found / Applied to DB Registry - Confirmed Applied OK

============================
Verify Timezone Patch applied to DB Registry
36260493 / timezlrg_43.dat
============================
Timezone Patch 36260493 timezlrg_43.dat Found / Applied to DB Registry - Confirmed Applied
OK

============================
Verify Timezone version applied to DB Registry
36260493 / 43
============================
Timezone Patch 36260493 43 Found / Applied to DB Registry - Confirmed Applied OK

Apr 2024 (DB Layer)


Document
Status

Image Legends

Patch Patches have been Released in MOS and approved for On Premise use
Release Status

Deployment
Status These patches have been superseded and no longer applicable.
These patches are certified for use in Prod/Live environments
The patches have been released in MOS and internally tested ONLY for documentation purposes.
Did not test or check any vulnerabilities or do any regression/performance or stability testing
Below conditions also ALSO apply
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released April 2024

Critical Patch Update (CPU) Program Apr 2024 Patch Availability Document (DB-only) (Doc ID 3000005.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Oracle Critical Patch Update (CPU) Apr 2024 for Oracle Java SE (Doc ID 3012587.1)

Primary Note DST FAQ : Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches (Doc
ID 412160.1)

Applying the DSTv42 update for the Oracle Database (Doc ID 2941491.1) (Doc ID 2941491.1)

Validation Oracle Hospitality OPERA 5 - Technology Components - Critical Patch Update (CPU) 2773929.1 - No Update After April 2023 -
Search for DOC DOC2735 in ICCP

Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1) - No Update After
April 2023 - Search for DOC DOC8165 in ICCP

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 17-Apr-24 - Initial Draft

19-Apr-24 - Prepare Steps - Doc preparations

25-Apr-24 - timezone 43 added

26-Apr-24 - Lab Testing and Approval based on DOC DOC2735 in ICCP

14-Aug-24 - Superseded by July 2024

Patch# Details Comments

6880880 x64 Bit OPatch 12.2.0.1.42 for DB 19.0.0.0.0 (Apr 2024) New

36219938 x64 Bit WINDOWS DATABASE BUNDLE PATCH 19.23.0.0.240416 WIN BP New

36199232 x64 Bit OJVM RELEASE UPDATE 19.23.0.0.240416 OJVM RU New

36195566 x64 Bit JDK 8u411 JDK BUNDLE PATCH 19.0.0.0.240416 New

Timezone DSTV43 - TZ43 TZDATA2024A

36260493 x64 Bit RDBMS - DSTV43 UPDATE - TZDATA2024A Already included in APR 2024 DB Bundle Patch

36260537 DSTV43 UPDATE - TZDATA2024A - NEED OJVM FIX NOT included in APR 2024 DB Bundle Patch

Misc Notes and Comments

Applied Known Issue


Patches

================
OPATCH Version
RDBMS Home : D:\ORACLE\1970
================
OPatch Version: 12.2.0.1.42

OPatch succeeded.

===========================
OPATCH Listing (Full List)
RDBMS Home : D:\ORACLE\1970
===========================
36260537;DSTV43 UPDATE - TZDATA2024A - NEED OJVM FIX
36195566;JDK BUNDLE PATCH 19.0.0.0.240416
36199232;OJVM RELEASE UPDATE: 19.23.0.0.240416 (36199232)
36219938;Windows Database Bundle Patch : 19.23.0.0.240416 (36219938)
36260493;Timezone Patch Picked from LSInventory

===================
Check Perl version
RDBMS Home : D:\ORACLE\1970
Perl Home : D:\ORACLE\1970\perl\bin
===================

This is perl 5, version 38, subversion 0 (v5.38.0) built for MSWin32-x64-multi-thread

Copyright 1987-2023, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on


this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at https://www.perl.org/, the Perl Home Page.

===================
Check D:\ORACLE\1970\jdk JDK version
RDBMS Home : D:\ORACLE\1970
JDK HOME : D:\ORACLE\1970\JDK
JAVA Home : D:\ORACLE\1970\JDK\bin
JAVA LOCATION : D:\ORACLE\1970\JDK\BIN
===================
java version "1.8.0_411"
Java(TM) SE Runtime Environment (build 1.8.0_411-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.411-b09, mixed mode)

===================
Check D:\ORACLE\1970\jdk\jre JDK/JRE version
RDBMS Home : D:\ORACLE\1970
JDK/JRE HOME : D:\ORACLE\1970\JDK\JRE
JAVA Home : D:\ORACLE\1970\JDK\JRE\bin
JAVA LOCATION : D:\ORACLE\1970\JDK\JRE\BIN
===================
java version "1.8.0_411"
Java(TM) SE Runtime Environment (build 1.8.0_411-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.411-b09, mixed mode)

=======================
Check Rollback Patches
RDBMS Home : D:\ORACLE\1970
=======================
======================================
Verify Rollback Patch 30805684
======================================
Patch 30805684 NOT found in Oracle Home D:\ORACLE\1970 - Rollback Sucessfull

=======================
Check Applied Patches
RDBMS Home : D:\ORACLE\1970
=======================
Jan 2023 and above Bundle Patches also included TZ Patches
Due to this the TZ Patch Number may not be visible
in opatch listing

======================================
Verify Applied Patch 36219938
======================================
36219938;Windows Database Bundle Patch : 19.23.0.0.240416 (36219938)
Patch 36219938 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 36199232
======================================
36199232;OJVM RELEASE UPDATE: 19.23.0.0.240416 (36199232)
Patch 36199232 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 36195566
======================================
36195566;JDK BUNDLE PATCH 19.0.0.0.240416
Patch 36195566 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

========================================
Verify Applied Patch 36260493 to D:\ORACLE\1970
========================================
36260493;Timezone Patch Picked from LSInventory
Patch 36260493 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 36260537
======================================
36260537;DSTV43 UPDATE - TZDATA2024A - NEED OJVM FIX
Patch 36260537 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

============================
Verify Timezone Patch applied to DB Home
36260493 / timezlrg_43.dat
============================
Timezone Patch 36260493 timezlrg_43.dat Found / Applied to DB Home - Confirmed Applied OK

==========================================================
Verify Applied Bundle Patch 36219938 to DB Registry
==========================================================
Bundle Patch 36219938 Found / Applied to DB Registry - Confirmed Applied OK

==========================================================
Verify Applied OJVM Patch 36199232 to DB Registry
==========================================================
OJVM Patch 36199232 Found / Applied to DB Registry - Confirmed Applied OK

============================
Verify Timezone Patch applied to DB Registry
36260493 / timezlrg_43.dat
============================
Timezone Patch 36260493 timezlrg_43.dat Found / Applied to DB Registry - Confirmed Applied
OK

============================
Verify Timezone version applied to DB Registry
36260493 / 43
============================
Timezone Patch 36260493 43 Found / Applied to DB Registry - Confirmed Applied OK

==================================
Check Response / Message / Prompt
** 26/04/2024 13:29:39.87 **
==================================

Confirm : Review the Highlighted Issues if any in the log/output.

==================================
User Reponse recorded as : OK
** 26/04/2024 13:29:39.87 **
==================================

January 2024 (DB Layer)


Document
Status

Image Legends

Patch Patches have been Released in MOS and approved for On Premise use
Release Status

Deployment
Status These patches have been superseded and no longer applicable.
Did not test or check any vulnerabilities or do any regression/performance or stability testing
Below conditions also apply

19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released Jan 2024

Critical Patch Update (CPU) Program Jan 2024 Patch Availability Document (DB-only) (Doc ID 2986269.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Oracle Critical Patch Update (CPU) Jan 2024 for Oracle Java SE (Doc ID 2992318.1)

Primary Note DST FAQ : Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches (Doc
ID 412160.1)

Applying the DSTv42 update for the Oracle Database (Doc ID 2941491.1) (Doc ID 2941491.1)

Validation Oracle Hospitality OPERA 5 - Technology Components - Critical Patch Update (CPU) 2773929.1 - No Update After April 2023 -
Search for DOC DOC2735 in ICCP

Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1) - No Update After
April 2023 - Search for DOC DOC8165 in ICCP

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names
Update History 17-Jan-24 - Initial Draft

31-Jan-24 - Patch released / Testing

26-Feb-24 - Approval for On Premise use based on DOC DOC8165 in ICCP on ICCP

21-May-24 - Patch List Superseded

Patch# Details Comments

6880880 x64 Bit OPatch 12.2.0.1.41 for DB 19.0.0.0.0 (Jan 2024 or later) New

35962832 x64 Bit WINDOWS DATABASE BUNDLE PATCH 19.22.0.0.240116 WIN BP New

35926646 x64 Bit OJVM RELEASE UPDATE 19.22.0.0.240116 OJVM RU New

35949090 x64 Bit JDK 8u401 BUNDLE PATCH 19.0.0.0.240116 New

Timezone DSTV42 - TZ42 TZDATA2023C

35220732 RDBMS - DSTV42 UPDATE - TZDATA2023C Already included in JAN 2024 DB Bundle Patch

35239280 DSTV42 UPDATE - TZDATA2023C - NEED OJVM FIX NOT included in JAN 2024 DB Bundle Patch

Misc Notes and Comments

Applied Known Issue


Patches
Deploy Notes:

Beginning from Jan 2023, TIMEZONE updates are included within the quarterly patches

Beginning from Jan2023, Perl updates are included within the quarterly patches

Beginning with the October 2022 patching cycle, 19c RURs will no longer be provided for 19.17.0 and above.
No additional RURs will be delivered on any platform after the delivery of Oracle Database 19c RUR 19.16.2 in January, 2023.
Refer to Sunsetting of 19c RURs and FAQ (Note 2898381.1) for further details.

To provide customers more frequent access to recommended and well-tested collections of patches,
Oracle is pleased to introduce Monthly Recommended Patches (MRPs) starting in Nov 2022.
MRPs are supported only on the Linux x86-64 platform. Refer to Introducing Monthly Recommended Patches (MRPs)
and FAQ (Note 2898740.1) for further details.

Beginning with OJVM Release Update 18.4 and later (including 19c and beyond) the OJVM Release Updates are now Oracle RAC
Rolling installable.
However, the rollback to older versions such as 18.2 and 18.1 will be Non-Rolling.
To use the RAC Rolling approach, out-of-place patching of the Oracle Home is mandatory, as is the use of database services and
SRVCTL to
control instance and service operations. For further information, please refer to MOS NOTE 2217053.1,
RAC Rolling Install Process for the "Oracle JavaVM Component Database PSU/RU"(OJVM PSU/RU) Patches.

================
OPATCH Version
RDBMS Home : D:\ORACLE\1970
================
OPatch Version: 12.2.0.1.41

OPatch succeeded.

===========================
OPATCH Listing (Full List)
RDBMS Home : D:\ORACLE\1970
===========================
35949090;JDK BUNDLE PATCH 19.0.0.0.240116
35926646;OJVM RELEASE UPDATE: 19.22.0.0.240116 (35926646)
35962832;Windows Database Bundle Patch : 19.22.0.0.240116 (35962832)
35239280;DSTV42 UPDATE - TZDATA2023C - NEED OJVM FIX
35220732;Timezone Patch Picked from LSInventory
===================
Check Perl version
RDBMS Home : D:\ORACLE\1970
Perl Home : D:\ORACLE\1970\perl\bin
===================

This is perl 5, version 36, subversion 0 (v5.36.0) built for MSWin32-x64-multi-thread

Copyright 1987-2022, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on


this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at https://www.perl.org/, the Perl Home Page.

===================
Check D:\ORACLE\1970\jdk JDK version
RDBMS Home : D:\ORACLE\1970
JDK HOME : D:\ORACLE\1970\JDK
JAVA Home : D:\ORACLE\1970\JDK\bin
JAVA LOCATION : D:\ORACLE\1970\JDK\BIN
===================
java version "1.8.0_401"
Java(TM) SE Runtime Environment (build 1.8.0_401-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.401-b10, mixed mode)

===================
Check D:\ORACLE\1970\jdk\jre JDK/JRE version
RDBMS Home : D:\ORACLE\1970
JDK/JRE HOME : D:\ORACLE\1970\JDK\JRE
JAVA Home : D:\ORACLE\1970\JDK\JRE\bin
JAVA LOCATION : D:\ORACLE\1970\JDK\JRE\BIN
===================
java version "1.8.0_401"
Java(TM) SE Runtime Environment (build 1.8.0_401-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.401-b10, mixed mode)

=======================
Check Rollback Patches
RDBMS Home : D:\ORACLE\1970
=======================
======================================
Verify Rollback Patch 35648110
======================================
Patch 35648110 NOT found in Oracle Home D:\ORACLE\1970 - Rollback Sucessfull

======================================
Verify Rollback Patch 35638318
======================================
Patch 35638318 NOT found in Oracle Home D:\ORACLE\1970 - Rollback Sucessfull

=======================
Check Applied Patches
RDBMS Home : D:\ORACLE\1970
=======================
Jan 2023 and above Bundle Patches also included TZ Patches
Due to this the TZ Patch Number may not be visible
in opatch listing
======================================
Verify Applied Patch 35962832
======================================
35962832;Windows Database Bundle Patch : 19.22.0.0.240116 (35962832)
Patch 35962832 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 35926646
======================================
35926646;OJVM RELEASE UPDATE: 19.22.0.0.240116 (35926646)
Patch 35926646 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 35949090
======================================
35949090;JDK BUNDLE PATCH 19.0.0.0.240116
Patch 35949090 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

========================================
Verify Applied Patch 35220732 to D:\ORACLE\1970
========================================
35220732;Timezone Patch Picked from LSInventory
Patch 35220732 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 35239280
======================================
35239280;DSTV42 UPDATE - TZDATA2023C - NEED OJVM FIX
Patch 35239280 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

============================
Verify Timezone Patch applied to DB Home
35220732 / timezlrg_42.dat
============================
Timezone Patch 35220732 timezlrg_42.dat Found / Applied to DB Home - Confirmed Applied OK

==========================================================
Verify Applied Bundle Patch 35962832 to DB Registry
==========================================================
Bundle Patch 35962832 Found / Applied to DB Registry - Confirmed Applied OK

==========================================================
Verify Applied OJVM Patch 35926646 to DB Registry
==========================================================
OJVM Patch 35926646 Found / Applied to DB Registry - Confirmed Applied OK

============================
Verify Timezone Patch applied to DB Registry
35220732 / timezlrg_42.dat
============================
Timezone Patch 35220732 timezlrg_42.dat Found / Applied to DB Registry - Confirmed Applied
OK

============================
Verify Timezone version applied to DB Registry
35220732 / 42
============================
Timezone Patch 35220732 42 Found / Applied to DB Registry - Confirmed Applied OK
October 2023 (DB Layer)
Document
Status

Image Legends

Patch All Patches have been Released in MOS


Release Status

Deployment
Status These patches have been superseded and no longer applicable.
The Patches have been released in MOS and internally tested only for documentation pruposes
Below conditions also apply
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released October 2023

Critical Patch Update (CPU) Program Oct 2023 Patch Availability Document (DB-only) (Doc ID 2966413.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Oracle Critical Patch Update (CPU) Oct 2023 for Oracle Java SE (Doc ID 2978178.1)

Primary Note DST FAQ : Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches (Doc
ID 412160.1)

Applying the DSTv42 update for the Oracle Database (Doc ID 2941491.1) (Doc ID 2941491.1)

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1) - No Update After
April 2023 - Search for DOC DOC8165 in ICCP

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 17-Oct-23 - Initial Draft

30-Oct-23 - Internal Test and Lab Validation

26-Feb-24 - Patces Superseded by Jan 2024

Patch# Details Comments

6880880 OPatch 12.2.0.1.40 for DB 19.0.0.0.0 (Oct 2023 or later) Released

35681552 WINDOWS DATABASE BUNDLE PATCH 19.21.0.0.231017

35648110 OJVM RELEASE UPDATE 19.21.0.0.231017

35638318 JDK8u391 BUNDLE PATCH 19.21.0.0.231017

Timezone DSTV42 - TZ42 TZDATA2023E - The Timezone 42 Patch 35220732 is already included in the JULY 2023 Patch / TZ 42 35239280
OJVM FIX is not included
35220732 RDBMS - DSTV42 UPDATE - TZDATA2023E Already included in JULY 2023 DB Bundle Patch

Optional - Required ONLY if TZ is also upgrading to TZ42

35239280 DSTV42 UPDATE - TZDATA2023E - NEED OJVM FIX NOT included in JULY 2023 DB Bundle Patch

Optional - Required ONLY if TZ is also upgrading to TZ42

Misc Notes and Comments

Applied Known Issue


Patches
Deploy Notes:

Beginning from Jan 2023, TIMEZONE updates are included within the quarterly patches

Beginning from Jan2023, Perl updates are included within the quarterly patches

Beginning with the October 2022 patching cycle, 19c RURs will no longer be provided for 19.17.0 and above.
No additional RURs will be delivered on any platform after the delivery of Oracle Database 19c RUR 19.16.2 in January, 2023.
Refer to Sunsetting of 19c RURs and FAQ (Note 2898381.1) for further details.

To provide customers more frequent access to recommended and well-tested collections of patches,
Oracle is pleased to introduce Monthly Recommended Patches (MRPs) starting in Nov 2022.
MRPs are supported only on the Linux x86-64 platform. Refer to Introducing Monthly Recommended Patches (MRPs)
and FAQ (Note 2898740.1) for further details.

Beginning with OJVM Release Update 18.4 and later (including 19c and beyond) the OJVM Release Updates are now Oracle RAC
Rolling installable.
However, the rollback to older versions such as 18.2 and 18.1 will be Non-Rolling.
To use the RAC Rolling approach, out-of-place patching of the Oracle Home is mandatory, as is the use of database services and
SRVCTL to
control instance and service operations. For further information, please refer to MOS NOTE 2217053.1,
RAC Rolling Install Process for the "Oracle JavaVM Component Database PSU/RU"(OJVM PSU/RU) Patches.

================
OPATCH Version
RDBMS Home : D:\ORACLE\1970
================
OPatch Version: 12.2.0.1.40

OPatch succeeded.

===========================
OPATCH Listing (Full List)
RDBMS Home : D:\ORACLE\1970
===========================
35239280;DSTV42 UPDATE - TZDATA2023C - NEED OJVM FIX
35638318;JDK BUNDLE PATCH 19.0.0.0.231017
35648110;OJVM RELEASE UPDATE: 19.21.0.0.231017 (35648110)
35681552;Windows Database Bundle Patch : 19.21.0.0.231017 (35681552)
35220732;Timezone Patch Picked from LSInventory

===================
Check Perl version
RDBMS Home : D:\ORACLE\1970
Perl Home : D:\ORACLE\1970\perl\bin
===================

This is perl 5, version 36, subversion 0 (v5.36.0) built for MSWin32-x64-multi-thread

Copyright 1987-2022, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on


this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at https://www.perl.org/, the Perl Home Page.

===================
Check D:\ORACLE\1970\jdk JDK version
RDBMS Home : D:\ORACLE\1970
JDK HOME : D:\ORACLE\1970\JDK
JAVA Home : D:\ORACLE\1970\JDK\bin
JAVA LOCATION : D:\ORACLE\1970\JDK\BIN
===================
java version "1.8.0_391"
Java(TM) SE Runtime Environment (build 1.8.0_391-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.391-b13, mixed mode)

===================
Check D:\ORACLE\1970\jdk\jre JDK/JRE version
RDBMS Home : D:\ORACLE\1970
JDK/JRE HOME : D:\ORACLE\1970\JDK\JRE
JAVA Home : D:\ORACLE\1970\JDK\JRE\bin
JAVA LOCATION : D:\ORACLE\1970\JDK\JRE\BIN
===================
java version "1.8.0_391"
Java(TM) SE Runtime Environment (build 1.8.0_391-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.391-b13, mixed mode)

=======================
Check Rollback Patches
RDBMS Home : D:\ORACLE\1970
=======================
======================================
Verify Rollback Patch 30805684
======================================
Patch 30805684 NOT found in Oracle Home D:\ORACLE\1970 - Rollback Sucessfull

=======================
Check Applied Patches
RDBMS Home : D:\ORACLE\1970
=======================
Jan 2023 and above Bundle Patches also included TZ Patches
Due to this the TZ Patch Number may not be visible
in opatch listing

======================================
Verify Applied Patch 35681552
======================================
35681552;Windows Database Bundle Patch : 19.21.0.0.231017 (35681552)
Patch 35681552 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 35648110
======================================
35648110;OJVM RELEASE UPDATE: 19.21.0.0.231017 (35648110)
Patch 35648110 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 35638318
======================================
35638318;JDK BUNDLE PATCH 19.0.0.0.231017
Patch 35638318 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

========================================
Verify Applied Patch 35220732 to D:\ORACLE\1970
========================================
35220732;Timezone Patch Picked from LSInventory
Patch 35220732 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 35239280
======================================
35239280;DSTV42 UPDATE - TZDATA2023C - NEED OJVM FIX
Patch 35239280 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

============================
Verify Timezone Patch applied to DB Home
35220732 / timezlrg_42.dat
============================
Timezone Patch 35220732 timezlrg_42.dat Found / Applied to DB Home - Confirmed Applied OK

==========================================================
Verify Applied Bundle Patch 35681552 to DB Registry
==========================================================
Bundle Patch 35681552 Found / Applied to DB Registry - Confirmed Applied OK

==========================================================
Verify Applied OJVM Patch 35648110 to DB Registry
==========================================================
OJVM Patch 35648110 Found / Applied to DB Registry - Confirmed Applied OK

============================
Verify Timezone Patch applied to DB Registry
35220732 / timezlrg_42.dat
============================
Timezone Patch 35220732 timezlrg_42.dat Found / Applied to DB Registry - Confirmed Applied
OK

============================
Verify Timezone version applied to DB Registry
35220732 / 42
============================
Timezone Patch 35220732 42 Found / Applied to DB Registry - Confirmed Applied OK

July 2023 (DB Layer)


Docu
ment
Status

Image Legends
Patch All Patches have been Released in MOS - These patches have been superseded and no longer applicable.
Releas
e Stat
us

Deploy
ment These patches have been superseded and no longer applicable.
Status The Patches have been released in MOS and internally tested only for documentation pruposes
Below conditions also apply
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released July 2023

Critical Patch Update (CPU) Program Jul 2023 Patch Availability Document (DB-only) (Doc ID 2946185.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Oracle Critical Patch Update (CPU) Jul 2023 for Oracle Java SE (Doc ID 2957260.1)

Validat Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1) - !!! NOTE !!!! NO MORE
ion UPDATES AFTER APRIL 2023 !!! - Please search DOC8165 in ICCP - Oracle Security Releases for Oracle Hospitality OPERA - R&D
Based Testing Results Only (Doc ID 2189898.1) Please search DOC8165 in ICCP

Miscell When extracting - please use 7zip - Windows internal Zip has issued with long file names
aneous

Update 18-Jul-23 - Initial Draft


History
08-Aug-23 - ALl Patches released

14-Aug-23 - JDK Patches released - Test in progress

16-Aug-23 - Internal Tests completed

Patch# Details Comments

6880880 OPatch 12.2.0.1.39 for DB 19.0.0.0.0 (July 2023 or later)

35348034 WINDOWS DATABASE BUNDLE PATCH 19.20.0.0.230718

35354406 OJVM RELEASE UPDATE 19.20.0.0.230718

35336174 JDK8u381 BUNDLE PATCH 19.0.0.0.230718

Timezone DSTV42 - TZ42 TZDATA2023E - The Timezone 42 Patch 35220732 is already included in the JULY 2023 Patch / TZ 42 35239280
OJVM FIX is not included

35220732 RDBMS - DSTV42 UPDATE - TZDATA2023E Already included in JULY 2023 DB Bundle Patch

Optional - Required ONLY if TZ is also upgrading to TZ42

35239280 DSTV42 UPDATE - TZDATA2023E - NEED OJVM FIX NOT included in JULY 2023 DB Bundle Patch

Optional - Required ONLY if TZ is also upgrading to TZ42

Misc Notes and Comments

Applied Known Issue


Patches
Deploy Notes:

Beginning from Jan 2023, TIMEZONE updates are included within the quarterly patches

Beginning from Jan2023, Perl updates are included within the quarterly patches

Beginning with the October 2022 patching cycle, 19c RURs will no longer be provided for 19.17.0 and above.
No additional RURs will be delivered on any platform after the delivery of Oracle Database 19c RUR 19.16.2 in January, 2023.
Refer to Sunsetting of 19c RURs and FAQ (Note 2898381.1) for further details.
To provide customers more frequent access to recommended and well-tested collections of patches,
Oracle is pleased to introduce Monthly Recommended Patches (MRPs) starting in Nov 2022.
MRPs are supported only on the Linux x86-64 platform. Refer to Introducing Monthly Recommended Patches (MRPs)
and FAQ (Note 2898740.1) for further details.

Beginning with OJVM Release Update 18.4 and later (including 19c and beyond) the OJVM Release Updates are now Oracle RAC
Rolling installable.
However, the rollback to older versions such as 18.2 and 18.1 will be Non-Rolling.
To use the RAC Rolling approach, out-of-place patching of the Oracle Home is mandatory, as is the use of database services and
SRVCTL to
control instance and service operations. For further information, please refer to MOS NOTE 2217053.1,
RAC Rolling Install Process for the "Oracle JavaVM Component Database PSU/RU"(OJVM PSU/RU) Patches.
Check OPATCH Version
=======================
OPatch Version: 12.2.0.1.39

Check OPATCH lspatches


=======================
35336174;JDK BUNDLE PATCH 19.0.0.0.230718
35354406;OJVM RELEASE UPDATE: 19.20.0.0.230718 (35354406)
35348034;Windows Database Bundle Patch : 19.20.0.0.230718 (35348034)

Check Perl version


=======================
cd /d D:\ORACLE\1970\perl\bin

This is perl 5, version 36, subversion 0 (v5.36.0) built for MSWin32-x64-multi-thread

Check JDK Version


=======================
java version "1.8.0_381"
Java(TM) SE Runtime Environment (build 1.8.0_381-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.381-b09, mixed mode)

=======================
Validate Applied Patch
=======================

======================================
Verify Rollback Patch 30805684
======================================
Patch 30805684 NOT found in Oracle Home D:\ORACLE\1970 - Rollback Sucessfull

=======================
Validate Applied Patch
=======================

Jan 2023 and above Bundle Patches also included TZ Patches


Due to this the TZ Patch Number may not be visible
in opatch listing

======================================
Verify Applied Patch 35348034
======================================
35348034;Windows Database Bundle Patch : 19.20.0.0.230718 (35348034)
Patch 35348034 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 35354406
======================================
35354406;OJVM RELEASE UPDATE: 19.20.0.0.230718 (35354406)
Patch 35354406 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 35336174
======================================
35336174;JDK BUNDLE PATCH 19.0.0.0.230718
Patch 35336174 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull
Apr 2023 (DB Layer)
Document Status

Image Legends

Patch Release Status All Patches have been Released in MOS

Deployment Status
These patches have been superseded and no longer applicable.
The Patches have been released in MOS and internally tested only for documentation pruposes
Below conditions also apply
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released Apr 2023

Critical Patch Update (CPU) Program Apr 2023 Patch Availability Document (DB-only) (Doc ID 2923348.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Oracle Critical Patch Update (CPU) Apr 2023 for Oracle Java SE (Doc ID 2935948.1)

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 19-May-23 - Initial Draft

22-May-23 - Internal Test/Documentation

25-May-23 - Approval (Doc ID 2189898.1)

17-July-23 - PAD Doc Links corrected

Patch# Details Comments

6880880 OPatch 12.2.0.1.37 for DB 19.0.0.0.0 (Apr 2023 or later)

35046439 WINDOWS DATABASE BUNDLE PATCH 19.19.0.0.230418 Includes Perl and TZ 40

35050341 OJVM RELEASE UPDATE 19.19.0.0.230418

35004974 JDK BUNDLE PATCH 19.0.0.0.230418

Timezone DSTV42 - TZ42 TZDATA2023E - The Timezone 40 Patch is already included in the April 2023 Patch

35220732 RDBMS - DSTV42 UPDATE - TZDATA2023E Optional - Required ONLY if TZ is also upgrading to TZ42

35239280 DSTV42 UPDATE - TZDATA2023E - NEED OJVM FIX Optional - Required ONLY if TZ is also upgrading to TZ42

Misc Notes and Comments

Applied Known Issue


Patches
If DB is open upgrade - datapatch -verbose fails

Doc Ref: 19.x:datapatch failed with 'ORA-13516: AWR Operation failed: CATPROC not valid ' (Doc ID 2922690.1)

Solution : open DB in normal mode and re run datapatch -verbose

Deploy Notes:

Beginning from Jan 2023, TIMEZONE updates are included within the quarterly patches
Beginning from Jan2023, Perl updates are included within the quarterly patches

Beginning with the October 2022 patching cycle, 19c RURs will no longer be provided for 19.17.0 and above.
No additional RURs will be delivered on any platform after the delivery of Oracle Database 19c RUR 19.16.2 in January, 2023.
Refer to Sunsetting of 19c RURs and FAQ (Note 2898381.1) for further details.

To provide customers more frequent access to recommended and well-tested collections of patches,
Oracle is pleased to introduce Monthly Recommended Patches (MRPs) starting in Nov 2022.
MRPs are supported only on the Linux x86-64 platform. Refer to Introducing Monthly Recommended Patches (MRPs)
and FAQ (Note 2898740.1) for further details.

Beginning with OJVM Release Update 18.4 and later (including 19c and beyond) the OJVM Release Updates are now Oracle RAC
Rolling installable.
However, the rollback to older versions such as 18.2 and 18.1 will be Non-Rolling.
To use the RAC Rolling approach, out-of-place patching of the Oracle Home is mandatory, as is the use of database services and
SRVCTL to
control instance and service operations. For further information, please refer to MOS NOTE 2217053.1,
RAC Rolling Install Process for the "Oracle JavaVM Component Database PSU/RU"(OJVM PSU/RU) Patches.

Check OPATCH Version


=======================
OPatch Version: 12.2.0.1.37

OPatch succeeded.

Check OPATCH lspatches


=======================
34699616;DSTV40 UPDATE - TZDATA2022E - NEED OJVM FIX
35004974;JDK BUNDLE PATCH 19.0.0.0.230418
35050341;OJVM RELEASE UPDATE: 19.19.0.0.230418 (35050341)
35046439;Windows Database Bundle Patch : 19.19.0.0.230418 (35046439)

Check Perl version


=======================
cd /d D:\ORACLE\1970\perl\bin

This is perl 5, version 36, subversion 0 (v5.36.0) built for MSWin32-x64-multi-thread

Copyright 1987-2022, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on


this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at https://www.perl.org/, the Perl Home Page.

Check JDK Version


=======================
java version "1.8.0_371"
Java(TM) SE Runtime Environment (build 1.8.0_371-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.371-b11, mixed mode)

=======================
Validate Applied Patch
=======================

Jan 2023 and above Bundle Patches also included TZ Patches


Due to this the TZ Patch Number may not be visible
in opatch listing

======================================
Verify Applied Patch 35046439
======================================
35046439;Windows Database Bundle Patch : 19.19.0.0.230418 (35046439)
Patch 35046439 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 35050341
======================================
35050341;OJVM RELEASE UPDATE: 19.19.0.0.230418 (35050341)
Patch 35050341 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 35004974
======================================
35004974;JDK BUNDLE PATCH 19.0.0.0.230418
Patch 35004974 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 34699616
======================================
34699616;DSTV40 UPDATE - TZDATA2022E - NEED OJVM FIX
Patch 34699616 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

============================
Verify Timezone Patch applied to DB Home
34698179 / timezlrg_40.dat
============================

Timezone Patch 34698179 timezlrg_40.dat Found / Applied to DB Home - Confirmed Applied OK

==========================================================
Verify Applied Bundle Patch 35046439 to DB Registry
==========================================================

Bundle Patch 35046439 Found / Applied to DB Registry - Confirmed Applied OK

==========================================================
Verify Applied OJVM Patch 35050341 to DB Registry
==========================================================

OJVM Patch 35050341 Found / Applied to DB Registry - Confirmed Applied OK

============================
Verify Timezone Patch applied to DB Registry
34698179 / timezlrg_40.dat
============================

Timezone Patch 34698179 timezlrg_40.dat Found / Applied to DB Registry - Confirmed Applied


OK

============================
Verify Timezone version applied to DB Registry
34698179 / 40
============================

Timezone Patch 34698179 40 Found / Applied to DB Registry - Confirmed Applied OK


IMPORTANT

Issue:

If you apply CPU Patches for 19c DB JAN 2023 AND TZ40 in this order - these below are the encountered issues

Jan 2023 ALREADY includes TZ 40 - See doc : Steps to update the timezone after applying 19.18 DBRU & higher (Doc ID
2940808.1)
The TZ 40 Files in ORACLE_HOME\oracore\zoneinfo is NOT copied across
If JAN 2023 is already applied then you CANNOT apply TZ 40 Patches as it causes conflicts
You CANNOT do the DB upgrade to TZ 40 as the files in oracore don’t exist

Solution:

If the Environment is going to go to JAN 2023 AND TZ 40 - then make sure to :

Apply TZ 40 Patches to oracle Home - 34698179 / 34699616


Apply JAN 2023 CPU Patches to Oracle Home 34750795 / 34786990 / 34777391

Now you proceed with your DBUPGRADE and TZ upgrades as normal.

Jan 2023 (DB Layer)


Document Status

Image Legends

Patch Release Status All Patches have been Released in MOS

Deployment Status
These patches have been superseded and no longer applicable.
The Patches have been released in MOS and internally tested only for documentation pruposes
Below conditions also apply
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released Jan 2023

Critical Patch Update (CPU) Program Jan 2023 Patch Availability Document (DB-only) (Doc ID 2906899.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Oracle Critical Patch Update (CPU) Jan 2023 for Oracle Java SE (Doc ID 2917310.1)

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 19-Jan-23 - Initial Draft

08-Mar-23 - OJVM Release

09-Mar-23 - Internal Lab Test

04-May-23 - Added TZ40 Patches due to Missing files workaround

25-May-23 - Superseded by April 2023

Patch# Details Comments

6880880 OPatch 12.2.0.1.36 for DB 19.0.0.0.0 (Jan 2023 or later)

34750795 WINDOWS DATABASE BUNDLE PATCH 19.18.0.0.230117

34786990 OJVM RELEASE UPDATE 19.18.0.0.230117

34777391 JDK BUNDLE PATCH 19.18.0.0.230117


Timezone DSTV40 - TZ40 TZDATA2022E

The Timezone 40 Patch is already included in the JAn 2023 Patch - but due to TZ missing file issues is being added here in the steps as a
workaround

34698179 RDBMS - DSTV40 UPDATE - TZDATA2022E

34699616 DSTV40 UPDATE - TZDATA2022E - NEED OJVM FIX

Beginning from Jan2023, Perl updates are included within the quarterly patches Doc ID 2584628.1

Misc Notes and Comments

Applied Known Issue


Patches
If DB is open upgrade - datapatch -verbose fails

Doc Ref: 19.x:datapatch failed with 'ORA-13516: AWR Operation failed: CATPROC not valid ' (Doc ID 2922690.1)

Solution : open DB in normal mode and re run datapatch -verbose

Deploy Notes:
Beginning from Jan2023, Perl updates are included within the quarterly patches

Beginning with the October 2022 patching cycle, 19c RURs will no longer be provided for 19.17.0 and above.
No additional RURs will be delivered on any platform after the delivery of Oracle Database 19c RUR 19.16.2 in January, 2023.
Refer to Sunsetting of 19c RURs and FAQ (Note 2898381.1) for further details.

To provide customers more frequent access to recommended and well-tested collections of patches,
Oracle is pleased to introduce Monthly Recommended Patches (MRPs) starting in Nov 2022.
MRPs are supported only on the Linux x86-64 platform. Refer to Introducing Monthly Recommended Patches (MRPs)
and FAQ (Note 2898740.1) for further details.

Beginning with OJVM Release Update 18.4 and later (including 19c and beyond) the OJVM Release Updates are now Oracle RAC
Rolling installable.
However, the rollback to older versions such as 18.2 and 18.1 will be Non-Rolling.
To use the RAC Rolling approach, out-of-place patching of the Oracle Home is mandatory, as is the use of database services and
SRVCTL to
control instance and service operations. For further information, please refer to MOS NOTE 2217053.1,
RAC Rolling Install Process for the "Oracle JavaVM Component Database PSU/RU"(OJVM PSU/RU) Patches.
To be added

Check OPATCH Version


=======================
OPatch Version: 12.2.0.1.36

Check OPATCH lspatches


=======================

34777391;JDK BUNDLE PATCH 19.0.0.0.230117


34786990;OJVM RELEASE UPDATE: 19.18.0.0.230117 (34786990)
34750795;Windows Database Bundle Patch : 19.18.0.0.230117 (34750795)
34699616;DSTV40 UPDATE - TZDATA2022E - NEED OJVM FIX

Check Perl version


===================
ECHO is off.
cd /d D:\ORACLE\1970\perl\bin

This is perl 5, version 36, subversion 0 (v5.36.0) built for MSWin32-x64-multi-thread

Copyright 1987-2022, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on


this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at https://www.perl.org/, the Perl Home Page.

Check JDK Version


=======================

java version "1.8.0_361"


Java(TM) SE Runtime Environment (build 1.8.0_361-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.361-b09, mixed mode)

Oct 2022 (DB Layer)


Document Status

Image Legends

Patch Release Status All Patches have been Released in MOS


Deployment Status
These patches are certified for use in Prod/Live environments
The Patches have been released in MOS and internally tested only for documentation pruposes
I did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released Oct 2022

Critical Patch Update (CPU) Program Oct 2022 Patch Availability Document (DB-only) (Doc ID 2888497.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 10-Nov-22 - Initial Draft

11-Nov-22 - Testing and documentation

20-Nov-22 - New DB Bundle Patch released which allows Perl Patch

29-Nov-22 - Approval Doc (Doc ID 2189898.1)

Patch# Details Comments

6880880 OPatch 12.2.0.1.33 for DB 19.0.0.0.0 (Oct 2022 or later) Oct 2022 or Later

34468114 WINDOWS DATABASE BUNDLE PATCH 19.17.0.0.221018 ** New Patch released on 17-11-22

34411846 OJVM RELEASE UPDATE 19.17.0.0.0.221018 ** New

34422617 JDK BUNDLE PATCH 19.0.0.0.221018 ** New

33912872 DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 - LIBEXPAT UPDATE) ** New

Misc Notes and Comments

Applied Perl Patch CONFLICT below error with Oct 2022 DB Bundle patch - Occurs ONLY if you use OLD released DB Bundle patch
Patches 34468114 - released BEFORE 17-11-22
==================================================
Apply Patch 33912872 to D:\ORACLE\1970
==================================================

33912872 does not exist...Will Apply Patch

Oracle Interim Patch Installer version 12.2.0.1.33


Copyright (c) 2022, Oracle Corporation. All rights reserved.

PREREQ session

Oracle Home : D:\ORACLE\1970


Central Inventory : D:\Oracle\Inventory
from :
OPatch version : 12.2.0.1.33
OUI version : 12.2.0.7.0
Log file location : D:\ORACLE\1970\cfgtoollogs\opatch\opatch2022-11-10_23-57-05PM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

ZOP-40: The patch(es) has conflicts with other patches installed in the Oracle Home (or) among
themselves.

Prereq "checkConflictAgainstOHWithDetail" failed.

Summary of Conflict Analysis:

There are no patches that can be applied now.

Following patches have conflicts. Please contact Oracle Support and get the merged patch of the
patches :
33912872, 34468114

Conflicts/Supersets for each patch are:

Patch : 33912872

Conflict with 34468114


Conflict details:
D:\ORACLE\1970\perl\html\lib\ExtUtils\CBuilder\Platform\Unix.html
D:\ORACLE\1970\perl\lib\ExtUtils\CBuilder\Platform\Unix.pm
D:\ORACLE\1970\perl\html\lib\File\Spec\Unix.html
D:\ORACLE\1970\perl\html\lib\ExtUtils\MM_Unix.html
D:\ORACLE\1970\perl\lib\ExtUtils\MM_Unix.pm
D:\ORACLE\1970\perl\lib\File\Spec\Unix.pm

OPatch succeeded.

Check OPATCH Version


=======================

OPatch Version: 12.2.0.1.33

Check OPATCH lspatches


=======================

33912872;DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 - LIBEXPAT UPDATE)


34422617;JDK BUNDLE PATCH 19.0.0.0.221018
34411846;OJVM RELEASE UPDATE: 19.17.0.0.221018 (34411846)
34468114;Windows Database Bundle Patch : 19.17.0.0.221018 (34468114)
32327201;RDBMS - DSTV36 UPDATE - TZDATA2020E

===================
Check Perl version
===================
ECHO is off.
cd /d D:\ORACLE\1970\perl\bin
This is perl 5, version 32, subversion 0 (v5.32.0) built for MSWin32-x64-multi-thread

===================
Check JDK Version
===================
ECHO is off.
java version "1.8.0_351"
Java(TM) SE Runtime Environment (build 1.8.0_351-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.351-b10, mixed mode)

=======================
Validate Rollback Patch
=======================

======================================
Verify Rollback Patch 33912872
======================================
Patch 33912872 NOT found in Oracle Home D:\ORACLE\1970 - Rollback Sucessfull

======================================
Verify Rollback Patch 31732095
======================================
Patch 31732095 NOT found in Oracle Home D:\ORACLE\1970 - Rollback Sucessfull

======================================
Verify Rollback Patch 30805684
======================================
Patch 30805684 NOT found in Oracle Home D:\ORACLE\1970 - Rollback Sucessfull

=======================
Check Applied Patches
=======================

==========================================================
Verify Applied Patch 34468114 to D:\ORACLE\1970
==========================================================
34468114;Windows Database Bundle Patch : 19.17.0.0.221018 (34468114)
Patch 34468114 Found / Applied in Oracle Home D:\ORACLE\1970 - Confirmed Applied OK

==========================================================
Verify Applied Patch 34411846 to D:\ORACLE\1970
==========================================================
34411846;OJVM RELEASE UPDATE: 19.17.0.0.221018 (34411846)
Patch 34411846 Found / Applied in Oracle Home D:\ORACLE\1970 - Confirmed Applied OK

==========================================================
Verify Applied Patch 34422617 to D:\ORACLE\1970
==========================================================
34422617;JDK BUNDLE PATCH 19.0.0.0.221018
Patch 34422617 Found / Applied in Oracle Home D:\ORACLE\1970 - Confirmed Applied OK

==========================================================
Verify Applied Patch 33912872 to D:\ORACLE\1970
==========================================================
33912872;DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 - LIBEXPAT UPDATE)
Patch 33912872 Found / Applied in Oracle Home D:\ORACLE\1970 - Confirmed Applied OK
==========================================================
Verify Applied Bundle Patch 34468114 to DB Registry
==========================================================

Bundle Patch 34468114 Found / Applied to DB Registry - Confirmed Applied OK

==========================================================
Verify Applied OJVM Patch 34411846 to DB Registry
==========================================================

OJVM Patch 34411846 Found / Applied to DB Registry - Confirmed Applied OK

July 2022 (DB Layer)


Document Status

Image Legends

Patch Release Status All Patches have been Released in MOS

Deployment Status
These patches have been superseded and no longer applicable.
Below conditions also apply
id not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released July 2022

Critical Patch Update (CPU) Program Jul 2022 Patch Availability Document (DB-only) (Doc ID 2867871.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 05-Aug-22 - Initial Draft

06-Aug-22 - Testing

09-Aug-22 - Approval Doc (Doc ID 2189898.1)

29-Nov-22 - Supseeded by Oct 2022

Patch# Details Comments

6880880 OPatch 12.2.0.1.32 for DB 19.0.0.0.0 (Apr 2022 or later) July 2022 or Later

34110685 WINDOWS DATABASE BUNDLE PATCH 19.16.0.0.220719

34086870 OJVM RELEASE UPDATE 19.16.0.0.0

34113634 JDK BUNDLE PATCH 19.0.0.0.220719

33912872 DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 - LIBEXPAT UPDATE) Not Tested in GRID/RAC

Misc Notes and Comments

Applied Patches
Check OPATCH Version
=======================
OPatch Version: 12.2.0.1.32
OPatch succeeded.

Check OPATCH lspatches


=======================
33912872;DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 - LIBEXPAT UPDATE)
34113634;JDK BUNDLE PATCH 19.0.0.0.220719
34086870;OJVM RELEASE UPDATE: 19.16.0.0.220719 (34086870)
34110685;Windows Database Bundle Patch : 19.16.0.0.220719 (34110685)

Check Perl version


=======================
cd /d D:\ORACLE\1970\perl\bin

This is perl 5, version 32, subversion 0 (v5.32.0) built for MSWin32-x64-multi-thread

Copyright 1987-2020, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on


this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

Check JDK Version


=======================
java version "1.8.0_341"
Java(TM) SE Runtime Environment (build 1.8.0_341-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.341-b10, mixed mode)

=======================
Validate Rollback Patch
=======================

======================================
Verify Rollback Patch 30805684
======================================
Patch 30805684 NOT found in Oracle Home D:\ORACLE\1970 - Rollback Sucessfull

Done

=======================
Validate Applied Patch
=======================

======================================
Verify Applied Patch 34110685
======================================
34110685;Windows Database Bundle Patch : 19.16.0.0.220719 (34110685)
Patch 34110685 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 34086870
======================================
34086870;OJVM RELEASE UPDATE: 19.16.0.0.220719 (34086870)
Patch 34086870 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 34113634
======================================
34113634;JDK BUNDLE PATCH 19.0.0.0.220719
Patch 34113634 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

======================================
Verify Applied Patch 31732095
======================================
33912872;DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 - LIBEXPAT UPDATE)
Patch 33912872 Found / Applied in Oracle Home D:\ORACLE\1970 - Patch Apply Sucessfull

==========================================================
Verify Applied Bundle Patch 34110685 to DB Registry
==========================================================

Bundle Patch 34110685 Found / Applied to DB Registry - Confirmed Applied OK

==========================================================
Verify Applied OJVM Patch 34086870 to DB Registry
==========================================================

OJVM Patch 34086870 Found / Applied to DB Registry - Confirmed Applied OK

April 2022 (DB Layer)


Document Status

Image Legends

Patch Release Status All Patches have been Released in MOS

Deployment Status
These patches have been superseded and no longer applicable.
The patches have been released in MOS and internally tested ONLY for documentation purposes.
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released April 2022

Critical Patch Update (CPU) Program Apr 2022 Patch Availability Document (DB-only) (Doc ID 2844795.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 20-Apr-22 - Initial Draft

22-May-22 - Approved for on Premise

Patch# Details Comments

6880880 OPatch 12.2.0.1.30 for DB 19.0.0.0.0 (Apr 2022 or later) April 2022 or Later

33829175 WINDOWS DATABASE BUNDLE PATCH 19.15.0.0.220419

33808367 OJVM RELEASE UPDATE 19.15.0.0.0

33810130 JDK 1.8.0_331 JDK BUNDLE PATCH 19.0.0.0.220419

33912872 DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 - LIBEXPAT Need to check if it will cause conflict like Jan
UPDATE) 2022
Misc Notes and Comments

Applied
Patches ===============
DB Patch Report
===============

OPatch Version: 12.2.0.1.30

OPatch succeeded.

33810130;JDK BUNDLE PATCH 19.0.0.0.220419


33808367;OJVM RELEASE UPDATE: 19.15.0.0.220419 (33808367)
33829175;Windows Database Bundle Patch : 19.15.0.0.220419 (33829175)

===================
Check Perl version
===================
ECHO is off.
cd /d D:\ORACLE\1970\perl\bin

This is perl 5, version 28, subversion 1 (v5.28.1) built for MSWin32-x64-multi-thread


(with 1 registered patch, see perl -V for more detail)

Copyright 1987-2018, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on


this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

===================
Check JDK Version
===================
ECHO is off.
java version "1.8.0_331"
Java(TM) SE Runtime Environment (build 1.8.0_331-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.331-b09, mixed mode)

OPATCH
For JAN 2022 - OPATCH must be OPATCH version x.29 (Feb 2022) or Later
OPATCH x.28 has a BUG - Causes issue with rollback of JDK and PERL Patch
Perl
Patch DO NOT Apply in GRID or DB Home for Jan 2022 Patching Cycle
Jan 2022 The Perl Patch 31732095 UPDATE PERL IN 19C DATABASE ORACLE HOME TO V5.32 - has now been removed temporarily from
Jan 2022 patching cycle till a merge patch is available. This is because the Perl Patch Perl 5, version 32, subversion 0 (v5.32.0) MOS
Patch # 31732095 issued in Jan 2021 causes conflict with DB Bundle Patch Jan 2022 33575656 WINDOWS DATABASE BUNDLE
PATCH 19.14.0.0.220118
The old condition of PERL Patch should NOT be applied in GRID Home still applies.

cd /d d:\stage\31732095
%ORACLE_HOME%\opatch\opatch apply -silent
Oracle Interim Patch Installer version 12.2.0.1.28
Copyright (c) 2022, Oracle Corporation. All rights reserved.

Oracle Home : d:\oracle\1970


Central Inventory : D:\Oracle\Inventory
from :
OPatch version : 12.2.0.1.28
OUI version : 12.2.0.7.0
Log file location : d:\oracle\1970\cfgtoollogs\opatch\opatch2022-02-03_15-00-50PM_1.log

Verifying environment and performing prerequisite checks...

Conflicts/Supersets for each patch are:

Patch : 31732095

Conflict with 33575656


Conflict details:
d:\oracle\1970\perl\html\lib\Test2\EventFacet\Assert.html
d:\oracle\1970\perl\lib\Test2\EventFacet\Assert.pm
d:\oracle\1970\perl\lib\unicore\lib\Perl\Assigned.pl
d:\oracle\1970\perl\lib\Pod\Simple\DumpAsXML.pm
d:\oracle\1970\perl\lib\Pod\Simple\DumpAsText.pm
d:\oracle\1970\perl\site\lib\DBD\Oracle\Troubleshooting\Linux.pod
d:\oracle\1970\perl\html\lib\Pod\Simple\DumpAsText.html
d:\oracle\1970\perl\html\lib\Pod\Simple\DumpAsXML.html

Following patches have conflicts: [ 31732095 33575656 ]


Use the MOS Patch Conflict Checker "https://support.oracle.com/epmos/faces/PatchConflictCheck" to
resolve.
See MOS documents 1941934.1 and 1299688.1 for additional information and resolution methods.

UtilSession failed: Inter-conflict checking failed in apply incoming patches


Log file location: d:\oracle\1970\cfgtoollogs\opatch\opatch2022-02-03_15-00-50PM_1.log

OPatch failed with error code = 73

January 2022 (DB Layer)


Document Status

Image Legends

Patch Release Status All Patches have been Released in MOS


Deployment Status
These patches have been superseded and no longer applicable.
Apply ONLY if required specifically for restore / recovery of environments to this level
The patches have been released in MOS and internally tested ONLY for documentation purposes.
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released January 2022

Critical Patch Update (CPU) Program Jan 2022 Patch Availability Document (PAD) (Doc ID 2817011.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 01-Feb-22 - Initial Draft

03-Feb-22 - Opatch Issues when rolling back JDK & PERL - See comments

06-Feb-22 - Internal LAB Testing complete

09-Mar-22 - Approval (Doc ID 2189898.1)

22-May-22 - Superseded by April 2022 Release

Patch# Details Comments

6880880 OPatch 12.2.0.1.29 for DB 19.0.0.0.0 (Feb 2022) Feb 2022 or Later

33575656 WINDOWS DATABASE BUNDLE PATCH 19.14.0.0.220118

33561310 OJVM RELEASE UPDATE 19.14.0.0.0

33497160 JDK 1.8.0_311 JDK BUNDLE PATCH 19.0.0.0.220118

Misc Notes and Comments


Applied
Patches ===============
DB Patch Report
===============

Check OPATCH Version

OPatch Version: 12.2.0.1.29

Check OPATCH lspatches

33497160;JDK BUNDLE PATCH 19.0.0.0.220118


33561310;OJVM RELEASE UPDATE: 19.14.0.0.220118 (33561310)
33575656;Windows Database Bundle Patch : 19.14.0.0.220118 (33575656)

Check Perl version

cd /d D:\ORACLE\1970\perl\bin

This is perl 5, version 28, subversion 1 (v5.28.1) built for MSWin32-x64-multi-thread


(with 1 registered patch, see perl -V for more detail)

Copyright 1987-2018, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on


this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

Check JDK 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)

OPATCH
For JAN 2022 - OPATCH must be OPATCH version x.29 (Feb 2022) or Later
OPATCH x.28 has a BUG - Causes issue with rollback of JDK and PERL Patch
Perl
Patch DO NOT Apply in GRID or DB Home for Jan 2022 Patching Cycle
Jan 2022 The Perl Patch 31732095 UPDATE PERL IN 19C DATABASE ORACLE HOME TO V5.32 - has now been removed temporarily from
Jan 2022 patching cycle till a merge patch is available. This is because the Perl Patch Perl 5, version 32, subversion 0 (v5.32.0) MOS
Patch # 31732095 issued in Jan 2021 causes conflict with DB Bundle Patch Jan 2022 33575656 WINDOWS DATABASE BUNDLE
PATCH 19.14.0.0.220118
The old condition of PERL Patch should NOT be applied in GRID Home still applies.

cd /d d:\stage\31732095
%ORACLE_HOME%\opatch\opatch apply -silent
Oracle Interim Patch Installer version 12.2.0.1.28
Copyright (c) 2022, Oracle Corporation. All rights reserved.

Oracle Home : d:\oracle\1970


Central Inventory : D:\Oracle\Inventory
from :
OPatch version : 12.2.0.1.28
OUI version : 12.2.0.7.0
Log file location : d:\oracle\1970\cfgtoollogs\opatch\opatch2022-02-03_15-00-50PM_1.log

Verifying environment and performing prerequisite checks...

Conflicts/Supersets for each patch are:

Patch : 31732095

Conflict with 33575656


Conflict details:
d:\oracle\1970\perl\html\lib\Test2\EventFacet\Assert.html
d:\oracle\1970\perl\lib\Test2\EventFacet\Assert.pm
d:\oracle\1970\perl\lib\unicore\lib\Perl\Assigned.pl
d:\oracle\1970\perl\lib\Pod\Simple\DumpAsXML.pm
d:\oracle\1970\perl\lib\Pod\Simple\DumpAsText.pm
d:\oracle\1970\perl\site\lib\DBD\Oracle\Troubleshooting\Linux.pod
d:\oracle\1970\perl\html\lib\Pod\Simple\DumpAsText.html
d:\oracle\1970\perl\html\lib\Pod\Simple\DumpAsXML.html

Following patches have conflicts: [ 31732095 33575656 ]


Use the MOS Patch Conflict Checker "https://support.oracle.com/epmos/faces/PatchConflictCheck" to
resolve.
See MOS documents 1941934.1 and 1299688.1 for additional information and resolution methods.

UtilSession failed: Inter-conflict checking failed in apply incoming patches


Log file location: d:\oracle\1970\cfgtoollogs\opatch\opatch2022-02-03_15-00-50PM_1.log

OPatch failed with error code = 73

October 2021 (DB Layer)


Document Status

Image Legends

Patch Release Status All Patches have been Released in MOS


Deployment Status
These patches have been superseded and no longer applicable.
Apply ONLY if required specifically for restore / recovery of environments to this level
The patches have been released in MOS and internally tested ONLY for documentation purposes.
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released October 2021

Critical Patch Update (CPU) Program Oct 2021 Patch Availability Document (PAD) (Doc ID 2796575.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 23-Nov - Initial Draft

25-Nov - Approval (Doc ID 2189898.1)

09-Mar-22 Superseded by Jan 2022 - (Doc ID 2189898.1)

Patch# Details Comments

6880880 OPatch 12.2.0.1.28 for DB Nov 2021 or Later


19.0.0.0.0 (Nov 2021)

33155330 WINDOWS DATABASE Must use OPATCH .28 or later


BUNDLE PATCH
19.13.0.0.211019

33192694 OJVM RELEASE UPDATE Issue noted when Datapatch -verbose Rollback of Default Media V1001407-01 OJVM April 2020 -
19.13.0.0.0 Patch 30805684 rollback to apply July 2021 OJVM patch - Solution Re-run the Datapatch

33197296 JDK BUNDLE PATCH


19.0.0.0.211019

31732095 UPDATE PERL IN 19C Do Not Apply in GRID Home - Causes issues see readme for details
DATABASE ORACLE HOME
TO V5.32

July 2021 (DB Layer)


Document Status

Image Legends

Patch Release Status All Patches have been Released in MOS

Deployment Status
These patches have been superseded and no longer applicable.
Apply ONLY if required specifically for restore / recovery of environments to this level
The patches have been released in MOS and internally tested ONLY for documentation purposes.
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released July 2021

Critical Patch Update (CPU) Program Jul 2021 Patch Availability Document (PAD) (Doc ID 2773670.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names
Update History 03-Aug - Initial Draft

18-Aug - Approval validation Doc ID 2189898.1

Patch# Details Comments

6880880 OPatch 12.2.0.1.27 for DB 12.x, 18.x, 19.x, Aug 2021 or Later
20.x and 21.x releases (Aug 2021)

32832237 WINDOWS DATABASE BUNDLE PATCH Must use OPATCH .25 or later
19.12.0.0.210720

32876380 OJVM RELEASE UPDATE Issue noted when Datapatch -verbose Rollback of Default Media V1001407-01 OJVM
19.12.0.0.210720 April 2020 - Patch 30805684 rollback to apply July 2021 OJVM patch

Patch 30805684 rollback: WITH ERRORS


logfile: D:\Oracle\cfgtoollogs\sqlpatch\30805684\23504850
/30805684_rollback_OPERA_2021Aug31_07_58_09.log (errors)
-> Error at line 44: script javavm/install/jvmpsupdi.sql
- ORA-04068: existing state of packages has been discarded
- ORA-04061: existing state of has been invalidated
- ORA-04061: existing state of package body "SYS.
DBMS_REGISTRY_SYS" has been
- invalidated
- ORA-04065: not executed, altered or dropped package body
- "SYS.DBMS_REGISTRY_SYS"
- ORA-06508: PL/SQL: could not find program unit being
called:
- "SYS.DBMS_REGISTRY_SYS"
- ORA-06512: at "SYS.DBMS_REGISTRY", line 2859
- ORA-06512: at line 5
-> Error at line 67: script javavm/install/jvmpsupdi.sql
- SP2-0556: Invalid file name.
Patch 32832237 apply: SUCCESS
logfile: D:\Oracle\cfgtoollogs\sqlpatch\32832237\24292339
/32832237_apply_OPERA_2021Aug31_08_00_42.log (no errors)
Patch 32876380 apply: SUCCESS
logfile: D:\Oracle\cfgtoollogs\sqlpatch\32876380\24382230
/32876380_apply_OPERA_2021Aug31_07_58_10.log (no errors)

Solution:

Re-run datapatch -verbose

32918394 JDK 8u301 JDK BUNDLE PATCH


19.0.0.0.210720

31732095 UPDATE PERL IN 19C DATABASE Do Not Apply in GRID Home - Causes issues see readme for details
ORACLE HOME TO V5.32

Apr 2021 (DB Layer)


Document Status

Image Legends

Patch Release Status All Patches have been Released in MOS


Deployment Status
These patches have been superseded and no longer applicable.
Apply ONLY if required specifically for restore / recovery of environments to this level
The patches have been released in MOS and being internally tested ONLY for documentation purposes.
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released April 2021

Critical Patch Update (CPU) Program Apr 2021 Patch Availability Document (PAD) (Doc ID 2749094.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 21-Apr - Initial Draft

10-Jun - Approval validation Doc ID 2189898.1

Patch# Details Comments

6880880 OPatch 12.2.0.1.24 for Db 12.x, 18.x, 19.x and 20.x Feb 2021 or Later
releases (Windows X64)

32409154 WINDOWS DATABASE BUNDLE PATCH Encountered Issue during Patching Oct 2020 - BUG 32193918 - Issue resolved -
19.11.0.0.210420 requires INIT / SPFILE updates)

32399816 OJVM RELEASE UPDATE 19.11.0.0.0

32490416 JDK 1.8.0_291 JDK BUNDLE PATCH 19.0.0.0.210420

31732095 UPDATE PERL IN 19C DATABASE ORACLE HOME Do Not Apply in GRID Home - Causes issues see readme for details
TO V5.32

Jan 2021 (DB Layer)


Document Status

Image Legends

Patch Release Status All Patches have been Released in MOS

Deployment Status
These patches have been superseded and no longer applicable.
Apply ONLY if required specifically for restore / recovery of environments to this level
The patches have been released in MOS and internally tested ONLY for documentation purposes.
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released January 2021

Critical Patch Update (CPU) Program Jan 2021 Patch Availability Document (PAD) (Doc ID 2694898.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Oracle Database 19c Release Update & Release Update Revision January 2021 Critical Issues (Doc ID 2725758.1)

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names
Update History 09-Mar - Initial Draft

09-Mar - Approval validation Doc ID 2189898.1

10-Jun - Apr 2021 Approval validation Doc ID 2189898.1

Patch# Details Comments

6880880 OPatch 12.2.0.1.23 for DB 19.x releases (Nov ** Important - MUST use 12.2.0.1.23 or Higher
2020)

32062765 WINDOWS DATABASE BUNDLE PATCH Encountered Issue during Patching Oct 2020 - BUG 32193918 - Issue resolved -
19.10.0.0.210119 requires INIT / SPFILE updates)

32067171 WINDOWS ORACLE OJVM RELEASE


UPDATE 19.10.0.0.0

32162391 JDK 1.8.0_281 BUNDLE PATCH


19.0.0.0.210119

31732095 UPDATE PERL IN 19C DATABASE ORACLE Do Not Apply in GRID Home - Causes issues see readme for details
HOME TO V5.32

April 2020 (DB Layer)


Document Status

Image Legends

Patch Release Status All Patches have been released in MOS

Deployment Status
These patches have been superseded and no longer applicable.
Apply ONLY if required specifically for restore / recovery of environments to this level
The patches have been released in MOS and internally tested ONLY for documentation purposes.
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY
April 2020 is the default patch level for 19c DB Media

Source https://www.oracle.com/security-alerts/cpuapr2020.html

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Patch# Details Comments

6880880 OPatch 12.2.0.1.21 for DB 19.x releases (Apr 2020)

30901317 WINDOWS DATABASE BUNDLE PATCH


19.7.0.0.200414

30805684 OJVM RELEASE UPDATE 19.7.0.0.0


19.7.0.0.200414

July 2020 (DB Layer)


Document Status

Image Legends

Patch Release Status All Patches have been Released in MOS

Deployment Status
These patches have been superseded and no longer applicable.
Apply ONLY if required specifically for restore / recovery of environments to this level
The patches have been released in MOS and internally tested ONLY for documentation purposes.
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source https://www.oracle.com/security-alerts/cpujul2020.html

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Patch# Details Comments

6880880 OPatch 12.2.0.1.21 for DB 19.x releases (Apr 2020)

31247621 WINDOWS DB BUNDLE PATCH 19.8.0.0.0.200714

31219897 WINDOWS ORACLE OJVM RELEASE UPDATE


19.8.0.0.0

October 2020 (DB Layer)


Document Status

Image Legends

Patch Release Status All Patches have been Released in MOS

Deployment Status
These patches have been superseded and no longer applicable.
Apply ONLY if required specifically for restore / recovery of environments to this level
The patches have been released in MOS and internally tested ONLY for documentation purposes.
Did not test or check any vulnerabilities or do any regression/performance or stability testing
19.x Applies to OPERA 5.6.11 and Above ONLY

Source CPU Alerts Released October 2020

Critical Patch Update (CPU) Program Oct 2020 Patch Availability Document (PAD) (Doc ID 2694898.1)

JDK and PERL Patches for Oracle Database Home and Grid Home (Doc ID 2584628.1)

Oracle Database 19c Release Update & Release Update Revision October 2020 Known Issues (Doc ID 2694903.1)

Validation Oracle Security Releases for Oracle Hospitality OPERA - R&D Based Testing Results Only (Doc ID 2189898.1)

Miscellaneous When extracting - please use 7zip - Windows internal Zip has issued with long file names

Update History 04-Nov - Initial Draft

23-Nov - Approval validation Doc ID 2189898.1

06-Jan - Patching issue resolved

10-Jun - Apr 2021 Approval validation Doc ID 2189898.1


Patch# Details Comments

6880880 OPatch 12.2.0.1.23 for DB 19.x releases (Nov ** Important - MUST use 12.2.0.1.23 or Higher
2020)

31719903 WINDOWS DB BUNDLE PATCH 19.9.0.0.201020 Encountered Issue during Patching Oct 2020 - BUG 32193918 - Issue resolved -
requires INIT / SPFILE updates)

31668882 WINDOWS ORACLE OJVM RELEASE UPDATE


19.9.0.0.201020

31743771 JDK 1.8.0_201 BUNDLE PATCH 19.0.0.0.201020

29511711 UPDATE PERL 5.28.1 IN 19.3.0.0.0 DATABASE Not required as it is included in default media since 19.3.0.0.
ORACLE HOME

Pre Patching Tasks


Validate Init.ORA / SPFILE file Changes
Depending on what is in use - make and keep copy of the spfileXXXX / initXXXX.ora file

Open initXXXX.ora file with notepad and change the following values - Edit the values below and save the document – make sure to choose and enable
correct memory parameters.

or use DB commands if using SPFILE

Modify INIT Parameters for the upgrade to complete successfully.

These can be enabled BACK post Backup

Media Default INIT / SP File Custom Tweksed INIT / SP File

if MEDIA Defalt INIT/SPFILE is in use ensure the following if Custom INIT / SPFILE is in use ensure the following parameters are NOT Set
parameters are NOT Set
Remove the below parameters BEFORE Upgrade
Remove the below parameters BEFORE Upgrade
deferred_segment_creation=false # for using exp/imp
*._optim_peek_user_binds=FALSE plsql_optimize_level=1 # fix for plsql table to return
*.utl_file_dir='*' ### This Parameter correct results, pending Oracle bug fix
is no longer applicable in 19c _optim_peek_user_binds=FALSE
*.plsql_optimize_level=1
*.deferred_segment_creation=FALSE _kill_enqueue_blocker=1
_optimizer_complex_pred_selectivity=false
_enable_shared_pool_durations=FALSE

utl_file_dir='*'

Update below parameters BEFORE Upgrade

Validate Values

job_queue_processes=0

aq_tm_processes=0

Compatible=19.0.0

shared_pool_reserved_size = 6553600

Install VC_Redist.x64 2015, 2017, 2019 and 2022


Install Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019 and 2022
Verify if already installed

Download and install the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019 and 2022 from below and install

Microsoft website

Direct Download

Install the EXE

Verify afgain if installed


Set DB Home

Warning

When Patching Make sure to use the correct ORACLE_HOME and ORACLE_SID wherever and whenever required.

Set Environment
set ORACLE_HOME=D:\ORACLE\1970

set ORACLE_SID=opera

set PERL5LIB=

set perlpath=

set PATH=D:\ORACLE\1970\bin;D:\ORACLE\1970\perl\bin;%PATH%

Make sure the WINDOWS PATH also includes the ORACLE_HOME - AS FIRST ENTRY

Also ensure the perl paths variables are NOT Set in WINDOWS Environment variables

Execute below to verify

echo %ORACLE_HOME%

echo %ORACLE_SID%

echo %path%

echo %PERL5LIB%

echo %perlpath%
Enable SQLNET / OS Authentication
Connect to the database and validate OS Authentication

Ensure User is member of Administrators and ORA_DBA group in windows.

Ensure SQLNET.ora has the following values setup

SQLNET.AUTHENTICATION_SERVICES = (NTS)

Now connect SQLPLUS connect and check If connection is successful.

sqlplus / as sysdba

Set Instance Manual


cd /D %ORACLE_HOME%\database

oradim -edit -sid opera -startmode m

Services / Environment
Stop all Database and APPS (If they exist) related Services

At this point the Downtime has started

STOP services WMI/MDTC


net stop msdtc
net stop winmgmt /y

taskkill /F /IM java.exe


taskkill /F /IM jucheck.exe
taskkill /F /IM jusched.exe
taskkill /F /IM javaw.exe
taskkill /F /IM emagent.exe
taskkill /F /IM httpd.exe
taskkill /F /IM rwserver.exe
taskkill /F /IM apache.exe
taskkill /F /IM tnslsnr.exe
taskkill /F /IM oracle.exe
taskkill /F /IM perl.exe
taskkill /F /IM extproc.exe
taskkill /F /IM rman.exe
taskkill /F /IM sqlplus.exe

taskkill /F /IM java.exe


taskkill /F /IM jucheck.exe
taskkill /F /IM jusched.exe
taskkill /F /IM javaw.exe
taskkill /F /IM emagent.exe
taskkill /F /IM httpd.exe
taskkill /F /IM rwserver.exe
taskkill /F /IM apache.exe
taskkill /F /IM tnslsnr.exe
taskkill /F /IM oracle.exe
taskkill /F /IM perl.exe
taskkill /F /IM extproc.exe
taskkill /F /IM rman.exe
taskkill /F /IM sqlplus.exe

Rollback Previous Applied OJVM, JDK & Perl


Remove/Rename the Temp newdirs.txt

Remove/Rename the temp newdirs.txt_tmp file (If it exists)


Go and verify %ORACLE_HOME%\.patch_storage\newdirs.txt_tmp file exists

after below a copy will be made and it will be deleted.

cd /d %ORACLE_HOME%\.patch_storage

copy newdirs.txt_tmp newdirs.txt_tmp_Prerollback_OJVM_PreviousPatch /y

del newdirs.txt_tmp /q

Rollback OJVM from RDBMS Oracle Home

Identify the OJVM Patch Applied for Rollback

%ORACLE_HOME%\opatch\opatch lspatches | findstr ;OJVM


Once the OJVM patch number has been identified ROLL it back

Update CHANGEME to the Patch number Identified above

%ORACLE_HOME%\opatch\opatch lspatches | findstr "CHANGEME"

%ORACLE_HOME%\opatch\opatch rollback -id CHANGEME -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "CHANGEME"

Example:
OJVM Patch 35648110 has been identified for rollback based on above screenshot (It may differ on site)

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35648110"

%ORACLE_HOME%\opatch\opatch rollback -id 35648110 -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35648110"

Verify OJVM has been rolled back sucessfully

%ORACLE_HOME%\opatch\opatch lspatches

After rollback there should be NO ERRORS in OPATCH

Rollback JDK from RDBMS Oracle Home

Identify the JDK Patch Applied for Rollback

%ORACLE_HOME%\opatch\opatch lspatches | findstr ;JDK

Once the JDK patch number has been identified ROLL it back

Update CHANGEME to the Patch number Identified above

%ORACLE_HOME%\opatch\opatch lspatches | findstr "CHANGEME"

%ORACLE_HOME%\opatch\opatch rollback -id CHANGEME -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "CHANGEME"

Example:
JDK Patch 35638318 has been identified for rollback based on above screenshot (It may differ on site)
%ORACLE_HOME%\opatch\opatch lspatches | findstr "35638318"

%ORACLE_HOME%\opatch\opatch rollback -id 35648110 -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35638318"

Verify JDK has been rolled back sucessfully

%ORACLE_HOME%\opatch\opatch lspatches

After rollback there should be NO ERRORS in OPATCH

(If Rollback JDK Causes Issues with missing file error - normally seen with Oct 2021 - 33197296)
Remove/Rename the temp newdirs.txt_tmp file
Normally this is seen with Oct 2021 JDK Patch
Go and verify %ORACLE_HOME%\.patch_storage\newdirs.txt_tmp file exists

after below a copy will be made and it will be deleted.

cd /d %ORACLE_HOME%\.patch_storage

copy newdirs.txt_tmp newdirs.txt_tmp_Prerollback_bkp /y

del newdirs.txt_tmp /q

Unzip the JDK Rollback Zip file

cd /d %ORACLE_HOME%\.patch_storage\33197296_Oct_12_2021_10_04_34\files

unzip jdk.zip

cd /d %ORACLE_HOME%\opatch

Rollback Oct 2021 JDK Patch 33197296

%ORACLE_HOME%\opatch\opatch lspatches | findstr "33197296"

%ORACLE_HOME%\opatch\opatch rollback -id 33197296 -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "33197296"

Enter Y to proceed with patching – then other options


Verify the patch has been rolled back
If it has been applied it will show result.

Remove/Rename the temp newdirs.txt_tmp file (If it exists)


Go and verify %ORACLE_HOME%\.patch_storage\newdirs.txt_tmp file exists

after below a copy will be made and it will be deleted.


cd /d %ORACLE_HOME%\.patch_storage

copy newdirs.txt_tmp newdirs.txt_tmp_Postrollback_bkp /y

del newdirs.txt_tmp /q

cd /d %ORACLE_HOME%\opatch

Rollback Perl from Oracle Home

Identify the Perl Patch Applied for Rollback

%ORACLE_HOME%\opatch\opatch lspatches | findstr "33912872 31732095"

Once the Perl Patch 33912872 31732095 has been identified that it exists ROLL it back

If NO PERL Patch is applied move on to NEXT section

Rollback 33912872 if it exists

%ORACLE_HOME%\opatch\opatch lspatches | findstr "33912872"

%ORACLE_HOME%\opatch\opatch rollback -id CHANGEME -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "33912872"

Rollback 31732095 if it exists

%ORACLE_HOME%\opatch\opatch lspatches | findstr "31732095"

%ORACLE_HOME%\opatch\opatch rollback -id CHANGEME -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "31732095"

Verify Perl has been rolled back sucessfully

%ORACLE_HOME%\opatch\opatch lspatches

After rollback there should be NO ERRORS in OPATCH

(If Rollback Perl Causes Issues with missing file error - normally seen with 31732095)
Remove/Rename the temp newdirs.txt_tmp file (If it exists)
Go and verify %ORACLE_HOME%\.patch_storage\newdirs.txt_tmp file exists

after below a copy will be made and it will be deleted.

cd /d %ORACLE_HOME%\.patch_storage

copy newdirs.txt_tmp newdirs.txt_tmp_Prerollback_BKP /y

del newdirs.txt_tmp /q

Unzip the Perl Rollback Zip file


cd /d %ORACLE_HOME%\.patch_storage\31732095_Jan_20_2021_15_51_16\files

unzip perl.zip

cd /d %ORACLE_HOME%\opatch

Rollback Oct 2021 PERL Patch 31732095

%ORACLE_HOME%\opatch\opatch lspatches | findstr "31732095"

%ORACLE_HOME%\opatch\opatch rollback -id 31732095 -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "31732095"

Enter Y to proceed with patching – then other options


Verify the patch has been rolled back
If it has been applied it will show result.

Remove/Rename the temp newdirs.txt_tmp file (If it exists)


Go and verify %ORACLE_HOME%\.patch_storage\newdirs.txt_tmp file exists

after below a copy will be made and it will be deleted.

cd /d %ORACLE_HOME%\.patch_storage

copy newdirs.txt_tmp newdirs.txt_tmp_Postrollback_31732095_BKP /y

del newdirs.txt_tmp /q

cd /d %ORACLE_HOME%\opatch

Verify OJVM, JDK and PERL - DOES NOT Exist in RDBMS Oracle Home
%ORACLE_HOME%\opatch\opatch lspatches

Upgrade 19.x Binary to latest Critical Patch


Set DB Home

Warning

When Patching Make sure to use the correct ORACLE_HOME and ORACLE_SID wherever and whenever required.

Set Environment
set ORACLE_HOME=D:\ORACLE\1970

set ORACLE_SID=opera

set PERL5LIB=

set perlpath=

set PATH=D:\ORACLE\1970\bin;D:\ORACLE\1970\perl\bin;%PATH%

Make sure the WINDOWS PATH also includes the ORACLE_HOME - AS FIRST ENTRY

Also ensure the perl paths variables are NOT Set in WINDOWS Environment variables

Execute below to verify

echo %ORACLE_HOME%

echo %ORACLE_SID%

echo %path%

echo %PERL5LIB%

echo %perlpath%

Stop Services
Stop all Database and APPS (If they exist) related Services
net stop msdtc
net stop winmgmt /y

taskkill /F /IM java.exe


taskkill /F /IM jucheck.exe
taskkill /F /IM jusched.exe
taskkill /F /IM javaw.exe
taskkill /F /IM emagent.exe
taskkill /F /IM httpd.exe
taskkill /F /IM rwserver.exe
taskkill /F /IM apache.exe
taskkill /F /IM tnslsnr.exe
taskkill /F /IM oracle.exe
taskkill /F /IM perl.exe
taskkill /F /IM extproc.exe
taskkill /F /IM rman.exe
taskkill /F /IM sqlplus.exe

taskkill /F /IM java.exe


taskkill /F /IM jucheck.exe
taskkill /F /IM jusched.exe
taskkill /F /IM javaw.exe
taskkill /F /IM emagent.exe
taskkill /F /IM httpd.exe
taskkill /F /IM rwserver.exe
taskkill /F /IM apache.exe
taskkill /F /IM tnslsnr.exe
taskkill /F /IM oracle.exe
taskkill /F /IM perl.exe
taskkill /F /IM extproc.exe
taskkill /F /IM rman.exe
taskkill /F /IM sqlplus.exe

Upgrade Opatch to Latest for DB 19c

Important - MUST use Latest OPATCH as recommended in Patches - else will fail.

Ensure you have set Variables for ORACLE_HOME and ORACLE_SID

CD /D %ORACLE_HOME%\bin

Verify OPATCH version

%ORACLE_HOME%\opatch\opatch version

rename existing OPATCH folder - rename %ORACLE_HOME%\OPatch to %ORACLE_HOME%\OPatch_OLD

copy the D:\Stage\6880880\Opatch folder to %ORACLE_HOME%\OPatch

verify OPATCH version

%ORACLE_HOME%\opatch\opatch version

Result should show latest OPatch number


Apply DB, OJVM , JDK and PERL Patches for DB 19c

Apply Patch 36878821 WINDOWS DATABASE BUNDLE PATCH 19.25.0.0.241015 WIN BP


CD /D D:\stage\36878821

%ORACLE_HOME%\opatch\opatch lspatches | findstr "36878821"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "36878821"

If it has been applied it will show result

Apply Patch 36878697 OJVM RELEASE UPDATE 19.25.0.0.241015 OJVM RU


CD /D D:\stage\36878697

%oracle_home%\opatch\Opatch lspatches | findstr "36878697"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "36878697"

If it has been applied it will show result.

Apply Patch 36866578 JDK 8u431 JDK BUNDLE PATCH 19.0.0.0.241015


CD /D D:\stage\36866578

%oracle_home%\opatch\Opatch lspatches | findstr "36866578"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "36866578"

If it has been applied it will show result.

Validate the Applied Patches, JDK & Perl


Numbers may differ depending on period/patches

%ORACLE_HOME%\opatch\Opatch version

%ORACLE_HOME%\opatch\Opatch lspatches

It will display the OPATCH Version and Patches applied (Screenshots Numbers may differ)
%ORACLE_HOME%\opatch\Opatch lsinventory | findstr “36260493”

%ORACLE_HOME%\opatch\Opatch lsinventory | findstr “36260537”

Will display the TIMEZONE43 and OJVMFix for Timezone 43 Patches

%ORACLE_HOME%\perl\bin\perl -version

cd /d %ORACLE_HOME%\jdk\bin

java -version

Will display the PERL and JDK versions

If it has been applied it will show result.

Apply Patch 36521936 WINDOWS DATABASE BUNDLE PATCH 19.24.0.0.240716 WIN BP


CD /D D:\stage\36521936

%ORACLE_HOME%\opatch\opatch lspatches | findstr "36521936"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "36521936"


If it has been applied it will show result

Apply Patch 36414915 OJVM RELEASE UPDATE 19.24.0.0.240716 OJVM RU


CD /D D:\stage\36414915

%oracle_home%\opatch\Opatch lspatches | findstr "36414915"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "36414915"

If it has been applied it will show result.

Apply Patch 36538667 JDK 8u421 JDK BUNDLE PATCH 19.0.0.0.240716


CD /D D:\stage\36538667

%oracle_home%\opatch\Opatch lspatches | findstr "36538667"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "36538667"

If it has been applied it will show result.

Validate the Applied Patches, JDK & Perl


Numbers may differ depending on period/patches

%ORACLE_HOME%\opatch\Opatch version

%ORACLE_HOME%\opatch\Opatch lspatches

It will display the OPATCH Version and Patches applied

%ORACLE_HOME%\opatch\Opatch lsinventory | findstr “36260493”

%ORACLE_HOME%\opatch\Opatch lsinventory | findstr “36260537”

Will display the TIMEZONE43 and OJVMFix for Timezone 43 Patches


%ORACLE_HOME%\perl\bin\perl -version

cd /d %ORACLE_HOME%\jdk\bin

java -version

Will display the PERL and JDK versions

If it has been applied it will show result.

Apply Patch 36260493 RDBMS - DSTV43 UPDATE - TZDATA2024A


CD /D D:\stage\36260493

%ORACLE_HOME%\opatch\opatch lspatches | findstr "36260493"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "36260493"

If it has been applied it will show result.

Apply Patch 36260537 DSTV43 UPDATE - TZDATA2024A - NEED OJVM FIX


CD /D D:\stage\36260537

%ORACLE_HOME%\opatch\opatch lspatches | findstr "36260537"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "36260537"

If it has been applied it will show result.

Apply Patch 36219938 WINDOWS DATABASE BUNDLE PATCH 19.23.0.0.240416 WIN BP


CD /D D:\stage\36219938

%ORACLE_HOME%\opatch\opatch lspatches | findstr "36219938"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "36219938"

If it has been applied it will show result

Apply Patch 36199232 OJVM RELEASE UPDATE 19.23.0.0.240416 OJVM RU


CD /D D:\stage\36199232

%oracle_home%\opatch\Opatch lspatches | findstr "36199232"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "36199232"

If it has been applied it will show result.

Apply Patch 36195566 JDK 8u411 JDK BUNDLE PATCH 19.0.0.0.240416


CD /D D:\stage\36195566

%oracle_home%\opatch\Opatch lspatches | findstr "36195566"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "36195566"

If it has been applied it will show result.

Apply Perl Patch (Post Jan 2023)

Beginning from Jan 2023, Perl updates are included within the quarterly DB Bundle patches Doc ID 2584628.1)

Validate the Applied Patches, JDK & Perl


%ORACLE_HOME%\opatch\Opatch version

%ORACLE_HOME%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

cd /d %ORACLE_HOME%\jdk\bin

java -version

If it has been applied it will show result.


Apply Patch 35220732 RDBMS - DSTV42 UPDATE - TZDATA2023C
CD /D D:\stage\35220732

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35220732"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35220732"

If it has been applied it will show result.

Apply Patch 35239280 DSTV42 UPDATE - TZDATA2023C - NEED OJVM FIX


CD /D D:\stage\35239280

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35239280"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35239280"

If it has been applied it will show result.

Apply Patch 35962832 WINDOWS DATABASE BUNDLE PATCH 19.22.0.0.240116 WIN BP


CD /D D:\stage\35962832

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35962832"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35962832"

If it has been applied it will show result.

Apply Patch 35926646 OJVM RELEASE UPDATE 19.22.0.0.240116 OJVM RU


CD /D D:\stage\35926646

%oracle_home%\opatch\Opatch lspatches | findstr "35926646"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "35926646"

If it has been applied it will show result.

Apply Patch 35949090 JDK 8u401 BUNDLE PATCH 19.0.0.0.240116


CD /D D:\stage\35949090

%oracle_home%\opatch\Opatch lspatches | findstr "35949090"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "35949090"

If it has been applied it will show result.

Apply Perl Patch (Post Jan 2023)

Beginning from Jan 2023, Perl updates are included within the quarterly DB Bundle patches Doc ID 2584628.1)

Validate the Applied Patches, JDK & Perl


%ORACLE_HOME%\opatch\Opatch version

%ORACLE_HOME%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

cd /d %ORACLE_HOME%\jdk\bin

java -version

If it has been applied it will show result.

Apply Patch 35220732 RDBMS - DSTV42 UPDATE - TZDATA2023E


CD /D D:\stage\35220732

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35220732"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 35239280 DSTV42 UPDATE - TZDATA2023E - NEED OJVM FIX


CD /D D:\stage\35239280

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35239280"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.
If it has been applied it will show result.

Apply Patch 35681552 WINDOWS DATABASE BUNDLE PATCH 19.21.0.0.231017


CD /D D:\stage\35681552

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35681552"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 35648110 OJVM RELEASE UPDATE 19.21.0.0.231017

CD /D D:\stage\35648110

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "35648110"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 35638318 JDK8u391 BUNDLE PATCH 19.21.0.0.231017

Apply Patch 35638318 JDK8u391 BUNDLE PATCH 19.21.0.0.231017

CD /D D:\stage\35638318

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "35638318"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Perl Patch Oct 2023


Beginning from Jan 2023, Perl updates are included within the quarterly DB Bundle patches Doc ID 2584628.1)

Validate the Applied Patches, JDK & Perl


%ORACLE_HOME%\opatch\Opatch version

%ORACLE_HOME%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

%ORACLE_HOME%\jdk\bin\java -version

Will Display Output

Apply Patch 35220732 RDBMS - DSTV42 UPDATE - TZDATA2023E


CD /D D:\stage\35220732

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35220732"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 35239280 DSTV42 UPDATE - TZDATA2023E - NEED OJVM FIX


CD /D D:\stage\35239280

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35239280"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 35348034 WINDOWS DATABASE BUNDLE PATCH 19.20.0.0.230718


CD /D D:\stage\35348034

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35348034"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 35354406 OJVM RELEASE UPDATE 19.20.0.0.230718


CD /D D:\stage\35354406

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "35354406"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 35336174 JDK8u381 BUNDLE PATCH 19.0.0.0.230718

Apply 35336174 JDK8u381 BUNDLE PATCH 19.0.0.0.230718

CD /D D:\stage\35336174

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "35336174"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Perl Patch July 2023


Beginning from Jan 2023, Perl updates are included within the quarterly DB Bundle patches Doc ID 2584628.1)

Validate the Applied Patches, JDK & Perl


%ORACLE_HOME%\opatch\Opatch version

%ORACLE_HOME%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

%ORACLE_HOME%\jdk\bin\java -version

Will Display Output

to be added

Apply Patch 34698179 RDBMS - DSTV40 UPDATE - TZDATA2022E


CD /D D:\stage\34698179

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "34698179"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 34699616 DSTV40 UPDATE - TZDATA2022E - NEED OJVM FIX


CD /D D:\stage\34699616

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "34699616"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 35046439 WINDOWS DATABASE BUNDLE PATCH 19.19.0.0.230418


CD /D D:\stage\35046439

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "35046439"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 35050341 OJVM RELEASE UPDATE 19.19.0.0.230418

CD /D D:\stage\35050341

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "35050341"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 34894382 JDK BUNDLE PATCH 19.19.0.0.230418

Apply 35004974: JDK BUNDLE PATCH 19.0.0.0.230418


CD /D D:\stage\35004974

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "35004974"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Perl Patch Apr 2023


Beginning from Jan2023, Perl updates are included within the quarterly DB Bundle patches Doc ID 2584628.1)

Validate the Applied Patches, JDK & Perl


%ORACLE_HOME%\opatch\Opatch version

%ORACLE_HOME%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

%ORACLE_HOME%\jdk\bin\java -version

Will Display Output

to be added

Apply Patch 34698179 RDBMS - DSTV40 UPDATE - TZDATA2022E


CD /D D:\stage\34698179

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "34698179"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 34699616 DSTV40 UPDATE - TZDATA2022E - NEED OJVM FIX


CD /D D:\stage\34699616

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "34699616"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 34750795 WINDOWS DATABASE BUNDLE PATCH 19.18.0.0.230117


CD /D D:\stage\34750795

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "34750795"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 34786990 OJVM RELEASE UPDATE 19.18.0.0.230117

CD /D D:\stage\34786990

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "34786990"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 34777391 JDK BUNDLE PATCH 19.18.0.0.230117

Apply 34777391 JDK BUNDLE PATCH 19.18.0.0.230117

CD /D D:\stage\34777391

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "34777391"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.


Apply Perl Patch Jan 2023
Beginning from Jan2023, Perl updates are included within the quarterly DB Bundle patches Doc ID 2584628.1)

Validate the Applied Patches, JDK & Perl


%ORACLE_HOME%\opatch\Opatch version

%ORACLE_HOME%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

%ORACLE_HOME%\jdk\bin\java -version

Will Display Output

Check OPATCH Version


=======================
OPatch Version: 12.2.0.1.36

Check OPATCH lspatches


=======================

34777391;JDK BUNDLE PATCH 19.0.0.0.230117


34786990;OJVM RELEASE UPDATE: 19.18.0.0.230117 (34786990)
34750795;Windows Database Bundle Patch : 19.18.0.0.230117 (34750795)
34699616;DSTV40 UPDATE - TZDATA2022E - NEED OJVM FIX

Check Perl version


===================
ECHO is off.
cd /d D:\ORACLE\1970\perl\bin

This is perl 5, version 36, subversion 0 (v5.36.0) built for MSWin32-x64-multi-thread

Copyright 1987-2022, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on


this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at https://www.perl.org/, the Perl Home Page.

Check JDK Version


=======================

java version "1.8.0_361"


Java(TM) SE Runtime Environment (build 1.8.0_361-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.361-b09, mixed mode)
Apply Patch 34468114 WINDOWS DATABASE BUNDLE PATCH 19.17.0.0.221018
CD /D D:\stage\34468114

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "34468114"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 34411846 OJVM RELEASE UPDATE 19.17.0.0.0.221018

CD /D D:\stage\34411846

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "34411846"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 34422617 JDK BUNDLE PATCH 19.0.0.0.221018

Apply 34422617 JDK BUNDLE PATCH 19.0.0.0.221018

CD /D D:\stage\34422617

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "34422617"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 33912872 DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 -


LIBEXPAT UPDATE)
Perl Patch 33912872 will cause conflict with DB Bundle Patch 34468114 - if OLD Pre Relase DB Bundle 17-11-22 and before patch is used.

Apply 33912872: DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 -


LIBEXPAT UPDATE)
Why Rollback First?

We are rolling back and then re-apply same patch Perl Patch was re-released with SAME patch number

CD /D D:\stage\33912872

%oracle_home%\opatch\Opatch lspatches | findstr "33912872"

%ORACLE_HOME%\opatch\opatch rollback -id 33912872 -silent

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "33912872"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

If the below command to validate Perl causes issues - the correct Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 is missing
from OS - check in control Panel.

%ORACLE_HOME%\perl\bin\perl -version

Solution: Install - Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 in next section

Validate the Applied Patches, JDK & Perl


%ORACLE_HOME%\opatch\Opatch version

%ORACLE_HOME%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

%ORACLE_HOME%\jdk\bin\java -version

Will Display Output


Check OPATCH Version
=======================
OPatch Version: 12.2.0.1.33

Check OPATCH lspatches


=======================
33912872;DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 - LIBEXPAT UPDATE)
34422617;JDK BUNDLE PATCH 19.0.0.0.221018
34411846;OJVM RELEASE UPDATE: 19.17.0.0.221018 (34411846)
34468114;Windows Database Bundle Patch : 19.17.0.0.221018 (34468114)
32327201;RDBMS - DSTV36 UPDATE - TZDATA2020E

Check Perl version


=======================
cd /d D:\ORACLE\1970\perl\bin

This is perl 5, version 32, subversion 0 (v5.32.0) built for MSWin32-x64-multi-thread

Check JDK Version


=======================
java version "1.8.0_351"
Java(TM) SE Runtime Environment (build 1.8.0_351-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.351-b10, mixed mode)

Apply Patch 34110685 WINDOWS DATABASE BUNDLE PATCH 19.16.0.0.220719


CD /D D:\stage\34110685

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "34110685"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Patch 34086870 OJVM RELEASE UPDATE 19.16.0.0.0

CD /D D:\stage\34086870

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "34086870"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.


If it has been applied it will show result.

Apply 34113634 JDK BUNDLE PATCH 19.0.0.0.220719

Apply 34113634 JDK BUNDLE PATCH 19.0.0.0.220719

CD /D D:\stage\34113634

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "34113634"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply 33912872: DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 -


LIBEXPAT UPDATE)

Apply 33912872: DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 -


LIBEXPAT UPDATE)

Why Rollback First?

We are rolling back and then re-apply same patch Perl Patch was re-released with SAME patch number

CD /D D:\stage\33912872

%oracle_home%\opatch\Opatch lspatches | findstr "33912872"

%ORACLE_HOME%\opatch\opatch rollback -id 33912872 -silent

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "33912872"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.


If the below command to validate Perl causes issues - the correct Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 is missing
from OS - check in control Panel.

%ORACLE_HOME%\perl\bin\perl -version

Solution: Install - Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 in next section

Validate the Applied Patches, JDK & Perl


%ORACLE_HOME%\opatch\Opatch version

%ORACLE_HOME%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

%ORACLE_HOME%\jdk\bin\java -version

Will Display Output

Check OPATCH Version


=======================
OPatch Version: 12.2.0.1.32

Check OPATCH lspatches


=======================
33912872;DATABASE PERL UPDATE IN 19C TO V5.32-1 (CVE-2022-23990 - LIBEXPAT UPDATE)
34113634;JDK BUNDLE PATCH 19.0.0.0.220719
34086870;OJVM RELEASE UPDATE: 19.16.0.0.220719 (34086870)
34110685;Windows Database Bundle Patch : 19.16.0.0.220719 (34110685)

Check Perl version


=======================
This is perl 5, version 32, subversion 0 (v5.32.0) built for MSWin32-x64-multi-thread

Check JDK Version


=======================
java version "1.8.0_341"
Java(TM) SE Runtime Environment (build 1.8.0_341-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.341-b10, mixed mode)

Apply Apr 2022 - Patch 33829175 WINDOWS DATABASE BUNDLE PATCH 19.15.0.0.220419
CD /D D:\stage\33829175

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "33829175"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Apr 2022 - Patch 33808367 OJVM RELEASE UPDATE 19.15.0.0.0

CD /D D:\stage\33808367

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "33808367"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Apr 2022 - Patch 33810130 : JDK 1.8.0_331 JDK BUNDLE PATCH 19.0.0.0.220419

Apply Apr 2022 - Patch 33810130 : JDK 1.8.0_331 JDK BUNDLE PATCH 19.0.0.0.220419

CD /D D:\stage\33810130

%oracle_home%\opatch\Opatch lspatches | findstr "33810130"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "33810130"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Validate the Applied Patches, JDK & Perl

%oracle_home%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

%ORACLE_HOME%\jdk\bin\java -version
Apply Jan 2022 - Patch 33575656 WINDOWS DATABASE BUNDLE PATCH 19.14.0.0.220118

CD /D D:\stage\33575656

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "33575656"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Jan 2022 - Patch 33561310 OJVM RELEASE UPDATE 19.14.0.0.0

CD /D D:\stage\33561310

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "33561310"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Jan 2022 - Patch 33497160 : JDK 1.8.0_311 JDK BUNDLE PATCH 19.0.0.0.220118

Apply Jan 2022 - Patch 33497160 : JDK 1.8.0_311 JDK BUNDLE PATCH 19.0.0.0.220118

CD /D D:\stage\33497160

%oracle_home%\opatch\Opatch lspatches | findstr "33497160"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "33497160"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Validate the Applied Patches, JDK & Perl


%oracle_home%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

%ORACLE_HOME%\jdk\bin\java -version

Apply Oct 2021 - Patch 33155330 WINDOWS DATABASE BUNDLE PATCH 19.13.0.0.211019
CD /D D:\stage\33155330
%ORACLE_HOME%\opatch\opatch lspatches | findstr "33155330"

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "33155330"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Oct 2021 - Patch 33192694 OJVM RELEASE UPDATE 19.13.0.0.0


CD /D D:\stage\33192694
%oracle_home%\opatch\Opatch lspatches | findstr "33192694"

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "33192694"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Oct 2021 - Patch 33197296 : JDK 1.8.0_311 BUNDLE PATCH 19.0.0.0.211019
CD /D D:\stage\33197296
%oracle_home%\opatch\Opatch lspatches | findstr "33197296"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "33197296"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.


DO NOT APPLY ON GRID HOME
Rollback Perl
Rollback Oct 2020 PERL Patch 29511771

%ORACLE_HOME%\opatch\opatch lspatches | findstr "29511771"

%ORACLE_HOME%\opatch\opatch rollback -id 29511771 -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "29511771"

Enter Y to proceed with patching – then other options


Verify the patch has been rolled back

Apply Jan 2021 - Patch 31732095: UPDATE PERL IN 19C DATABASE ORACLE HOME TO V5.
32

Why Rollback First?

We are rolling back and then re-apply same patch as JAN 2021 Perl Patch was re-released with SAME patch number

CD /D D:\stage\31732095

%oracle_home%\opatch\Opatch lspatches | findstr "31732095"

%ORACLE_HOME%\opatch\opatch rollback -id 31732095 -silent

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "31732095"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.


If the below command to validate Perl causes issues - the correct Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 is missing
from OS - check in control Panel.

%ORACLE_HOME%\perl\bin\perl -version

Solution: Install - Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 in next section

Validate the Applied Patches, JDK & Perl


%oracle_home%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

cd /d %ORACLE_HOME%\jdk\bin

java -version

Apply Jul 20201 - Patch 32832237: WINDOWS DATABASE BUNDLE PATCH 19.12.0.0.210720
CD /D D:\stage\32832237

%ORACLE_HOME%\opatch\opatch lspatches | findstr "32832237"

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "32832237"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Jul 20201 - Patch 32876380 : OJVM RELEASE UPDATE 19.12.0.0.210720


CD /D D:\stage\32876380

%oracle_home%\opatch\Opatch lspatches | findstr "32876380"

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "32876380"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Jul 2021 - Patch 32918394 : JDK 1.8.0_301 BUNDLE PATCH 19.0.0.0.210720
CD /D D:\stage\32918394

%oracle_home%\opatch\Opatch lspatches | findstr "32918394"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "32918394"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

DO NOT APPLY ON GRID HOME


Rollback Perl
Rollback Oct 2020 PERL Patch 29511771

%ORACLE_HOME%\opatch\opatch lspatches | findstr "29511771"

%ORACLE_HOME%\opatch\opatch rollback -id 29511771 -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "29511771"

Enter Y to proceed with patching – then other options


Verify the patch has been rolled back

Apply Jan 2021 - Patch 31732095: UPDATE PERL IN 19C DATABASE ORACLE HOME TO V5.
32
Why Rollback First?

We are rolling back and then re-apply same patch as JAN 2021 Perl Patch was re-released with SAME patch number

CD /D D:\stage\31732095

%oracle_home%\opatch\Opatch lspatches | findstr "31732095"

%ORACLE_HOME%\opatch\opatch rollback -id 31732095 -silent

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "31732095"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

If the below command to validate Perl causes issues - the correct Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 is missing
from OS - check in control Panel.

%ORACLE_HOME%\perl\bin\perl -version

Solution: Install - Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 in next section

Validate the Applied Patches, JDK & Perl


%oracle_home%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

cd /d %ORACLE_HOME%\jdk\bin

java -version

Apply Apr 20201 - Patch 32409154: WINDOWS DATABASE BUNDLE PATCH 19.11.0.0.210420
CD /D D:\stage\32409154

%ORACLE_HOME%\opatch\opatch lspatches | findstr "32409154"

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "32409154"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Apr 20201 - Patch 32399816: OJVM RELEASE UPDATE 19.11.0.0.0.210420


CD /D D:\stage\32399816

%oracle_home%\opatch\Opatch lspatches | findstr "32067171"

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "32399816"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Apr 2021 - Patch 32490416 : JDK 1.8.0_281 BUNDLE PATCH 19.0.0.0.210420
CD /D D:\stage\32490416

%oracle_home%\opatch\Opatch lspatches | findstr "32490416"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "32490416"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

DO NOT APPLY ON GRID HOME


Rollback Perl
Rollback Oct 2020 PERL Patch 29511771
%ORACLE_HOME%\opatch\opatch lspatches | findstr "29511771"

%ORACLE_HOME%\opatch\opatch rollback -id 29511771 -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "29511771"

Enter Y to proceed with patching – then other options


Verify the patch has been rolled back

Apply Jan 2021 - Patch 31732095: UPDATE PERL IN 19C DATABASE ORACLE HOME TO V5.
32

Why Rollback First?

We are rolling back and then re-apply same patch as JAN 2021 Perl Patch was re-released with SAME patch number

CD /D D:\stage\31732095

%oracle_home%\opatch\Opatch lspatches | findstr "31732095"

%ORACLE_HOME%\opatch\opatch rollback -id 31732095 -silent

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "31732095"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.


If the below command to validate Perl causes issues - the correct Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 is missing
from OS - check in control Panel.

%ORACLE_HOME%\perl\bin\perl -version

Solution: Install - Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 in next section

Validate the Applied Patches, JDK & Perl


%oracle_home%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

cd /d %ORACLE_HOME%\jdk\bin

java -version

Apply Jan 20201 - Patch 32062765: WINDOWS DATABASE BUNDLE PATCH 19.10.0.0.210119
CD /D D:\stage\32062765

%ORACLE_HOME%\opatch\opatch lspatches | findstr "32062765"

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "32062765"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Jan 20201 - Patch 32067171: OJVM RELEASE UPDATE 19.10.0.0.0.210119


CD /D D:\stage\32067171

%oracle_home%\opatch\Opatch lspatches | findstr "32067171"

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "32067171"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Jan 2021 - Patch 32162391: JDK 1.8.0_281 BUNDLE PATCH 19.0.0.0.210119
CD /D D:\stage\32162391

%oracle_home%\opatch\Opatch lspatches | findstr "32162391"

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "32162391"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

DO NOT APPLY ON GRID HOME


Rollback Perl
Rollback Oct 2020 PERL Patch 29511771

%ORACLE_HOME%\opatch\opatch lspatches | findstr "29511771"

%ORACLE_HOME%\opatch\opatch rollback -id 29511771 -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "29511771"

Enter Y to proceed with patching – then other options


Verify the patch has been rolled back

Apply Jan 2021 - Patch 31732095: UPDATE PERL IN 19C DATABASE ORACLE HOME TO V5.
32
Why Rollback First?

We are rolling back and then re-apply same patch as JAN 2021 Perl Patch was re-released with SAME patch number

CD /D D:\stage\31732095

%oracle_home%\opatch\Opatch lspatches | findstr "31732095"

%ORACLE_HOME%\opatch\opatch rollback -id 31732095 -silent

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "31732095"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

If the below command to validate Perl causes issues - the correct Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 is missing
from OS - check in control Panel.

%ORACLE_HOME%\perl\bin\perl -version

Solution: Install - Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 in next section

Validate the Applied Patches, JDK & Perl


%oracle_home%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

cd /d %ORACLE_HOME%\jdk\bin

java -version
Apply Oct 2020 - 19.9.0.0.201020 DB Patch 31719903
CD /D D:\stage\31719903

%ORACLE_HOME%\opatch\opatch lspatches | findstr "31719903"

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "31719903"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply Oct 2020 - 19.9.0.0.201020 JVM Patch 31668882


CD /D D:\stage\31668882

%oracle_home%\opatch\Opatch lspatches | findstr "31668882"

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "31668882"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Oct 2020 - JDK BUNDLE PATCH 19.0.0.0.201020 Patch 31743771


CD /D D:\stage\31743771

%ORACLE_HOME%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "31743771"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply Oct 2020 - UPDATE PERL IN 19.3.0.0.0 DATABASE ORACLE HOME Patch 29511771
Not Required as it is included in Default media since 19.3.0.0.0

set ORACLE_HOME=D:\ORACLE\1970

%ORACLE_HOME%\perl\bin\perl -version

To Check version:

set ORACLE_HOME=D:\ORACLE\1970

%ORACLE_HOME%\perl\bin\perl -version

Validate the Applied Patches, JDK & Perl


%oracle_home%\opatch\Opatch lspatches

%ORACLE_HOME%\perl\bin\perl -version

cd /d %ORACLE_HOME%\jdk\bin

java -version
Apply July 2020 - 19.8.0.0.0.200714 DB Patch 31247621
CD /D D:\stage\31247621

%ORACLE_HOME%\opatch\opatch lspatches | findstr "31247621"

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "31247621"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.

Apply July 2020 - 19.7.0.0.0.200714 JVM Patch 31219897


CD /D D:\stage\31219897

%oracle_home%\opatch\Opatch lspatches | findstr "31219897"

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "31219897"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Apply April 2020 - 19.7.0.0.0.200414 DB Patch 30901317


CD /D D:\stage\30901317

%ORACLE_HOME%\opatch\opatch lspatches | findstr "30901317"

%ORACLE_HOME%\opatch\opatch apply -silent

%ORACLE_HOME%\opatch\opatch lspatches | findstr "30901317"

Enter Y to proceed with patching – then other options


Verify the patch has been applied.

If it has been applied it will show result.


Apply April 2020 - 19.7.0.0.0.200414 JVM Patch 30805684
CD /D D:\stage\30805684

%oracle_home%\opatch\Opatch lspatches | findstr "30805684"

%ORACLE_HOME%\opatch\opatch apply -silent

%oracle_home%\opatch\Opatch lspatches | findstr "30805684"

When prompted – enter Y to proceed and any other prompts as required – Allow the patch to complete without errors.

Verify the patch has been applied.

If it has been applied it will show result.

Patch Database
Set DB Home
Set Environment
Set Instance Startup Manual
Start DB Service for Listener / Instance
Check Current Patch versions
Apply Oracle 19.x Current Patch
Post Apply - Restart Database
Run UTLRP to recompile
Upgrade Timezone (Mandatory)
Re Verify patches Applied
Granting Java permission ON sun.misc classes TO OPERA AND SYNONYM schemas (OPTIONAL)
Update ANYDATASET
Resource Plan Scheduler
Modify Stats
Revert ini / spfile Changes
Instance Startup AUTO
Restart services and validate
Modify INIT / SPFILE Parameters
Other Services

Setup Proper Environment Variables

If your ORACLE_HOME is different - ensure you have the correct value set
If your ORACLE_SID is different - ensure you have the correct value set
If you have a separate instance for OPERA and INFRA make sure to APPLY the patches to BOTH OPERA and INFRA
databases by setting the set ORACLE_SID=OPERA or set ORACLE_SID=INFRA
Make sure to modify INIT / SPFILE parameters BEFORE upgrade to avoid issues.

Set DB Home

Warning

When Patching Make sure to use the correct ORACLE_HOME and ORACLE_SID wherever and whenever required.
set ORACLE_HOME=D:\ORACLE\1970

set ORACLE_SID=opera

Make sure the WINDOWS PATH also includes the following AS FIRST ENTRY

D:\ORACLE\1970\bin;D:\ORACLE\1970\perl\bin

Also ensure the BELOW variables are NOT Set in WINDOWS Environment variables

PERL5LIB
perlpath

Set Environment
If opening a new command window open CMD.prompt (as admin) and use BELOW Environment variables and stick to that window

set ORACLE_BASE=d:\oracle

set ORACLE_HOME=D:\ORACLE\1970

set ORACLE_SID=opera

set PERL5LIB=

set perlpath=

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

cd /D %ORACLE_HOME%\rdbms\admin

Set Instance Startup Manual


cd /D %ORACLE_HOME%\database

oradim -edit -sid opera -startmode m

Start DB Service for Listener / Instance


Start the Database Listener and the Database Services for INSTANCE being upgraded.

then Open database in upgrade mode

Depending on Which ENV is being upgraded Make sure to set ORACLE_HOME and ORACLE_SID before connect as SYS
cd /D %ORACLE_HOME%\rdbms\admin

sqlplus / as sysdba

startup upgrade

select instance_name from v$instance;

Check Current Patch versions


Make sure you are connected to the Correct Instance

select instance_name from v$instance;

set lines 150


Column ActionTime heading 'Action Time' format a15
Column Action heading 'Action' format a15
Column Details heading 'Details' format a100
select to_char(action_time,'RRRR-MM-DD HH24:MI') ActionTime,
ltrim(rtrim(action)) Action,
' P# '||ltrim(rtrim(to_char(patch_ID)))||' '||ltrim(rtrim(description)) Details
from registry$sqlpatch order by 1;

output may differ depending on Patches applied

Exit from SQLPLUS - But Keep the CMD window open as we need the Environment variables set earlier.

Apply Oracle 19.x Current Patch


Make sure the PATH also includes the following:

D:\ORACLE\1970\perl\bin

Also ensure the BELOW variables are NOT Set in Environment variables

PERL5LIB
perlpath

Ensure Database is OPEN in UPGRADE mode

Depending on Which ENV is being upgraded Make sure to set ORACLE_HOME and ORACLE_SID before connect as SYS

cd /D %ORACLE_HOME%\opatch

datapatch -prereq

Patch numbers may differ depending on what is being applied.


Evaluate the output if you see no issues then proceed.

cd /D %ORACLE_HOME%\opatch

datapatch -verbose

Patch numbers may differ depending on what is being applied.

As always, review the upgrade logs for any typical errors. and also ensure the patches that were applied in binaries have been applied to the
database.

Issue noted when Datapatch -verbose is done for Jan 2023:

Known Issue

If DB is open upgrade - datapatch -verbose fails

Doc Ref: 19.x:datapatch failed with 'ORA-13516: AWR Operation failed: CATPROC not valid ' (Doc ID 2922690.1)

Solution : open DB in normal mode and re run datapatch -verbose

Issue (1)

SQL Patching tool version 19.18.0.0.0 Production on Thu Mar 9 13:12:22 2023
Copyright (c) 2012, 2023, Oracle. All rights reserved.

Log file for this invocation: D:


\Oracle\cfgtoollogs\sqlpatch\sqlpatch_16916_2023_03_09_13_12_22\sqlpatch_invocation.log
Connecting to database...OK
Gathering database info...done
Bootstrapping registry and package to current versions...done
Determining current state...done

Current state of interim SQL patches:


Interim patch 30805684 (OJVM RELEASE UPDATE: 19.7.0.0.200414 (30805684)):
Binary registry: Not installed
SQL registry: Rolled back successfully on 02-MAR-23 06.02.30.122000 PM
Interim patch 34411846 (OJVM RELEASE UPDATE: 19.17.0.0.221018 (34411846)):
Binary registry: Not installed
SQL registry: Applied successfully on 02-MAR-23 06.02.36.358000 PM
Interim patch 34786990 (OJVM RELEASE UPDATE: 19.18.0.0.230117 (34786990)):
Binary registry: Installed
SQL registry: Not installed

Current state of release update SQL patches:


Binary registry:
19.18.0.0.0 Release_Update 230201003237: Installed
SQL registry:
Applied 19.17.0.0.0 Release_Update 221027022151 successfully on 02-MAR-23 06.02.36.358000 PM

Adding patches to installation queue and performing prereq checks...done


Installation queue:
The following interim patches will be rolled back:
34411846 (OJVM RELEASE UPDATE: 19.17.0.0.221018 (34411846))
Patch 34750795 (Windows Database Bundle Patch : 19.18.0.0.230117 (34750795)):
Apply from 19.17.0.0.0 Release_Update 221027022151 to 19.18.0.0.0 Release_Update 230201003237
The following interim patches will be applied:
34786990 (OJVM RELEASE UPDATE: 19.18.0.0.230117 (34786990))

Installing patches...
Patch installation complete. Total patches installed: 3

Validating logfiles...done
Patch 34411846 rollback: SUCCESS
logfile: D:\Oracle\cfgtoollogs\sqlpatch\34411846\24997534/34411846_rollback_OPERA_2023Mar09_13_20_45.
log (no errors)
Patch 34750795 apply: WITH ERRORS
logfile: D:\Oracle\cfgtoollogs\sqlpatch\34750795\25040762/34750795_apply_OPERA_2023Mar09_13_24_30.log
(errors)
-> Error at line 45033: script rdbms/admin/backport_files/bug_33527739_apply.sql
- ORA-13516: AWR Operation failed: CATPROC not valid
- ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 328
- ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 355
- ORA-06512: at line 12
Patch 34786990 apply: WITH ERRORS (PREV PATCH)
logfile: D:\Oracle\cfgtoollogs\sqlpatch\34786990\25141362/34786990_apply_OPERA_2023Mar09_13_24_30.log
(no errors)

Adding patches to retry installation queue...done


Retry installation queue:
No interim patches need to be rolled back
Patch 34750795 (Windows Database Bundle Patch : 19.18.0.0.230117 (34750795)):
Apply from 19.17.0.0.0 Release_Update 221027022151 to 19.18.0.0.0 Release_Update 230201003237
The following interim patches will be applied:
34786990 (OJVM RELEASE UPDATE: 19.18.0.0.230117 (34786990))

Installing patches...
Patch installation complete. Total patches installed: 2

Validating logfiles...done
Patch 34750795 apply: WITH ERRORS
logfile: D:\Oracle\cfgtoollogs\sqlpatch\34750795\25040762/34750795_apply_OPERA_2023Mar09_13_26_59.log
(errors)
-> Error at line 45033: script rdbms/admin/backport_files/bug_33527739_apply.sql
- ORA-13516: AWR Operation failed: CATPROC not valid
- ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 328
- ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 355
- ORA-06512: at line 12
Patch 34786990 apply: WITH ERRORS (PREV PATCH)
logfile: D:\Oracle\cfgtoollogs\sqlpatch\34786990\25141362/34786990_apply_OPERA_2023Mar09_13_26_58.log
(no errors)

Please refer to MOS Note 1609718.1 and/or the invocation log


D:\Oracle\cfgtoollogs\sqlpatch\sqlpatch_16916_2023_03_09_13_12_22\sqlpatch_invocation.log
for information on how to resolve the above errors.

SQL Patching tool complete on Thu Mar 9 13:27:24 2023

Issue (2)

For some customers following error is observed after applying patch 35012866 ,which can be resolved by
rerun of the datapatch

Error at line 47019: script rdbms/admin/backport_files/bug_33527739_apply.sql


- ORA-06550: line 12, column 24:
- PLS-00302: component 'FIXUP_CATALOG' must be declared
- ORA-06550: line 12, column 5:

Cause:

Issue is due to database started up in upgrade or restricted mode .At the moment ,issue is triaged
under unpublished Bug 35012866 - BUG_33527739_APPLY.SQL GOT ORA-13516: AWR OPERATION FAILED: CATPROC
NOT VALID
Sample AWR API script creation to check AWR is fine or not also failed with errors .

SQL> exec dbms_workload_repository.create_snapshot();


BEGIN dbms_workload_repository.create_snapshot(); END;

*
ERROR at line 1:
ORA-13516: AWR Operation failed: CATPROC not valid
ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 99
ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 145
ORA-06512: at line 1

Solution/Workaround

Solution : Patch 35012866 (Linux only for now) can be applied on oracle home to fix this issue and datapatch can be run in database
started in upgrade mode as well.

Workaround is to start the database in normal mode and re-run of datapatch .Development provided fix for the same for next CPU

open SQLPLUS and connect as sys

shutdown immediate

startup

exec dbms_workload_repository.create_snapshot();

alter trigger SYS.LOGMNRGGC_TRIGGER disable ;

Now run datapatch again

open CMD.exe

cd /d %ORACLE_HOME%\opatch

datapatch -verbose

Again check SQLPLUS is sucessfull


open SQLPLUS and connect as sys

exec dbms_workload_repository.create_snapshot();

Output as seen:
cd /d D:\Oracle\1970\opatch

D:\Oracle\1970\opatch>datapatch -verbose

D:\Oracle\1970\OPatch>datapatch -verbose
SQL Patching tool version 19.18.0.0.0 Production on Thu Mar 9 08:44:38 2023
Copyright (c) 2012, 2023, Oracle. All rights reserved.

Log file for this invocation: D:


\Oracle\cfgtoollogs\sqlpatch\sqlpatch_1156_2023_03_09_08_44_38\sqlpatch_invocation.log

Connecting to database...OK
Gathering database info...done
Bootstrapping registry and package to current versions...done
Determining current state...done

Current state of interim SQL patches:


Interim patch 30805684 (OJVM RELEASE UPDATE: 19.7.0.0.200414 (30805684)):
Binary registry: Not installed
SQL registry: Rolled back successfully on 09-MAR-23 06.19.38.264000 AM
Interim patch 34786990 (OJVM RELEASE UPDATE: 19.18.0.0.230117 (34786990)):
Binary registry: Installed
SQL registry: Applied with errors on 09-MAR-23 06.46.39.204000 AM

Current state of release update SQL patches:


Binary registry:
19.18.0.0.0 Release_Update 230201003237: Installed
SQL registry:
Applied 19.18.0.0.0 Release_Update 230201003237 with errors on 09-MAR-23 06.46.39.188000 AM

Adding patches to installation queue and performing prereq checks...done


Installation queue:
No interim patches need to be rolled back
Patch 34750795 (Windows Database Bundle Patch : 19.18.0.0.230117 (34750795)):
Apply from 19.7.0.0.0 Release_Update 200514113449 to 19.18.0.0.0 Release_Update 230201003237
The following interim patches will be applied:
34786990 (OJVM RELEASE UPDATE: 19.18.0.0.230117 (34786990))

Installing patches...
Patch installation complete. Total patches installed: 2

Validating logfiles...done
Patch 34750795 apply: SUCCESS
logfile: D:\Oracle\cfgtoollogs\sqlpatch\34750795\25040762/34750795_apply_OPERA_2023Mar09_08_59_15.log
(no errors)
Patch 34786990 apply: SUCCESS
logfile: D:\Oracle\cfgtoollogs\sqlpatch\34786990\25141362/34786990_apply_OPERA_2023Mar09_08_59_13.log
(no errors)
SQL Patching tool complete on Thu Mar 9 09:03:54 2023

Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.18.0.0.0

SQL> exec dbms_workload_repository.create_snapshot();

PL/SQL procedure successfully completed.


Issue noted when Datapatch -verbose ORA-04088: error during execution of trigger 'SYS.LOGMNRGGC_TRIGGER'

Patch 34110685 apply: WITH ERRORS


logfile: D:\Oracle\cfgtoollogs\sqlpatch\34110685\24797704/34110685_apply_OPERA_2023Mar07_13_42_35.log
(errors)
-> Error at line 3503: script rdbms/admin/backport_files/bug_31926848_apply.sql
- ORA-04088: error during execution of trigger 'SYS.LOGMNRGGC_TRIGGER'
- ORA-00604: error occurred at recursive SQL level 1
- ORA-04068: existing state of packages has been discarded
- ORA-04061: existing state of package body "SYS.LOGMNR_DICT_CACHE" has been
- invalidated
- ORA-06512: at "SYS.LOGMNR_DDL_TRIGGER_PROC", line 142
- ORA-04065: not executed, altered or dropped package body
- "SYS.LOGMNR_DICT_CACHE"
- ORA-06508: PL/SQL: could not find program unit being called:
- "SYS.LOGMNR_DICT_CACHE"
- ORA-06512: at "SYS.LOGMNR_DDL_TRIGGER_PROC", line 111
- ORA-06512: at line 2

Solution / Workaround

-- connect to SYS

alter trigger SYS.LOGMNRGGC_TRIGGER disable ;

-- now re run the datapatch

cd /d %ORACLE_HOME%\opatch

datapatch -verbose

Issue noted when Datapatch -verbose Rollback of Default Media V1001407-01 OJVM April 2020 - Patch 30805684 rollback to apply
July 2021 OJVM patch

Patch 30805684 rollback: WITH ERRORS


logfile: D:\Oracle\cfgtoollogs\sqlpatch\30805684\23504850/30805684_rollback_OPERA_2021Aug31_07_58_09.
log (errors)
-> Error at line 44: script javavm/install/jvmpsupdi.sql
- ORA-04068: existing state of packages has been discarded
- ORA-04061: existing state of has been invalidated
- ORA-04061: existing state of package body "SYS.DBMS_REGISTRY_SYS" has been
- invalidated
- ORA-04065: not executed, altered or dropped package body
- "SYS.DBMS_REGISTRY_SYS"
- ORA-06508: PL/SQL: could not find program unit being called:
- "SYS.DBMS_REGISTRY_SYS"
- ORA-06512: at "SYS.DBMS_REGISTRY", line 2859
- ORA-06512: at line 5
-> Error at line 67: script javavm/install/jvmpsupdi.sql
- SP2-0556: Invalid file name.
Patch 32832237 apply: SUCCESS
logfile: D:\Oracle\cfgtoollogs\sqlpatch\32832237\24292339/32832237_apply_OPERA_2021Aug31_08_00_42.log
(no errors)
Patch 32876380 apply: SUCCESS
logfile: D:\Oracle\cfgtoollogs\sqlpatch\32876380\24382230/32876380_apply_OPERA_2021Aug31_07_58_10.log
(no errors)

Re-run datapatch -verbose


-- now re run the datapatch

cd /d %ORACLE_HOME%\opatch

datapatch -verbose

D:\Oracle\1970\opatch>datapatch -verbose
SQL Patching tool version 19.13.0.0.0 Production on Thu Nov 25 10:23:13 2021
Copyright (c) 2012, 2021, Oracle. All rights reserved.

Log file for this invocation: D:


\Oracle\cfgtoollogs\sqlpatch\sqlpatch_2044_2021_11_25_10_23_13\sqlpatch_invocation.log

Connecting to database...OK
Gathering database info...done
Bootstrapping registry and package to current versions...done
Determining current state...done

Current state of interim SQL patches:


Interim patch 30805684 (OJVM RELEASE UPDATE: 19.7.0.0.200414 (30805684)):
Binary registry: Not installed
SQL registry: Rolled back with errors on 25-NOV-21 10.19.46.514000 AM

Current state of release update SQL patches:


Binary registry:
19.13.0.0.0 Release_Update 211018090745: Installed
SQL registry:
Applied 19.13.0.0.0 Release_Update 211018090745 successfully on 25-NOV-21 10.19.54.170000 AM

Adding patches to installation queue and performing prereq checks...done


Installation queue:
The following interim patches will be rolled back:
30805684 (OJVM RELEASE UPDATE: 19.7.0.0.200414 (30805684))
No release update patches need to be installed
No interim patches need to be applied

Installing patches...
Patch installation complete. Total patches installed: 1

Validating logfiles...done
Patch 30805684 rollback: SUCCESS
logfile: D:\Oracle\cfgtoollogs\sqlpatch\30805684\23504850/30805684_rollback_OPERA_2021Nov25_10_27_53.
log (no errors)
SQL Patching tool complete on Thu Nov 25 10:27:54 2021

For Validation RE-RUN the DATAPATCH and evaluate the result

cd /D %ORACLE_HOME%\opatch

datapatch -verbose

Patch numbers may differ depending on what is being applied.

It is important to see below messages


Post Apply - Restart Database
cd /D %ORACLE_HOME%\rdbms\admin

sqlplus / as sysdba

shutdown immediate

startup

Run UTLRP to recompile


purge dba_recyclebin;

alter system flush shared_pool;

@?\rdbms\admin\utlrp.sql

Upgrade Timezone (Mandatory)

IMPORTANT

TIMEZONE UPGRADE PROCEDURE HAS CHANGED FROM JAN 2024

THE TIMEZONE PATCHES ARE INCLUDED IN DATABASE BUNDLE PATCH SINCE JANUARY 2023

OJVM TIMEZONE PATCH ARE SEPARATELY PROVIDED AND MUST BE APPLIED

YOU MUST UPGRADE THE DATABASE TIMEZONE WHEN UPGRADING THE DATABASE

References
Important Notification
Download Patches
Workaround / Solution to TZ Hanging
STARTING JAN 2024 THIS WORKAROUND SHOULD NO LONGER BE REQUIRED - BUT PROVIDED BELOW IN CASE REQUIRED
Set Environment
Check Current Time Patch Applied DB Home
Check Current Time Zone File Version In DB Home
Check Time Zone Details in Database Registry
Upgrade OPATCH (Latest)
Apply Timezone Patch 36260493 RDBMS - DSTV43 UPDATE - TZDATA2024A
Apply Timezone OJVM FIX Patch 36260537 DSTV43 UPDATE - TZDATA2024A - NEED OJVM FIX
Check Current Time Patch Applied DB Home
Check Current Time Zone Version (In DB Home)
Startup the Database in UPGRADE Mode
Validate of the Latest File version from DB registry picked up from DB Home
Validate of the Latest Filezone file version from DB Home
Check Current Time Zone Version
Upgrade Timezone in Database
Check Current Time Zone Version
Post Tasks For OJVM
Timezone Upgrade Complete

References

Issues and workarounds:

Updating the RDBMS DST version in 12c Release 1 (12.1.0.1 ) and above using DBMS_DST (Doc ID 1509653.1)

Updating the RDBMS DST version in 11g Release 2 (11.2.0.1 and up) using DBMS_DST (Doc ID 977512.1)

Upgrading the Time Zone File and Timestamp with Time Zone Data / Globalization Methods to Upgrade the Time Zone File and Timestamp with Time
Zone Data (18c and above)

To Download Latest utltz_upg_check (See attachments in the end)

Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches (Doc ID 412160.1)

Oracle 19c - Complete Checklist for Manual Upgrades to Non-CDB Oracle Database 19c (Doc ID 2539778.1)

Upgrading the Time Zone File and Timestamp with Time Zone Data

A complete overview of timezone updates is found in Note 412160.1 Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time
Zone File Patches.

For latest DST patch refer to Note 412160.1.

check section C.1.a) If you upgrade to 10.2.0.4, 10.2.0.5, 11.1.0.6, 11.1.0.7 , 11.2.0.1, 11.2.0.2 ,11.2.0.3 , 11.2.0.4 , 12.1.0.1 or 12.1.0.2,18.x, 19.x please
see:

If the Pre-Upgrade Information Tool instructed you to upgrade the time zone files after completing the database upgrade, then use the DBMS_DST PL
/SQL package to update the RDBMS DST (timezone) version.

Applying the DSTv43 update for the Oracle Database (Doc ID 3002390.1)

Important Notification

IMPORTANT

TIMEZONE UPGRADE PROCEDURE HAS CHANGED FROM JAN 2024

THE TIMEZONE PATCHES ARE INCLUDED IN DATABASE BUNDLE PATCH SINCE JANUARY 2023

OJVM TIMEZONE PATCH ARE SEPARATELY PROVIDED AND MUST BE APPLIED

YOU MUST UPGRADE THE DATABASE TIMEZONE WHEN UPGRADING THE DATABASE

Download Patches

Patches Details Comments

6880880 x64 Bit OPatch 12.2.0.1.42 for DB 19.0.0.0.0 (Apr 2024 or later) Use Latest

36260493 x64 Bit RDBMS - DSTV43 UPDATE - TZDATA2024A Already included in DB Bundle Patch from APR 2024

36260537 x64 Bit DSTV43 UPDATE - TZDATA2024A - NEED OJVM FIX Already included in OJVM Bundle Patch from JUL 2024

Download and extract all the patch to D:\Stage\<PATCHNUMBER>


Workaround / Solution to TZ Hanging

STARTING JAN 2024 THIS WORKAROUND SHOULD NO LONGER BE REQUIRED - BUT PROVIDED
BELOW IN CASE REQUIRED

Use with CAUTION.

Solution to TZ Hanging during CHECK and APPLY - Use with CAUTION

There have been issues where the CHECK or APPLY phase just hangs on 19c and seem to do Nothing

Attach the new version files in %ORACLE_HOME%\rdbms\admin (keep old backups)

And re run the TZ process from CHECK and APPLY.

DBMST_Utltz-Media_files-CPU-APR-2024-TZ43.zip

Set Environment

set ORACLE_BASE=d:\oracle

set ORACLE_HOME=D:\ORACLE\1970

set ORACLE_SID=opera

set PERL5LIB=

set perlpath=

set PATH=D:\ORACLE\1970\bin;D:\ORACLE\1970\perl\bin;%PATH%

cd /D %ORACLE_HOME%\rdbms\admin

Check Current Time Patch Applied DB Home

%ORACLE_HOME%\opatch\opatch version

%ORACLE_HOME%\opatch\Opatch lspatches

will display the OPATCH Version and List of apatches applied to DB Home (May differ)

%ORACLE_HOME%\opatch\Opatch lsinventory | findstr “36260493”

%ORACLE_HOME%\opatch\Opatch lsinventory | findstr “36260537”


will display if PATCH 36260493 and PATCH 36260537 have been applied to DB Home

Check Current Time Zone File Version In DB Home


go to Directory %ORACLE_HOME%\oracore\zoneinfo and verify WHAT Timezone files exist

cd /d %ORACLE_HOME%\oracore\zoneinfo

dir *43*.dat

Important : Make a note of the Last timezone***.dat and timezlrg***.dat files existing in the folder

Check Time Zone Details in Database Registry

SELECT * FROM v$timezone_file;

SELECT tz_version FROM registry$database;

COLUMN property_name FORMAT A30


COLUMN property_value FORMAT A20

SELECT property_name, property_value


FROM database_properties
WHERE property_name LIKE 'DST_%'
ORDER BY property_name;

SELECT DBMS_DST.get_latest_timezone_version FROM dual;

If TZ 42 Patch HAS NOT been applied If TZ 43 Patch HAS been Applied


You should see THIS current version of the Timezone file
You should see the latest version of the Timezone file in %oracle_home%\oracore\zonefile - It will NOT the version you are applying.
Necessarilty be the version you are applying.

IMPORTANT

IMPORTANT

IF THE NEW TIMEZONE HAS ALREADY BEEN APPLIED

MOVE TO STEP "Post Tasks For OJVM"


Upgrade OPATCH (Latest)
Important - If the ABOVE output Shows the TIMEZONE Patch Has been applied no need to do this step

Ensure you have set Variables for ORACLE_HOME and ORACLE_SID

Verify OPATCH version

set oracle_home=d:\oracle\1970

CD /D %ORACLE_HOME%\bin

%ORACLE_HOME%\opatch\opatch version

Rename existing OPATCH folder - rename %ORACLE_HOME%\OPatch to %ORACLE_HOME%\OPatch_OLD

Copy the D:\Stage\6880880\Opatch folder to %ORACLE_HOME%\OPatch

verify OPATCH version

set oracle_home=d:\oracle\1970

CD /D %ORACLE_HOME%\bin

%ORACLE_HOME%\opatch\opatch version

Apply Timezone Patch 36260493 RDBMS - DSTV43 UPDATE - TZDATA2024A

%oracle_home%\opatch\opatch lsinventory | findstr "36260493"

Important - If the ABOVE output Shows the TIMEZONE Patch Has been applied no need to do this step

cd /d d:\stage\36260493_19

%oracle_home%\opatch\opatch lsinventory | findstr "36260493"

%oracle_home%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%oracle_home%\opatch\opatch apply -silent

%oracle_home%\opatch\opatch lsinventory | findstr "36260493"

Apply Timezone OJVM FIX Patch 36260537 DSTV43 UPDATE - TZDATA2024A - NEED OJVM FIX

%oracle_home%\opatch\opatch lsinventory | findstr "36260537"

Important - If the ABOVE output Shows the TIMEZONE OJVMFIX Patch Has been applied no need to do this step
cd /d d:\stage\36260537

%oracle_home%\opatch\opatch lsinventory | findstr "36260537"

%oracle_home%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%oracle_home%\opatch\opatch apply -silent

%oracle_home%\opatch\opatch lsinventory | findstr "36260537"

Check Current Time Patch Applied DB Home

%ORACLE_HOME%\opatch\opatch version

%ORACLE_HOME%\opatch\Opatch lspatches

will display the OPATCH Version and List of apatches applied to DB Home (May differ)

%ORACLE_HOME%\opatch\Opatch lsinventory | findstr “36260493”

%ORACLE_HOME%\opatch\Opatch lsinventory | findstr “36260537”

will display if PATCH 36260493 and PATCH 36260537 have been applied to DB Home

Check Current Time Zone Version (In DB Home)


go to Directory %ORACLE_HOME%\oracore\zoneinfo and verify the Timezone files exist

cd /d %ORACLE_HOME%\oracore\zoneinfo

dir *43*.dat
Check the timezone_43.dat and timezlrg_43.dat files existing in the folder

DO NOT PROCEED IF IT DOES NOT

Startup the Database in UPGRADE Mode

cd /d %ORACLE_HOME%\rdbms\admin

sqlplus / as sysdba

shutdown immediate

startup upgrade

Validate of the Latest File version from DB registry picked up from DB Home
Important - The OUTPUT should show the version of the TIMEZONE Patch you are applying - in this case TIMEZONE 42 is showing

--connect as SYS and run via SQLPLUS

SELECT DBMS_DST.get_latest_timezone_version FROM dual;

1. If above query DOES not reflect the NEW current version of the Timezone being upgraded - DO NOT PROCEED.

Validate of the Latest Filezone file version from DB Home


Important - The OUTPUT should show the cversion of the TIMEZONE Patch you applied - in this case TIMEZONE 42 was applied.

cd /d %ORACLE_HOME%\oracore\zoneinfo

dir *43*.dat
1. Check the latest Timezone files exist in %oracle_home%\oracore\zoneinfo
2. There WILL be two NEW files - If they don't exist in %oracle_home%\oracore\zoneinfo - DO NOT PROCEED.
a. timezlrg_43.dat
b. timezone_43.dat

Check Current Time Zone Version

SELECT * FROM v$timezone_file;

SELECT tz_version FROM registry$database;

COLUMN property_name FORMAT A30


COLUMN property_value FORMAT A20

SELECT property_name, property_value


FROM database_properties
WHERE property_name LIKE 'DST_%'
ORDER BY property_name;

SELECT DBMS_DST.get_latest_timezone_version FROM dual;

If TZ 42 Patch HAS NOT been applied If TZ 42 Patch HAS been Applied


You should see THIS current version of the Timezone file
You should see the latest version of the Timezone file in %oracle_home%\oracore\zonefile - It will NOT be the version you are applying.
Necessarilty be the version you are applying.

IMPORTANT

IMPORTANT

IF THE NEW TIMEZONE HAS ALREADY BEEN APPLIED

MOVE TO STEP "Post Tasks For OJVM"

Upgrade Timezone in Database


Apply these commands ONE BY ONE – Not all combined – in one shot – check for issues/errors in each.

-- Spool the output


cd /d %ORACLE_HOME%\rdbms\admin

sqlplus / as sysdba

purge dba_recyclebin;

exec dbms_scheduler.purge_log;

select systimestamp - dbms_stats.get_stats_history_availability from dual;

select count(*) from SYS.WRI$_OPTSTAT_HISTGRM_HISTORY;

select count(*) from SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY;

exec dbms_stats.alter_stats_history_retention(7);

EXEC DBMS_STATS.PURGE_STATS( SYSDATE-7 );

@%ORACLE_HOME%\rdbms\admin\utltz_countstats.sql

@%ORACLE_HOME%\rdbms\admin\utltz_countstar.sql

@%ORACLE_HOME%\rdbms\admin\utltz_upg_check.sql

@%ORACLE_HOME%\rdbms\admin\utltz_upg_apply.sql

select * from v$timezone_file;

exec dbms_stats.alter_stats_history_retention(31);

Check Current Time Zone Version

SELECT * FROM v$timezone_file;

SELECT tz_version FROM registry$database;

COLUMN property_name FORMAT A30


COLUMN property_value FORMAT A20

SELECT property_name, property_value


FROM database_properties
WHERE property_name LIKE 'DST_%'
ORDER BY property_name;

Output - YOU MUST SEE THIS


Post Tasks For OJVM
Apply fixTZa

@?/javavm/admin/fixTZa.sql

If you see below....No Need to apply fixTZb (Next Step)


IMPORTANT

IMPORTANT

IF YOU SEE BELOW OUTPUT - NO NEED TO APPLY fixTZb IN THE NEXT STEP

########################################################
Bug is not present. Patch not needed.
########################################################

PL/SQL procedure successfully completed.

If you see below....Proceed to Next Step and APPLY fixTZb

IMPORTANT

IMPORTANT

IF YOU SEE BELOW OUTPUT - YOU MUST APPLY fixTZb IN THE NEXT STEP

########################################################
Bug is in fact present, so this patch is needed
Proceed by restarting the database and running script
fixTZb
########################################################

note that the "FAILED " messages are normal and part of the patching process and not an error/problem

If the output say to run fixTZb (it almost always will) then do:

Step1: If needed, edit init.ora and set cluster_database=FALSE


Step2: As SYS shutdown database: SQL> shutdown
Step3: Start the database in migrate: SQL> startup migrate
Step4: Execute the script SQL> $ORACLE_HOME/javavm/admin/fixTZb

Apply fixTZb

See example below - it is important to review output and then apply the next step if required

shutdown immediate

startup migrate

@?/javavm/admin/fixTZb.sql

shutdown immediate

startup

--- Sample Output


SQL> @?/javavm/admin/fixTZa.sql

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Java created.

No errors.

Java altered.

No errors.

Package created.

No errors.

Package body created.

No errors.

PL/SQL procedure successfully completed.

Call completed.

Testing various timezone DST attributes


FAILED for Pacific/Auckland 10:0:0 10/1/2007
FAILED for Pacific/Chatham 10:0:0 10/1/2007
FAILED for Pacific/Auckland 10:0:0 4/1/2008
...
FAILED for Pacific/Chatham 1396706399999 45900000 3900000
FAILED for Pacific/Chatham 1411826400000 45900000 3900000
##
Bug is in fact present, so this patch is needed
##
(Perhaps) modifying ild_ub1$ for rehotloading of sun/util/calendar/ZoneInfoFile
obj# = 432434
nbytes %d = 64512, 1st read = 64512, 2nd read = -1
87 379782 399648 2203701434 joxbtflag>>8 = 3
===

PL/SQL procedure successfully completed.

########################################################
Bug is in fact present, so this patch is needed
Proceed by restarting the database and running script
fixTZb
########################################################

note that the "FAILED " messages are normal and part of the patching process and not an error/problem

If the output say to run fixTZb (it almost always will) then do:

Step1: If needed, edit init.ora and set cluster_database=FALSE


Step2: As SYS shutdown database: SQL> shutdown
Step3: Start the database in migrate: SQL> startup migrate
Step4: Execute the script SQL> $ORACLE_HOME/javavm/admin/fixTZb
SQL> @?/javavm/admin/fixTZb.sql

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Call completed.

Testing various timezone DST attributes


########################################################
Bug is no longer present. Patch succeeded.
########################################################

PL/SQL procedure successfully completed.

drop java source fixTZ

drop package fixTZ

PL/SQL procedure successfully completed.

Timezone Upgrade Complete


Timezone upgrade to 43 is completed

References
Important Notification
Download Patches
Workaround / Solution to TZ Hanging
STARTING JAN 2024 THIS WORKAROUND SHOULD NO LONGER BE REQUIRED - BUT PROVIDED BELOW IN CASE REQUIRED
Set Environment
Check Current Time Zone File Version In DB Home
Check Time Zone Details in Database Registry
Upgrade OPATCH (Latest)
Apply Timezone Patch 35220732 RDBMS - DSTV42 UPDATE - TZDATA2023C
Apply Timezone OJVM Patch 35239280 DSTV42 UPDATE - TZDATA2023E - NEED OJVM FIX
Check Patches applied
Check Current Time Zone Version (In DB Home)
Startup the Database in UPGRADE Mode
Validate of the Latest File version from DB registry picked up from DB Home
Validate of the Latest Filezone file version from DB Home
Check Current Time Zone Version
Upgrade Timezone in Database
Check Current Time Zone Version
Post Tasks For OJVM
Timezone Upgrade Complete

References

Issues and workarounds:

Updating the RDBMS DST version in 12c Release 1 (12.1.0.1 ) and above using DBMS_DST (Doc ID 1509653.1)

Updating the RDBMS DST version in 11g Release 2 (11.2.0.1 and up) using DBMS_DST (Doc ID 977512.1)

Upgrading the Time Zone File and Timestamp with Time Zone Data / Globalization Methods to Upgrade the Time Zone File and Timestamp with Time
Zone Data (18c and above)

To Download Latest utltz_upg_check (See attachments in the end)


Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches (Doc ID 412160.1)

Oracle 19c - Complete Checklist for Manual Upgrades to Non-CDB Oracle Database 19c (Doc ID 2539778.1)

Upgrading the Time Zone File and Timestamp with Time Zone Data

A complete overview of timezone updates is found in Note 412160.1 Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time
Zone File Patches.

For latest DST patch refer to Note 412160.1.

check section C.1.a) If you upgrade to 10.2.0.4, 10.2.0.5, 11.1.0.6, 11.1.0.7 , 11.2.0.1, 11.2.0.2 ,11.2.0.3 , 11.2.0.4 , 12.1.0.1 or 12.1.0.2,18.x, 19.x please
see:

Applying the DSTv42 update for the Oracle Database (Doc ID 2941491.1)

If the Pre-Upgrade Information Tool instructed you to upgrade the time zone files after completing the database upgrade, then use the DBMS_DST PL
/SQL package to update the RDBMS DST (timezone) version.

Applying the DSTv42 update for the Oracle Database (Doc ID 2941491.1)

Important Notification

IMPORTANT

TIMEZONE UPGRADE PROCEDURE HAS CHANGED FROM JAN 2024

THE TIMEZONE PATCHES ARE INCLUDED IN DATABASE BUNDLE PATCH SINCE JANUARY 2023

OJVM TIMEZONE PATCH ARE SEPARATELY PROVIDED AND MUST BE APPLIED

YOU MUST UPGRADE THE DATABASE TIMEZONE WHEN UPGRADING THE DATABASE

Download Patches

6880880 x64 Bit OPatch 12.2.0.1.42 for DB 19.0.0.0.0 (Apr 2024 or later) Use Latest

35220732 x64 Bit RDBMS - DSTV42 UPDATE - TZDATA2023C Already included in DB Bundle Patch since JAN 2023

35239280 DSTV42 UPDATE - TZDATA2023C - NEED OJVM FIX NOT included in DB Bundle Patch

Download and extract all the patch to D:\Stage\<PATCHNUMBER>

Workaround / Solution to TZ Hanging

STARTING JAN 2024 THIS WORKAROUND SHOULD NO LONGER BE REQUIRED - BUT PROVIDED
BELOW IN CASE REQUIRED

Use with CAUTION.

Solution to TZ Hanging during CHECK and APPLY - Use with CAUTION

There have been issues where the CHECK or APPLY phase just hangs on 19c and seem to do Nothing

Attach the new version files in %ORACLE_HOME%\rdbms\admin (keep old backups)

And re run the TZ process from CHECK and APPLY.

DBMST_Utltz-Media_files-CPU-JAN-2024-TZ42.zip
Set Environment

set ORACLE_BASE=d:\oracle

set ORACLE_HOME=D:\ORACLE\1970

set ORACLE_SID=opera

set PERL5LIB=

set perlpath=

set PATH=D:\ORACLE\1970\bin;D:\ORACLE\1970\perl\bin;%PATH%

cd /D %ORACLE_HOME%\rdbms\admin

Check Current Time Zone File Version In DB Home


go to Directory %ORACLE_HOME%\oracore\zoneinfo and verify WHAT Timezone files exist

cd /d %ORACLE_HOME%\oracore\zoneinfo

dir timezone*.dat

dir timezlrg*.dat

Important : Make a note of the Last timezone***.dat and timezlrg***.dat files existing in the folder

Check Time Zone Details in Database Registry

SELECT * FROM v$timezone_file;

SELECT tz_version FROM registry$database;

COLUMN property_name FORMAT A30


COLUMN property_value FORMAT A20

SELECT property_name, property_value


FROM database_properties
WHERE property_name LIKE 'DST_%'
ORDER BY property_name;

SELECT DBMS_DST.get_latest_timezone_version FROM dual;

If TZ 42 Patch HAS NOT been applied If TZ 42 Patch HAS been Applied


You should see the latest version of the Timezone file in %oracle_home%\oracore\zonefile - It will NOT You should see THIS current version of the Timezone file
Necessarilty be the version you are applying. will be the version you are applying.

IMPORTANT

IMPORTANT

IF THE NEW TIMEZONE HAS ALREADY BEEN APPLIED

MOVE TO STEP "Post Tasks For OJVM"


Upgrade OPATCH (Latest)
Important - If the ABOVE output Shows the TIMEZONE Patch Has been applied no need to do this step

Ensure you have set Variables for ORACLE_HOME and ORACLE_SID

Verify OPATCH version

set oracle_home=d:\oracle\1970

CD /D %ORACLE_HOME%\bin

%ORACLE_HOME%\opatch\opatch version

Rename existing OPATCH folder - rename %ORACLE_HOME%\OPatch to %ORACLE_HOME%\OPatch_OLD

Copy the D:\Stage\6880880\Opatch folder to %ORACLE_HOME%\OPatch

verify OPATCH version

set oracle_home=d:\oracle\1970

CD /D %ORACLE_HOME%\bin

%ORACLE_HOME%\opatch\opatch version

Apply Timezone Patch 35220732 RDBMS - DSTV42 UPDATE - TZDATA2023C


Important - If the ABOVE output Shows the TIMEZONE Patch Has been applied no need to do this step

cd /d d:\stage\35220732

-- Check if applied
%oracle_home%\opatch\opatch lsinventory | findstr "35220732"

-- if not applied go ahead and apply


%oracle_home%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%oracle_home%\opatch\opatch apply -silent

%oracle_home%\opatch\opatch lsinventory | findstr "35220732"

Apply Timezone OJVM Patch 35239280 DSTV42 UPDATE - TZDATA2023E - NEED OJVM FIX
Important - If the ABOVE output Shows the TIMEZONE Patch Has been applied no need to do this step

cd /d d:\stage\35239280

-- Check if applied
%oracle_home%\opatch\opatch lspatches | findstr "35239280"

-- if not applied - go ahead and apply


%oracle_home%\opatch\opatch prereq CheckConflictAgainstOHWithDetail -ph ./

%oracle_home%\opatch\opatch apply -silent

%oracle_home%\opatch\opatch lspatches | findstr "35239280"


Check Patches applied

cd /d %ORACLE_HOME%\opatch

%ORACLE_HOME%\opatch\Opatch version

%ORACLE_HOME%\opatch\Opatch lspatches | findstr “35220732 35239280”

%ORACLE_HOME%\opatch\Opatch lsinventory | findstr “35220732 35239280”

Check Current Time Zone Version (In DB Home)


go to Directory %ORACLE_HOME%\oracore\zoneinfo and verify the Timezone files exist

cd /d %ORACLE_HOME%\oracore\zoneinfo

dir timezone*.dat

dir timezlrg*.dat

Check the timezone_42.dat and timezlrg_42.dat files existing in the folder

DO NOT PROCEED IF IT DOES NOT

Startup the Database in UPGRADE Mode

-- Restart Database upgrade


cd /d %ORACLE_HOME%\rdbms\admin

sqlplus / as sysdba

shutdown immediate

startup upgrade

Validate of the Latest File version from DB registry picked up from DB Home
Important - The OUTPUT should show the version of the TIMEZONE Patch you are applying - in this case TIMEZONE 42 is showing

--connect as SYS and run via SQLPLUS

SELECT DBMS_DST.get_latest_timezone_version FROM dual;


1. If above query DOES not reflect the NEW current version of the Timezone being upgraded - DO NOT PROCEED.

Validate of the Latest Filezone file version from DB Home


Important - The OUTPUT should show the cversion of the TIMEZONE Patch you applied - in this case TIMEZONE 42 was applied.

set oracle_home=d:\oracle\1970

dir %oracle_home%\oracore\zoneinfo\*42.dat

1. Check the latest Timezone files exist in %oracle_home%\oracore\zoneinfo


2. There WILL be two NEW files - If they don't exist in %oracle_home%\oracore\zoneinfo - DO NOT PROCEED.
a. timezlrg_42.dat
b. timezone_42.dat

Check Current Time Zone Version

SELECT * FROM v$timezone_file;

SELECT tz_version FROM registry$database;

COLUMN property_name FORMAT A30


COLUMN property_value FORMAT A20

SELECT property_name, property_value


FROM database_properties
WHERE property_name LIKE 'DST_%'
ORDER BY property_name;

SELECT DBMS_DST.get_latest_timezone_version FROM dual;

If TZ 42 Patch HAS NOT been applied If TZ 42 Patch HAS been Applied


You should see the latest version of the Timezone file in %oracle_home%\oracore\zonefile - It will NOT You should see THIS current version of the Timezone file
Necessarilty be the version you are applying. will be the version you are applying.

IMPORTANT

IMPORTANT

IF THE NEW TIMEZONE HAS ALREADY BEEN APPLIED

MOVE TO STEP "Post Tasks For OJVM"

Upgrade Timezone in Database


-- Spool the output
cd /d %ORACLE_HOME%\rdbms\admin

sqlplus / as sysdba

spool d:\stage\utltz_upg_check.log

-- Purge recyclebin
purge dba_recyclebin;

-- Stop the main jobs before running this command as it may not delete all the data from the DBMS_SCHEDULER
table, if some of the main jobs in a chain of jobs are still running.
exec dbms_scheduler.purge_log;

-- check the data retention period of the stats


-- the default value is 31
select systimestamp - dbms_stats.get_stats_history_availability from dual;

-- check the result of the purge operation


select count(*) from SYS.WRI$_OPTSTAT_HISTGRM_HISTORY;
select count(*) from SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY;

-- reduce stats retention to 7 days


exec dbms_stats.alter_stats_history_retention(7);

-- remove all the stats beyond 7 days


EXEC DBMS_STATS.PURGE_STATS( SYSDATE-7 );

-- Upgrade the Time Zone File Version After Upgrading Oracle Database

-- Script to gives how much TIMESTAMP WITH TIME ZONE data there is in a database using stats info. No restart
required.
@%ORACLE_HOME%\rdbms\admin\utltz_countstats.sql

-- Script to approximate how much TIMESTAMP WITH TIME ZONE data there is in a database using a COUNT(*) for
each table that has a TSTZ column.
-- This script is useful when using DBMS_DST package or the scripts of utlz_upg_check.sql and utlz_upg_apply.
sql scripts.
@%ORACLE_HOME%\rdbms\admin\utltz_countstar.sql

-- Run the utltz_upg_check.sql script from the $ORACLE_HOME directory:


@%ORACLE_HOME%\rdbms\admin\utltz_upg_check.sql

--Time zone apply script. Warning: This script will restart the database and adjust time zone data
@%ORACLE_HOME%\rdbms\admin\utltz_upg_apply.sql

select * from v$timezone_file;

-- You may set the data retention period back to its original value using the following command once the time
zone data upgrade is completed:
exec dbms_stats.alter_stats_history_retention(31);

spool off

Check Current Time Zone Version


SELECT * FROM v$timezone_file;

SELECT tz_version FROM registry$database;

COLUMN property_name FORMAT A30


COLUMN property_value FORMAT A20

SELECT property_name, property_value


FROM database_properties
WHERE property_name LIKE 'DST_%'
ORDER BY property_name;

Output - YOU MUST SEE THIS

Post Tasks For OJVM


Apply fixTZa

@?/javavm/admin/fixTZa.sql

If you see below....No Need to apply fixTZb (Next Step)


IMPORTANT

IMPORTANT

IF YOU SEE BELOW OUTPUT - NO NEED TO APPLY fixTZb IN THE NEXT STEP

########################################################
Bug is not present. Patch not needed.
########################################################

PL/SQL procedure successfully completed.

If you see below....Proceed to Next Step and APPLY fixTZb

IMPORTANT

IMPORTANT

IF YOU SEE BELOW OUTPUT - YOU MUST APPLY fixTZb IN THE NEXT STEP

########################################################
Bug is in fact present, so this patch is needed
Proceed by restarting the database and running script
fixTZb
########################################################

note that the "FAILED " messages are normal and part of the patching process and not an error/problem

If the output say to run fixTZb (it almost always will) then do:

Step1: If needed, edit init.ora and set cluster_database=FALSE


Step2: As SYS shutdown database: SQL> shutdown
Step3: Start the database in migrate: SQL> startup migrate
Step4: Execute the script SQL> $ORACLE_HOME/javavm/admin/fixTZb

Apply fixTZb

See example below - it is important to review output and then apply the next step if required

shutdown immediate

startup migrate

@?/javavm/admin/fixTZb.sql

shutdown immediate

startup

--- Sample Output


SQL> @?/javavm/admin/fixTZa.sql

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Java created.

No errors.

Java altered.

No errors.

Package created.

No errors.

Package body created.

No errors.

PL/SQL procedure successfully completed.

Call completed.

Testing various timezone DST attributes


FAILED for Pacific/Auckland 10:0:0 10/1/2007
FAILED for Pacific/Chatham 10:0:0 10/1/2007
FAILED for Pacific/Auckland 10:0:0 4/1/2008
...
FAILED for Pacific/Chatham 1396706399999 45900000 3900000
FAILED for Pacific/Chatham 1411826400000 45900000 3900000
##
Bug is in fact present, so this patch is needed
##
(Perhaps) modifying ild_ub1$ for rehotloading of sun/util/calendar/ZoneInfoFile
obj# = 432434
nbytes %d = 64512, 1st read = 64512, 2nd read = -1
87 379782 399648 2203701434 joxbtflag>>8 = 3
===

PL/SQL procedure successfully completed.

########################################################
Bug is in fact present, so this patch is needed
Proceed by restarting the database and running script
fixTZb
########################################################

note that the "FAILED " messages are normal and part of the patching process and not an error/problem

If the output say to run fixTZb (it almost always will) then do:

Step1: If needed, edit init.ora and set cluster_database=FALSE


Step2: As SYS shutdown database: SQL> shutdown
Step3: Start the database in migrate: SQL> startup migrate
Step4: Execute the script SQL> $ORACLE_HOME/javavm/admin/fixTZb
SQL> @?/javavm/admin/fixTZb.sql

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Call completed.

Testing various timezone DST attributes


########################################################
Bug is no longer present. Patch succeeded.
########################################################

PL/SQL procedure successfully completed.

drop java source fixTZ

drop package fixTZ

PL/SQL procedure successfully completed.

Timezone Upgrade Complete


Timezone upgrade to 42 is completed

Re Verify patches Applied


set pages 999
set lines 150
Column ActionTime heading 'Action Time' format a15
Column Action heading 'Action' format a15
Column Details heading 'Details' format a100
select to_char(action_time,'RRRR-MM-DD HH24:MI') ActionTime,
ltrim(rtrim(action)) Action,
' P# '||ltrim(rtrim(to_char(patch_ID)))||' '||ltrim(rtrim(description)) Details
from registry$sqlpatch order by 1;

Output may differ depending on the upgrade paths

Verify your PATCH numbers exist in below output - Shows all patches APPLIED in last 24 Hrs

set lines 150


Column ActionTime heading 'Action Time' format a15
Column Action heading 'Action' format a15
Column Details heading 'Details' format a100
select to_char(action_time,'RRRR-MM-DD HH24:MI') ActionTime,
ltrim(rtrim(action)) Action,
' P# '||ltrim(rtrim(to_char(patch_ID)))||' '||ltrim(rtrim(description)) Details
from registry$sqlpatch where action_time > sysdate-1;

Recompile and check component


Alter system flush shared_pool;
@?/rdbms/admin/utlrp.sql

Column comp_name heading 'Component' format a50


Column version heading 'Version' format a15
Column status heading 'Status' format a15
select comp_name,version,status from dba_registry;

Granting Java permission ON sun.misc classes TO OPERA AND SYNONYM schemas (OPTION
AL)
Applicable ONLY if OPERA Database is being Patched

select instance_name from v$instance;

BEGIN
FOR rec IN (
SELECT OWNER AS grantee
,object_type
FROM dba_objects
WHERE object_name = 'PMS_P'
AND object_type = 'PACKAGE'
ORDER BY 1
)
LOOP dbms_java.grant_permission(rec.grantee, 'SYS:java.security.SecurityPermission', 'sun.misc.
BASE64Decoder', '');
dbms_java.grant_permission(rec.grantee, 'SYS:java.security.SecurityPermission', 'sun.misc.
BASE64Encoder', '');
EXECUTE IMMEDIATE 'begin ' || rec.grantee || '.register_sql_script(''v520150107_osg_java_perm.
sql''); end;';
END LOOP;
END;
/

Alter system flush shared_pool;


@?/rdbms/admin/utlrp.sql

Check for Invalid Objects there should be NONE.

Update ANYDATASET
select instance_name from v$instance;

SET echo off


SET feedback off
SET term off
SET pagesize 0
SET linesize 80
SET newpage 0
SET space 0
spool c:\temp\upgrd.SQL
SELECT DISTINCT 'alter table '||owner||'.'||table_name||' upgrade;' FROM DBA_TAB_COLUMNS b WHERE
DATA_TYPE='ANYDATASET';
spool OFF
spool c:\temp\upgradeinfo.log
@@c:\temp\upgrd.sql
spool off
SET term on
SET feedback on

@?/rdbms/admin/utlrp.sql
Resource Plan Scheduler
select instance_name from v$instance;

select * from DBA_SCHEDULER_GLOBAL_ATTRIBUTE where attribute_name='CURRENT_OPEN_WINDOW';

exec DBMS_SCHEDULER.close_window ('WEEKNIGHT_WINDOW');


exec DBMS_SCHEDULER.close_window ('WEEKEND_WINDOW');

execute dbms_scheduler.set_attribute('WEEKNIGHT_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('WEEKEND_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('MONDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('TUESDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('WEDNESDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('THURSDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('FRIDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('SATURDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('SUNDAY_WINDOW','RESOURCE_PLAN','');
COMMIT;

Modify Stats
select instance_name from v$instance;

exec dbms_stats.set_param('METHOD_OPT','FOR ALL COLUMNS SIZE 1')


exec dbms_stats.set_param('CASCADE','TRUE')
exec dbms_stats.set_param('ESTIMATE_PERCENT','100');
select dbms_stats.get_param('METHOD_OPT') from dual;
select dbms_stats.get_param('cascade') from dual;
select dbms_stats.get_param('ESTIMATE_PERCENT') from dual;

Revert ini / spfile Changes


If parameters were updated BEFORE upgrade - these can now be reverted back.

Media Default INIT / SP File Custom Tweksed INIT / SP File

If below parameters were disabled BEFORE If below parameters were disabled BEFORE upgrade - re enable them.
upgrade - re enable them.
deferred_segment_creation=false # for using exp/imp
*._optim_peek_user_binds=FALSE plsql_optimize_level=1 # fix for plsql table to return correct
*.plsql_optimize_level=1 results, pending Oracle bug fix
*.deferred_segment_creation=FALSE _optim_peek_user_binds=FALSE

_kill_enqueue_blocker=1
_optimizer_complex_pred_selectivity=false
_enable_shared_pool_durations=FALSE

Other Parameters

job_queue_processes=64
aq_tm_processes=1
Compatible=19.0.0
shared_pool_reserved_size = 6553600

Instance Startup AUTO


cd /D %ORACLE_HOME%\database

oradim -edit -sid opera -startmode a

Restart services and validate


cd /D %ORACLE_HOME%\rdbms\admin

sqlplus / as sysdba

select instance_name from v$instance;

shutdown immediate

start from windows service to ensure DB comes up

Modify INIT / SPFILE Parameters


If parameters were updated BEFORE upgrade - these can now be reverted back.

Media Default INIT / SP File Custom Tweksed INIT / SP File

If below parameters were disabled BEFORE If below parameters were disabled BEFORE upgrade - re enable them.
upgrade - re enable them.
deferred_segment_creation=false # for using exp/imp
*._optim_peek_user_binds=FALSE plsql_optimize_level=1 # fix for plsql table to return correct
*.plsql_optimize_level=1 results, pending Oracle bug fix
*.deferred_segment_creation=FALSE _optim_peek_user_binds=FALSE

_kill_enqueue_blocker=1
_optimizer_complex_pred_selectivity=false
_enable_shared_pool_durations=FALSE

Other Services
Start the Windows Management Instrumentation again if desired.

sc config Winmgmt start= demand


net start winmgmt /y

Verify & Test DB Connectivity


Restart Services

Open SQLPLUS and ensure you can connect to the Database successfully.

Check no invalid objects exist and operations perform as per expectation

The Database is now upgraded to latest 19.x Patch Level

You might also like