Oracle Critical Database Patch ID for January 2024 along with enabled Download Link

January 19, 2024
()

Oracle Critical Database Patch ID for January 2024 along with enabled Download Link


An Essential/Critical Patch Update could be a collection of patches for multiple security vulnerabilities. These patches address vulnerabilities in Oracle code and third-party elements enclosed in Oracle merchandise. These patches are sometimes additive, however every informative describes only the protection patches intercalary since the previous essential Patch Update informative.

Below is the list of Oracle Critical Patch IDs for all versions (21c, 19c) of Grid & Databases along with combo PSU, EXADATA, and SUPERCLUSTER patch IDs for January 2024. All patch IDs are enabled with the direct download link.


Version 21c (21.0.0.0)

Patch IDDatabase ReleasePatch TypeAvailable Date (ETA)
3603179021.13.0.0.240116GRID (UNIX)30.JAN.2024
3604122221.13.0.0.240116DATABASE (UNIX)30.JAN.2024
36031748Q FULL STACK 21.13.0 (Jan.2024)EXADATA (LINUX 64 BIT)22.JAN.2024
3596285721.13.0.0.240116MS WINDOWS BP (32 & 64 BIT)30.JAN.2024
3604122221.13.0.0.240116CLIENT (UNIX)30.JAN.2024
21c: Oracle Critical Patches Jan, 24


Version 19c (19.0.0.0)

Patch IDDatabase ReleasePatch TypeAvailable Date (ETA)
3603145319.22.0.0.240116Combo OJVM plus GRID (UNIX)25.JAN.2024
3594098919.22.0.0.240116GRID (UNIX)25.JAN.2024
36031426 19.22.0.0.240116Combo OJVM plus DATABASE (UNIX)30.JAN.2024
3594315719.22.0.0.240116DATABASE (UNIX)30.JAN.2024
3596283219.22.0.0.240116MS WINDOWS BP (32 & 64 BIT)30.JAN.2024
36031733Q FULL STACK 19.22.0 (Jan.2024)EXADATA (UNIX)30.JAN.2024
36031759Q Full Stack SuperCluster (Q1.2024)SOLARIS SPARC 64-Bit07.MAR.2024
3592664619.22.0.0.240116OJVM (All Platform)30.JAN.2024
3594315719.22.0.0.240116CLIENT (UNIX)30.JAN.2024
3596283219.22.0.0.240116MS WINDOWS CLIENT(32 & 64 BIT)30.JAN.2024
19c: Oracle Critical Patches Jan, 24


Click here to read about Steps to Apply Combo Patch on Clusterware in Two Node RAC in Oracle.


The next four dates for Critical Patch Updates are:

  • 16th Apr 2024
  • 16th Jul 2024
  • 15th Oct 2024
  • 21st Jan 2025

Click here to get patching-related articles.


Key points to remember:

**All patch IDs are enabled with the direct download link.
**To download patches you need valid credentials of Oracle support/Metalink.

**All patch IDs are provided by Oracle, visit DOC ID 2966413.1

**Most patches are revealed for platform Linux except Exadata and Supercluster, a few platforms are to be revealed soon, refer to the above tables for ETA.

**21c does not have COMBO or OJVM patches. Instead, the OJVM fixes are contained within the DB RU and the GU RU patches.
**Team DBsGuru is not chargeable for patch transfer/download to apply or any error occurs while the patch applies, so transfer/download the proper patch for the desired version and platform.

** Oracle client home patch ID is the same patch ID as Oracle database server home-specific platform UNIX or WINDOWS i.e applicable on both.

**Always suggest reviewing patch readme, specific to patch ID before applying.

**Feel free to reach us for any help/suggestion required on the patch, drop your valuable concerns/suggestions within the comment/chat section.
**Click here to get patch delivery methods for 12.2.0.1 and greater (Doc ID 2337415.1).
**Click here to get patch delivery methods for 12.1.0.2 and order (Doc ID Note 1962125.1).

**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.

**Frequent access to recommended and well-tested collections of patches, Oracle is introducing 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 more details.

**Feel free to reach us for any help/suggestion required on the patch, drop your valuable concerns/suggestions within the comment/chat section.


This document is just for learning purposes and always validate in the LAB environment first before applying it in the LIVE environment.


Hope so you like this article
!
Please share your valuable feedback/comments/subscribe and follow us below and don’t forget to click on the bell icon to get the most recent update. Click here to understand more about our pursuit.

Related Articles

Loading

How useful was this post?

Click on a star to rate it!

Average rating / 5. Vote count:

No votes so far! Be the first to rate this post.

As you found this post useful...

Follow us on social media!

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

<strong>Hello and welcome to DBsGuru,</strong>DBsGuru is a group of experienced DBA professionals and serves databases and their related community by providing technical blogs, projects, training. Technical blogs are the source of vast information not about databases but its related product like middleware, PL/SQL, replication methodology, and so on.Thanks for the visits!<strong>Share Learn Grow!</strong>

Leave a Reply

Your email address will not be published. Required fields are marked *