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

This article introduces the relevant knowledge of "what are the knowledge and terms related to Oracle patches?" in the operation of actual cases, many people will encounter such a dilemma, and then let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

1. PSU introduction

Patch Set Updates (PSU) is a collection of Oracle patches and an active patch for Oracle.

An PSU has the following characteristics:

-PSU is a cumulative collection of patches

-publish one quarterly (quarterly plan)

-highly controlled and selected content

-including CPU (Critical Patch Update) security fixes

-does not include feature enhancements

-follow the patch-level error correction strategy on which PSU is based

PSU is a collection of patches, and PSU and CPU (critical patch updates) make the same quarterly progress, approaching the Tuesday of January, April, July, and October, respectively.

2. PSU applicable products

-Oracle database

-Oracle Grid infrastructure

-Cluster Ready Services

-Enterprise Manager

-Weblogic Server

-Exalogic

3. PSU features and benefits

1) low risk and high value

The risk of PSU is low, mainly through content control and in-depth testing. Including Bug repair criteria:

-Technical issues that may affect a large number of customers and have been validated

-CPU (Critical Patch Update) repair

Each PSU has something new, usually containing 25-100 bug fixes. The content is found in issues that advanced customers download and develop and support for resolution.

2) Integrated and good testing patches

-by including patch recommendations in a patch. Oracle conducts thorough regression testing of each PSU in order to ensure that the recommended patches work well.

3) baseline version for easy tracking

Oracle associates the version number with the patch, and each PSU increases the fifth number of the database. For example, the initial PSU is 11.2.0.4.1 and the second PSU version is 11.2.0.4.2. and so on.

4. PSU and CPU

The full name of CPU means Critical Patch Update,Oracle releases a security patch package every quarter to fix security vulnerabilities in the product.

PSU contains key patches related to security issues, as well as key patches that are not related to security issues. Therefore, PSU is included in critical patch updates (CPU), but is not limited to CPU. PSU is usually released with CPU.

CPU is cumulative. The latest CPU patch already contains previous CPU patches, so just install the latest CPU patch.

PSU is usually incremental, and most PSU can be installed directly, but some PSU must be installed after the previous version of PSU. Please read the readme documentation carefully before installing PSU.

5. Changes in patch number

Starting from 2016, the fifth place of the version number of database-related PSU/SPU/BP has changed, for example, the next version of 11.2.0.4.8 is no longer 11.2.0.4.9, but 11.2.0.4.160119, and the format is YYMMDD related to the release date.

6. One-off patch

There are two types of patches for Oracle databases:

One is proactive patches (oracle updates periodically), including PSU/SPU/CPU/BP; (CPU renamed to SPU)

One is a passive patch (when the user discovers BUG, it is fixed by oracle), only one-off patch.

Therefore, one-off patch is generated only to modify a certain Bug.

Since 12c, Oracle has provided another patch type called DBBP. Before 12c, at least the corresponding version of PSU is installed, but if you want to install a more complete patch set after 12c, you should choose DBBP.

7. SPU/CPU changes

Starting from 12c, it is also easier for databases to provide security-related fixes that are no longer released as SPU alone, but as centralized fixes in the form of PSU or DBBP packages.

8. BP for exadata and dbim changes

Since April 2016, "database patch for engineered systems and database in-memory bundle patch (BP)" has been renamed to "database procative bundle patch (DBBP)" and is no longer limited to EXADATA systems. DBBP is a superset of multiple PSU, including the related fixes of GI PSU/DB PSU/EXADATA/DBIM. In other words, DBBP can be applied to all database environments since 12c, and DBBP is limited to Linux and UNIX systems, not windows systems. The windows platform continues to use BP.

9. Download address of all patches

Mos Doc ID 2118136.2

Note: SPU,PSU,DBBP is not compatible. Check for conflicts when changing patches and roll back previous conflicts. The installation of DBBP cannot be based on the PSU of the previous quarter.

10. Terminology for patches

1) Patch Set Release

It's what people used to say in the early days, PSR. This is a patch set released on the major version number, and the fourth field of the version, such as 11.2.0.4, fixes more Bug and may include some enhancements. For example, 11.2.0.1 is a major version, then 11.2.0.2 and 11.2.0.3 are two different Patch set. This patch set has undergone rigorous integration testing and is cumulative. Therefore, it is recommended to install the latest Patch Set.

2) Patch Set Update

That is, DBA often talk about the PSU.Oracle selection that users download the most in each quarter, and the patches that have been verified to have lower risk are put into the PSU every quarter to fix some of the more serious problems, including the CPU of each quarter, which is cumulative. Important fixes for databases and database clients. Includes security (CPU) content. There is no optimizer fix, although the 5th position of the database version will be used when describing PSU, but in fact, the version of the database will not really be changed after typing PSU, which needs to be confirmed from opatch lsinv.

Be careful

(1) there is no CPU and PSU on Windows. Using Bundle Patch instead of PSU,Bundle Patch for Windows and Exadata,Oracle will include the content of PSU.

(2) before 11G, some PSU can be installed directly, while some PSU must be installed after the previous version of PSU can be installed. For example, for the 10.2.0.4 database, PSU 10.2.0.4.4 can be installed directly in the original 10.2.0.4.0 version, while the latest PSU 10.2.0.4.8 must be installed first. For more information, see the readme.txt that comes with PSU.

(3) starting from version 11.2.0.2, a new patch strategy has been introduced, and the Patch Set released after 11.2.0.1 is itself a complete installation package, and the basic Release version installation is no longer required.

3) Grid Infrastructure Patch Set Update

Also known as GI PSU, RAC DB above 11.2.0.1 is installed on the Unix platform (including single instance RAC). The patch includes important fixes for Grid Infrastructure, as well as matching DB PSU, but does not include any OJVM PSU, quarterly release, called CRS PSU before 11.2, and no release since 11.2.

4) OJVM Patch Set Update

That is, OJVM PSU, applicable to all platforms above the database version DB version 11.1.0.7 and 11.2.0.3, 11.2.0.4 and 12.1.0.1. Note that the Windows platform has a special OJVM PSU overlay patch installed on Windows BP

OJVM PSU was introduced in October 2014, but OJVM and JDBC have separate patches. After January 2015, OJVM PSU including JDBC fixes for databases

OJVM PSU is included in DBBP in 12c

5) Timezone Patches

For DB and DB client installations, when there is a high demand for the latest time zone data, the patch contains only time zone data and is released every six months.

6) Critical Patch Update

The product security update strategy introduced by Oracle in 2005, the earliest prototype of CPU appeared in 2005, the project aims to provide customers with cumulative patches periodically to fix security vulnerabilities. There is no reason to force the installation of CPU. Oracle simply strongly recommends the implementation of these patches to reduce potential security risks and reduce the probability of successful hacker intrusion, as specified by the month / year, such as 11.2.0.4 Jan 2015 SPU.

This refers to the CPU patch. Released quarterly, some of the patches used to fix security are cumulative. Now it has been renamed Security Patch Update (SPU).

PSU contains the latest CPU. Starting from 12.1.0.1, CPU is no longer released separately but is included in the PSU release.

7) One-Off Patch

It is what we often call a small patch, a patch released to fix one (or several) Bug. This patch is recommended to be tested on the test library and then installed on the production library.

8) Merged Patch

Merged patches. This Merged Patch is required when there is a conflict between several small patches and cannot be installed at the same time. Patch conflicts are mainly due to two or more patches that modify the same file, but the contents of the changes are different.

9) Quarterly Full Stack Download Patch / Combo Patch

Several different patches are packaged and released together, applicable to DB version 11.1.0.7, 11.2.0.3 and above, and has been released quarterly since October 2014, with Patch Set Updates of different components included in one download.

10) Windows Bundle Patch (BP)

The patch set for WINDOWS platforms only fixes multiple Bug. There are no small patches for Oracle on the Windows platform, only this Bundle Patch. This cumulative patch is released periodically (at least quarterly), meaning that each Bundle Patch contains all previous Bundle Patch. Windows Bundle Patch 16, for example, will contain all the previous 15 Bundle Patch, so we always recommend installing the latest Bundle Patch. The Window Bundle Patch of Oracle's cluster software is the same as that of database software, such as Windows Bundle Patch 16 (patch number 16167942, which can be used either on the cluster or on the database), which contains DB PSU and OJVM PSU content every quarter.

10) Diagnostic Patch

Diagnostic patch. As the name implies, such patches are not used to solve the problem, but to find the cause of the problem. Such patches need to be installed only when required by Oracle Technical support. You should uninstall this patch as soon as you get the diagnostic information you need.

11) Composite Patch

Starting with Database PSU 11.2.0.3.2 and 11.2.0.2.0.7 in April 2012, a new concept called Composite Patches has been introduced. This is a new type of patch package, which is different from other cumulative patch packs. If you install Composite Patches for the first time, all the patches included in the Composite Patches will be installed, and the subsequent installation of Composite Patches will only install the changes and new patches compared to the previous Composite Patches.

12) Database Patch for Exadata

Also known as EXADBBP or BP, only for exadata machine ORACLE 11G, monthly release, monthly important BP will be placed in this quarter's Quarterly Full Stack Download Patch for Exadata

13) Quarterly Full Stack Download Patch for Exadata

QFSDP for Exadata, also available only for EXADATA MACHINE ORACLE 11G, is released quarterly, including database patches on Exadata and patches for other Exadata components.

Not available for non-EXADATA systems. Most updates are released specifically for Bundle patches created by Oracle Database (DB_BP) and Oracle Clusterware (GI_BP) on Exadata. Bundle patches does not contain Exadata-specific code, but these patches can only be installed on Exadata systems for testing purposes or for disaster recovery support for non-Exadata systems. Only when the non-Exadata system is used as a standby system for the Exadata system in the Data Guard environment does Oracle provide a temporary fix to the non-Exadata system based on Exadata bundle patches.

14) Database Proactive Bundle Patch

It is suitable for 12c database installation on Exadata, as well as for any 12c system, RAC or non-RAC that uses Database In-Memory (DBIM) features. Database and Grid home are also applicable. It is only used for 12.1.0.2 and above DB on linux/unix platforms. From 1937782.1, we can see that all patches before April 2016 are called for Engineered Systems and DB In-Memory, and the release cycle is once a month. As of April 2016, Database Patch for Engineered Systems and Database In-Memory has been renamed "Database Proactive Bundle Patch" and is no longer limited to Engineered Systems and DB In-Memory. It can also be used for EXADATA and non-EXADATA, and RAC and non-RAC systems. Released quarterly, it becomes a new quarterly patch and cumulative, and the fifth field of the version specifies that "Database Proactive Bundle Patch" requires a little more testing than Patch Set Update (PSU) because it provides a large number of fixes.

DBBP is a superset of PSU. BP contains increments such as 10, including 1-9, as well as the most recent PSU and CPU when creating BP, so it is recommended to install the latest BP, which precisely includes the problem fixed by PSU,CPU.

The important point is that 12C DBBP is not directly related to the previous "Windows Bundle Patch" (BP), windows continues to use the previous WINDOWS BP.

Although DBBP contains multiple PSU and BUG FIXED, DBBP cannot continue to install based on the PSU of the previous quarter, and vice versa, so if switching between DBBP and PSU patch installation technology requires rollback conflicting PSU in advance, this requires more time windows and downtime.

If you download DBBP and PSU of the same period, you will find that the sub-patches are mutually exclusive. In the readme of DBBP, you will see that DBBP contains all PSU and CPU incrementally. Although the sub-patch number is different, you will find that DBBP contains all the BUG repaired by PSU during the same period when you use opatch lsinventory-bugs_fixed after installation. You can also find some fixed BUG in DBBP, but not in PSU.

This is the end of the content of "what is the knowledge and terminology related to the Oracle patch". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

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.