Related to Oracle patches

Naming rules for 1.Oracle software version

Main database release number, database maintenance release number, application server release number, component-related release number, platform-related release number. The fourth is patch set, and the fifth is patch set update.

two。 Classification of versions and patches

2.1 version version

After a period of time, Oracle will sort out all the patches for the previous version, add new features or major changes, conduct overall testing, and get a software version package called version, such as 10.2.

2.2 Patch set Patch Set

A set of fully tested cumulative fixes released between two product releases, such as 10.2.0.4, 10.2.0.5

2.3 critical patch update/ key patch update CPU

A set of high-priority fixes provided quarterly (usually for security issues) that are cumulative for previous security fixes, but can also include other fixes designed to resolve patch conflicts with non-security patches (reducing the need for merge requests)

2.4 Patch Set Update patch set update PSU

Starting from 10.2.0.4, it will be released between two patch sets, four times a year. Each update of the Boding set contains 50-100 fixes, and will be released after testing and integration, such as 10.2.0.4.1, 10.2.0.4.2.

2.5 CRS Bundle Patch Cluster Software Patch set

Patches specifically designed to fix Oracle cluster, released as cumulative patches.

3. Terminology related to version management and patch implementation

Large version upgrade (upgrade) refers to the improvement and enrichment of RDBMS software functions and features similar to the upgrade of database major version number from 9.2 to 10.2.

For operations from 10.2.0.2 to 10.2.0.3, Oracle is called patch pack upgrade (update). The patch pack does not add new features, but will

Various patches after 10.2.0.2, such as one-off patch, merge patch, etc., release a new patch pack that covers existing patches and resolves various patch conflicts after integration testing and verification.

Recommended patches issued by Oracle should be applied periodically

Proactive patch implementation strategy

Update regularly according to monthly, quarterly, annual and other time periods

Which patches need to be installed in the first proactive analysis

Second, how to analyze and resolve patch conflicts

The patch conflict is that both patches modify the same file of the database software.