Shulou(Shulou.com)05/31 Report--

This article mainly introduces "how to understand the Oracle patch system and its iterative phase". In the daily operation, I believe many people have doubts about how to understand the Oracle patch system and its iterative phase. The editor consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful to answer the doubts of "how to understand the Oracle patch system and its iterative phase". Next, please follow the editor to study!

Patch introduction

Reactive patch

Reactive patch is what we often call temporary patches, that is, in daily operation and maintenance, the database triggers bug in specific scenarios. Based on the description and stack information in the generated trace, combined with the basic information such as the version and operating system of the database, we retrieve it in the Oracle official document library (metalink) to obtain the patch for solving bug.

Proactive patch

In Proactive patch, PSU is the most commonly used before 12c2. When you deploy a new environment, you should use the newly released PSU to improve the stability of the database launched in the future. In addition, after security vulnerability scanning, hit PSU (because SPU is already included in PSU).

After 12c2, PSU disappeared and was replaced by RU.

Release Update (RU) is defined as a quarterly cumulative proactive (Proactive) patch for the annual version (Annual Releases) that contains tested security and non-security patches.

Release Update Revision (RUR) is defined as quarterly cumulative proactive patches that include security and regression fixes for RU, extending the life cycle of RU by half a year. RUR replaces SPU.

Six months after each update is released, there will be revisions for that update: RU.1 and RU.2 (red mark in the following figure).

Oracle officials use the following chart to further illustrate the iterative relationship between time-version number-patch.

For the same version of the patch, the collection size can be represented by the following figure:

Three patch versions (for example, 18.4.0, 18.3.1, and 18.2.2) released for the same time node (July / October of each year) have exactly the same up-to-date information, security vulnerability fixes. However, only update (18.4) has the latest non-secure bug fixes. The size of the collection is shown in the following figure:

(patch set size at the same time)

If you want to deploy 19c in the near future, it is recommended to use the version 19.3 installation media released by Oracle, and then use the patch tool to apply the new 19.6 patch (patchid:30557433) released in January 2020.

The patch is named Database Release Update 19.6.0.0.200114, and the last 200114 is the date the patch was created, in the format of YYMMDD, January 14, 2020.

On January 14, 2020, Oracle officially launched the following patches for the first quarter of the database:

Prior to 12.2, the relationship between patches and versions was limited to space, which is briefly shown in the following table:

Finally, attach the patch roadmap officially given by Oracle:

At this point, the study on "how to understand the Oracle patch system and its iterative phase" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.