2020

ORACLE FUSION MIDDLEWARE

Error Correction Policy

VERSION 1.1
10-DEC-2021

ORACLE CORPORATION | [Company address]

1 CONTENTS
2 Overview .......................................................................................................................................... 3

2.1 Basic Concepts ................................................................................................................................... 3

2.1.1 What is Error Correction Policy? ............................................................................................... 3
2.1.2 What is Grace Period? ................................................................................................................ 3

2.2 Release Model .................................................................................................................................... 5

2.2.1 Major Release ............................................................................................................................ 5
2.2.2 Patch Set releases ....................................................................................................................... 5
2.2.3 Long Term Support (LTS) ......................................................................................................... 5
2.2.4 Proactive Patching ...................................................................................................................... 5
3 Fusion Middleware insights ............................................................................................................... 6
4 Error Correction Policy Details .......................................................................................................... 7
5 Terminology ....................................................................................................................................... 8
6 Patch Sets ......................................................................................................................................... 10

6.1 Definition ......................................................................................................................................... 10

6.2 Policies ............................................................................................................................................. 10

6.2.1 For Which Patch Set releases Will New Fixes Be Created? .................................................... 10
6.2.2 Patch Sets Releases Only For Premier Supported Releases ..................................................... 11
6.2.3 Regressions Due To Patch Sets ................................................................................................ 11
6.2.4 Not All Patch Sets Ported to Every Platform............................................................................ 11
7 Proactive Patching (Quarterly Patch Set Updates, Bundle Patches) ............................................... 12

7.1 Definitions ........................................................................................................................................ 12

7.1.1 Security Patch Updates ............................................................................................................. 12
7.1.2 Testing ...................................................................................................................................... 12
7.1.3 Scope ........................................................................................................................................ 12
7.1.4 Patch Set Updates ..................................................................................................................... 13
7.1.5 Recommended Patches ............................................................................................................. 13

Error Correction Policy Oracle Corporation 10-Dec-2021 Page 1

7.2 Policies – Critical Patch Update Program ............................................................................ 14
7.2.1 Which Patch Set Versions Are Covered by the CPU Program? .............................................. 14
7.2.2 Patch Conflict Resolution for SPUs ......................................................................................... 14

7.3 Policies – Patch Set Updates ............................................................................................................ 14

7.3.1 For Which Patch Set Versions Will a PSU be created?............................................................ 14
7.3.2 For Which PSUs Can Interim Patches Be Created? ................................................................. 14
7.3.3 Conflicts between PSUs and Previously Installed Interim Patches .......................................... 15
7.3.4 Requested Patches Not Included In Future PSUs .................................................................... 15
8 Interim Patches ................................................................................................................................. 16

8.1 Definition ......................................................................................................................................... 16

8.1.1 Testing ..................................................................................................................................... 16
8.1.2 Policies .................................................................................................................................... 16
9 Diagnostic Patches ........................................................................................................................... 20

9.1 Definition ......................................................................................................................................... 20

9.2 Policies ............................................................................................................................................. 20

9.2.1 Install Only On Problem System .............................................................................................. 20
9.2.2 Diagnostic Patches Created On All Versions ........................................................................... 20
9.2.3 Remove Diagnostic Patches after Problem Resolution ............................................................ 20

9.3 History .............................................................................................................................................. 20

Error Correction Policy Oracle Corporation 10-Dec-2021 Page 2

2 OVERVIEW

2.1 BASIC CONCEPTS

The Lifetime Support Policy (LSP) defines the type of support delivered during each support
phase (Premier, Extended, and Sustaining) of a product’s lifecycle.
This Error Correction Policy documents the details on delivering fixes during the LSP phases
and establishes policies for generating new fixes based on the defined grace periods.
As a general rule, Oracle provides patches for products when they are still covered under the
error correction grace period.
All products and versions in the LSP are subject to this ECP as a release progresses through a
release lifecycle.
In most products, LSP windows are set at the Major release level.

2.1.1 What is Error Correction Policy?

LSP provides dates for Premier, Extended & Sustaining support policies.
This date holds good for the latest release versions of various products that are under the
respective support policy.
ECP comes into picture only for the intermediate releases. The Error Correction Policy defines
a grace period and date when an intermediate release expires error correction support.
It is important to note that, the ECP date may be before the end of Premier or Extended
Support.

This document applies to Oracle Fusion Middleware (including former BEA products).
Refer to release documentation to determine the products and options included based on
version.
At this time Sun Software products such as Solaris, iPlanet, and Java are not covered under
this ECP policy.

2.1.2 What is Grace Period?

Grace Period is the period of time following a new release where Oracle will create patches
for both the new release and previous versions that fall within a certain grace period window.
This allows customers time to plan for and install the latest version and receive patches while
the upgrade is in process.
Grace periods vary by product.

Error Correction Policy Oracle Corporation 10-Dec-2021 Page 3

 Figure 1 is an illustration of the grace period for a FMW patch set release 12.2.1.2,
showing the release dates and overlap of maintenance for the previous patch set release.

October 2016 - August 2018

Error Correction Patching for FMW 12.2.1.2
Figure 1 Grace Period for FMW release
The above example depicts timelines when LSP & ECP dates are considered.

As of Oct 2016, 12.2.1.2 is the latest release & LSP dates apply at that point in time.

Once 12.2.1.3 is released, the LSP dates no longer apply to 12.2.1.2.

The Grace Period date is then in effect.

It is important to note that LSP dates are always associated with the latest release only.

For ECP dates of FMW 12.2.x releases, refer to MOS Notes : 1933372.1.

Refer to Section 4 for individual product ECP details.

Error Correction Policy Oracle Corporation 10-Dec-2021 Page 4

2.2 RELEASE MODEL

Oracle FMW Products uses the below release model:

2.2.1 Major Release

Major Releases are new releases that have a significant set of new feature or architectural
changes. Major releases historically release about every 3 to 5 years with interim
Patch Set releases releasing in between each major release. (E.g. FMW 12.2.1)

2.2.2 Patch Set releases

Patch Set releases are integrated, cumulative, fully tested collections of bug fixes or
enhancements issued in between major releases. Patch Set releases include the
major release in their versioning scheme (e.g. 12.2.1.4 is a patch set of release 12.2.1).
Patch Set can be an update to an existing set of binaries on some releases and versions.
In newer FMW releases, these are distributed as new installations with an upgrade option.
In all cases, they are signified by the 4th digit unless otherwise noted.
Herein, these may be referred to as “Patch Set releases” whether they are an update,
upgrade, or new installation.

2.2.3 Long Term Support (LTS)

Long Term Support (LTS) is defined as a final intermediate or maintenance release

in a release series, (e.g. 12.2.x). After Grace Periods expire on previous maintenance
releases, as per the Error Correction Policy, an LTS release is the one eligible for all benefits,
(including error correction support), outlined under Premier and Extended Support
as defined in the Lifetime Support Policy.

2.2.4 Proactive Patching

Recommended Proactive Patching involves Patch Set Updates (PSUs) and

Security Patch Updates (SPUs) delivered quarterly and contain well-tested,
important fixes that should be part of every proactive maintenance strategy.

Error Correction Policy Oracle Corporation 10-Dec-2021 Page 5

3 FUSION MIDDLEWARE INSIGHTS

Fusion Middleware 12c minor releases:

The release cycle for Oracle Fusion Middleware 12c releases minor releases
(aka Patch Set releases) which are feature bearing and distinguished by a change
in the 4th place of the version number (e.g. 12.2.1.3 and 12.2.1.4).
Proactive patches (e.g. Patch Set Updates, Security Patch Updates, and Bundle Patches) will be
released quarterly as required.
Grace Period: 1 year
Oracle will continue to make new patches available for the preceding patch set (n-1) for one
year from release of a new patch set release. After that it is required to install the new patch
set in order to get new fixes.
For details (including links to documents containing error correction dates for specific products
and patch set releases), see Error Correction Support Dates for Oracle Fusion Middleware
(10g/11g/WLS) (Doc ID 944866.1).
For a full definition of the grace period for patch set releases, see section 6.2.1.
Exceptions:
Grace Period extensions:
The error correction period for:
 FMW 12.2.1.3 has been extended from Sep 2020 through Dec 2022. During this
timeframe, content will be limited to :
o Sev 1 production impacting fixes that cannot be resolved by a workaround
o All fixes will be at Oracle’s discretion based on technical review and feasibility
on 12.2.1.3 code base
o No new certifications including Accessibility/OAG changes, OS, DB drivers, JDBC
client, DB product versions, Web Server/OHS updates, browser
updates/certifications (ADF/WCP)
o No third-party library upgrades on any platform
o All crypto library updates will be at Oracle’s discretion based on technical
feasibility/changes required
o No security fixes will be provided for FMW 12.2.1.3 product samples or
examples after Dec 2021.

 Weblogic Server and Coherence 12.1.3 has been extended for the period of
January 1, 2020, through January 31, 2021.

 Oracle Enterprise Single Sign-On 11.1.2.3.0 ends December 31st, 2021.

Refer to "Error Correction Support Dates for Oracle Enterprise Single Sign-On
(Doc ID 2741509.1)" for more details.

Error Correction Policy Oracle Corporation 10-Dec-2021 Page 6

4 ERROR CORRECTION POLICY DETAILS

For detailed information on Error Correction refer to the table below:

Product Notes
Oracle Fusion Middleware 944866.1
Oracle Fusion Middleware (11.1.1.x & 11.1.2.x) 1290894.1
Oracle Fusion Middleware 12c (12.1.x & 12.2.x) 1933372.1
Oracle WebLogic Server 950131.1
Oracle Business Intelligence Suite 1664916.1
Oracle Enterprise Performance Management 1617238.1
Oracle Enterprise Single Sign-On 2741509.1

Error Correction Policy Oracle Corporation 10-Dec-2021 Page 7

5 TERMINOLOGY

Bundle Patch (BP)

An iterative patch issued between Patch Set releases. Bundle patches usually
include only fixes, but some products may include minor enhancements.
Bundle Patches are also cumulative (e.g. they include all the fixes from
previous patches in the series.

Conflicting Patch
Conflicting patches are two or more patches that have some files in common,
but contain independent fixes.
Critical Patch Update (CPU)
A Critical Patch Update is a collection of patches for multiple security vulnerabilities.

Critical Patch Update patches are usually cumulative, but each advisory describes only the
security fixes added since the previous Critical Patch Update advisory.
Thus, prior Critical Patch Update advisories should be reviewed for information regarding earlier
published security fixes. See the CPU program documentation for specific patches
Cumulative Patch

A patch in a series of patches which includes both new fixes plus all fixes from previous patches
in the series.
Diagnostic Patch

An interim patch created specifically to diagnose one particular problem.

Grace Period

The period of time following a new release where Oracle will create patches for both the new release
and previous versions that fall within a certain grace period window. This allows customers time to
plan for and install the latest version and receive patches while the upgrade is in process.
Grace periods vary by product – Refer to Section 3 - Fusion Middleware for details by product.
Interim Patch

When a customer cannot wait for the next release (Patch Set release) or proactive patch
(Patch Set Update or Bundle Patch), Oracle will create an interim patch that contains one more fixes.
These patches are not tested as thoroughly as the new releases and proactive patches.

Error Correction Policy Oracle Corporation 10-Dec-2021 Page 8

Major Release
Major Release is the release model that has historically been the primary model for all Technology
products. A Major release contains new features and technical upgrades.

The Lifetime Support Policy typically applies specifically to major releases and are listed
in the LSP document. All other releases in a series are considered Patch Set releases
of a major release.
Merged patch

A combination of multiple conflicting bug fixes into a single interim patch.

Minor release

A software release that has limited new feature content and is considered a sub-release of a major
release.
Patch set release

An integrated, cumulative, fully tested collection of fixes issued on top of a major product release
or as a full installation. Patch set releases may include enhancements.
Normally patch set numbers are denoted by the fourth digit in the version number (e.g. 12.2.1.4).
For the FMW 12.2.1 series, 12.2.1.2 and 12.2.1.4 are considered patch set releases of the 12.2.1
release.
Patch Set Update (PSU)
A cumulative, well-tested, quarterly recommended patch that contains the most critical fixes for
the applicable product, allowing customers to apply one patch to avoid many problems.
PSU patches are created during the Premier and Extended Support for those Patch Set releases
that are covered by the Error Correction Policy.
Point-in- time Snapshot
A patch that includes all fixes to date for a product at one point in time.
By its nature, it is fully cumulative.
Point-in-time snapshot patches are subjected to regression and system testing prior to release.
Regression

A new bug introduced or revealed as part of a new release or interim patch.

Security Patch Update (SPU)
An iterative, cumulative patch consisting of security fixes. Also known as Critical Patch Update.

Error Correction Policy Oracle Corporation 10-Dec-2021 Page 9

6 PATCH SETS

6.1 DEFINITION

Periodically during the Premier Support phase of a product's release lifecycle, Oracle
combines patches made since the product released, tests them thoroughly together,
and releases them in one single package. This package is known as a patch set.

Patch sets are the safest and most reliable way to get bug fixes for a supported release,
and are the cornerstone of preventive maintenance strategy. In the hierarchy
of patching, patch sets are the foundation upon which more frequent proactive
and interim patches are built.
By proactively applying Patch sets, as they are released, encountering bugs can be avoided
which might otherwise affect the smooth operation of systems. It helps in avoiding
installation at an inconvenient time if a known bug is encountered.

Patch sets are typically identified by a change in the 4th digit of the version number.
Because they are cumulative, it is possible to skip a patch set and still get all the fixes
with the latest release.

6.2 POLICIES
6.2.1 For Which Patch Set releases Will New Fixes Be Created?

Oracle will investigate bugs and will provide assistance for all supported product releases.
However, error correction which includes Interim Patches, Bundle Patches, PSUs, SPUs,
and Point- in-time Snapshots will only be created for Patch Set releases that within the
grace period time frame.
The grace period is intended to provide customers adequate time to plan and execute
the installation of the most recent patch set release. During the grace period, Oracle
will continue to create new fixes for the previous patch set release until the
grace period expires.
The end date for error correction is set for the previous patch set when the new patch set
is released. Future patch set releases will not have any effect on this end date once it
is established.

Error Correction Policy Oracle Corporation 28-Oct-2020 Page 10

 For example: Patch set N is released and the end of error correction for patch set N-1
is set for a year from the release date of N.
Nine months later, patch set N+1 is released.
The end date for error correction for N is set to a year from the release date of N+1.
But even though it means that three patch sets will be supported simultaneously, the
original date for end of error correction for N-1 remains the same.
Error correction is not shortened due to the quick release of N+1.

See Section 3 - Fusion Middleware for details about the grace period for each specific
product. Also, see section 8.1.2.2 - Criteria for Considering Interim Patch Requests
for other information about requesting an interim patch.

6.2.2 Patch Sets Releases Only For Premier Supported Releases

Patch sets are only created for releases in the Premier Support period. Patch sets
are not created for releases which have entered Extended Support.

6.2.3 Regressions Due To Patch Sets

Oracle’s goal is to produce patch sets of the highest quality, because we know
customers need them to be trouble-free if they are to be a successful part
of a preventive maintenance program.
Because of this, if a patch set does introduce a new bug, Oracle will give extra
priority to any P1 or P2 regression until fixed – but the issue should be identified
as a regression and a higher priority needs to be requested.
If necessary, Oracle may create an interim patch to correct the problem.

6.2.4 Not All Patch Sets Ported to Every Platform

Oracle may not port every patch set to every platform.

Oracle will always port the last patch set for a release to all platforms the release
was originally ported to.

Error Correction Policy Oracle Corporation 28-Oct-2020 Page 11

7 PROACTIVE PATCHING
(QUARTERLY PATCH SET UPDATES, BUNDLE PATCHES)

7.1 DEFINITIONS

Oracle streamlines patching by providing customers with well-tested patches released

on a fixed predictable schedule. This helps to plan and install the fewest number of
patches with the highest expectation of success.
For patch set releases, there are quarterly patches:
Critical/Security Patches (SPU/CPU), Patch Set Updates (PSU) and Bundle Patches.

The form of these may be individual patches, a bundle patch,

or a point-in-time snapshot patch, and may be different for different platforms
or products.
For example, PSUs are as a single patch for some platforms and as a bundle patch
on other platforms.

7.1.1 Security Patch Updates

A Security Patch Update (SPU) is a collection of security fixes issued quarterly

on the Tuesday closest to the 17th of the month (Jan, Apr, Jul, and Oct).
SPUs are built for specific patch sets for all versions of Oracle products covered
under error correction.

For example, for a given platform an SPU might be issued for FMW 12.2.1.4
(in the Extended Support period).
The number of bug fixes is very small compared to patch set releases.

7.1.2 Testing

SPUs are tested extensively including install and functional regression tests,
and in some cases are tested as part of an Oracle application stack.

Oracle recommends as a best practice customers install each SPU on a test system
which mirrors their production system’s environment before installing in a production
system.

7.1.3 Scope

SPUs contain new security fixes, plus all fixes from previous SPUs issued
on any given patch set. Thus each new SPU on a particular patch set is cumulative.

For example, the second SPU issued against FMW 12.2.1.4 will contain all the fixes
from the first SPU for 12.2.1.4 plus the new fixes.
Even though Oracle intends to include mainly security fixes in SPUs, we may decide to
include high-priority non- security fixes.
We will always identify them in the SPU documentation.
Error Correction Policy Oracle Corporation 28-Oct-2020 Page 12
7.1.4 Patch Set Updates

Patch Set Updates are proactive cumulative patches comprised of critical bug fixes
released quarterly. PSUs establish a new baseline version number.
Where both are released in a quarter, all the fixes in the Security Patch Update are
included in the PSU.
PSU applies to a specific patch set. Unlike patch sets, interim patches can be requested
for any PSU, as long as the patch set it applies to still supports error correction.
Every PSU is a version of the software, changing the 5th place of the version number
to a string that represents the “year month date” of the PSU release
(i.e. 190716 means the patch released on July 16, 2019).
It also represents a new baseline of the code, so an interim patch may need to be built
specifically for the PSU installed in order to be applied. For more information on PSUs
see Patch Set Updates for Oracle Products (Doc ID 854428.1) including information about
patch conflicts and how to resolve them.

7.1.4.1 Testing

PSUs are subjected to extensive tests prior to release. Regression, system

and performance testing are done to ensure customers have the most
successful experience using them.

7.1.4.2 Scope

PSUs contain strictly limited number of fixes. Content is selected to provide

maximum benefit while ensuring the PSUs are safe to apply.
Fixes include:
 Fixes for critical technical issues such as wrong results,
corruptions, and hangs.
 Fixes encountered by a large number of customers.
 Fixes already proven in the field.
 All fixes that are included in the SPU patch
Excluded from any PSU are:
o Fixes which would require recertification or changes functional behavior.
o Fixes which would require any configuration changes.
o Fixes to the optimizer.
If a Critical Patch Update security fix breaks one of the above rules, we include it and
document the exception.

7.1.5 Recommended Patches

Some products may designate some patches as “Recommended” or “Critical”.

Recommended patches mean all customers should apply due to the likelihood the
customer may experience the problem fixed by the patch or the potential severity
of the problem.

Error Correction Policy Oracle Corporation 28-Oct-2020 Page 13

7.2 POLICIES – CRITICAL PATCH UPDATE PROGRAM
7.2.1 Which Patch Set Versions Are Covered by the CPU Program?

Patches released as part of the CPU program (e.g. PSUs, SPUs, bundle patches,
or point-in-time snapshot patches) follow the same rules for a patching support
as other patches do.
They are created for the current releases or patch set releases and the previous versions
(if any) for the duration of the grace period (see section 3.2.1 above).

For example, if FMW 12.2.1.4 is the current FMW patch set release, a PSU would be
created for FMW 12.2.1.3 as long as it is within the grace period allocated for upgrading to
FMW 12.2.1.4.
Only customers who have contracted for Extended Support are entitled to download
and use proactive patches created for a product in Extended Support.
Only customers who have contracted for Market Driven Support (MDS) are entitled to
download PSUs created for a product covered by MDS. (E.g. FMW 12.2.1.4)

7.2.2 Patch Conflict Resolution for SPUs

It is possible to encounter a conflict between the new SPU and a patch

that was installed prior to the SPU.
Conflict resolution process is different for different products –
see Patch Conflict Resolution (Doc ID 1299688.1) for more information.

7.3 POLICIES – PATCH SET UPDATES

7.3.1 For Which Patch Set Versions Will a PSU be created?

Patch Set Updates are created for products and patch set versions which in Oracle’s
judgment are adopted widely enough to benefit from this approach to delivering an
integrated set of fixes, and only for patch set releases currently under error correction.
See Section 3 - Fusion Middleware for more information on which patch sets are eligible
for error correction.

7.3.2 For Which PSUs Can Interim Patches Be Created?

Interim patches can be created for any PSU as long as the patch set it is based
on is supported for patching. In other words, there is no requirement to install the
latest PSU in order to get a new patch built.

Error Correction Policy Oracle Corporation 28-Oct-2020 Page 14

7.3.3 Conflicts between PSUs and Previously Installed Interim Patches

For products and releases issue fixes via interim patches, it is very important
to check for conflicts as part of the planning process when applying a PSU to
understand if the installed patches will conflict and ensure conflicts are resolved
before the PSU is installed.
It is important to get a replacement fix which is specific to the PSU that is planned for
application. If the required patch that resolves the conflict does not already exist
on My Oracle Support, it must be requested.
Unlike a typical request for a new interim patch, no special approval is required to get
a replacement patch built.

Note: Even if a conflict i s r e s o l v e d with the current PSU, the new fix might still
conflict with later PSUs. Overlay patches are proactively created to resolve conflicts
as part of the quarterly program, so the required fix needed may already exist.

7.3.4 Requested Patches Not Included In Future PSUs

In order to keep them small and focused, new fixes delivered to customers on top
of a PSU are NOT typically rolled into the next PSU built on the same patch set – fixes
are selected for inclusion based on the criteria outlined in the Scope section above.

For example, a new fix for WLS 10.3.6.0.1 will not be included in 10.3.6.0.2 –
it would generally be included in the next release or patch set instead.

This means if there was an interim patch built on a particular PSU, a new patch for the
same fix may have to b e requested when installing a later PSU, if the interim patch
conflicts.

Error Correction Policy Oracle Corporation 28-Oct-2020 Page 15

8 INTERIM PATCHES

8.1 DEFINITION
An Interim Patch is a patch containing one or more fixes made available to customers
who cannot wait until the next proactive patch to get the fix, or are running on a long
term patch set of a release.
Interim patches will not be used to backport features to older releases or implement new
features. Interim patches are specific to a particular product version (patch set).
For example, an interim patch created for FMW 12c should NOT be installed on FMW 11g.
All interim patches are included in a future (usually next) product release or patch set.
Interim patches are not released for all products or on all platforms. In some cases
products may release fixes on some or all platforms as cumulative bundles or
point-in-time snapshots, and may not release any interim patches, or interim patching is
limited.

8.1.1 Testing

Interim patches are tested for the specific environment in which the patch was
initially created. Users installing interim patches in other environments, such as where
different combinations of patches are installed, compound the risk to system stability
with each additional interim patch installed

8.1.2 Policies

8.1.2.1 Supported Releases

New interim patches are only created for eligible releases and that are in:
Premier Support
Extended Support
Limited Extended Support
NOTE: During Limited Extended Support, interim patches are only created
for Severity 1 issues reported via Service Request.
This includes security issues which are of critical impact to business
when there is good reason to believe the issue affects the version being run
with the current configuration being used.
See Lifetime Support Policy – Oracle Technology Products for the dates of Premier
and Extended Support, and Oracle Software Technical Support Policies for exceptions
such as any Limited Extended Support offerings on specific releases or platforms.

Error Correction Policy Oracle Corporation 28-Oct-2020 Page 16

8.1.2.2 Criteria for Considering Interim Patch Requests

Any request for a new interim patch should be accompanied by a case showing
the customer business and operational impact is severe to be considered.
Also, Oracle must believe it is technically feasible to create a patch
which does not jeopardize the stability of the system.
Below are some of the criteria which should be discussed in the impact case
which must accompany a request:
 Customer business impact
 Inability to do normal business
 Significant risk to development or deployment schedule
 Patch required to replace a patch rolled back by a PSU
Operational/technical impact
 Permanent data corruption (physical or logical)
 System hangs or crashes repeatedly
 Failure of critical functionality
 Severe performance regression
 Bug fix is not implemented in a later release or patch set for the release being
run, or installing a later release is not feasible due to a strong business
or technical reason
 No workaround available or inability to use workaround because of a strong
business/technical reason
 Technical Feasibility: if a fix requires too many lines of code to be changed,
Oracle may determine the bug fix cannot be safely implemented as an interim
patch
If the impact case for the request is strong, Oracle Support will log a request
for an Interim Patch, which will result in the patch being created
and placed on My Oracle Support to download.

If the impact of a bug is high but does not meet the above criteria,
Oracle Support will log a request to include the fix in the next release
or patch set.

Error Correction Policy Oracle Corporation 28-Oct-2020 Page 17

8.1.2.3 Which Patch Sets Are Eligible For Interim Patches?

Oracle will create new interim patches against the currently available release,
and for the previous patch set for the duration of the grace period
(see section 6.2.1 above).

Oracle prefers to create new fixes on the latest release. Hence, Oracle Support
will always recommend to install the latest patch, although previous release
is still being supported.
However, this approach will be required if a fix is not technically feasible to implement
in the previous release or patch set.
NOTE: It is NOT REQUIRED to install any release or patch set as a prerequisite for
Oracle to investigate a potential bug.

8.1.2.4 Regressions Due To Interim Patch

If an interim patch introduces a new bug when installed on a customer system,

Oracle will work the problem at the level of priority assigned to the original bug.
If necessary, Oracle may create a new interim patch to correct the problem.

8.1.2.5 Interim Fixes Included In Future Patch Sets and Releases

Interim patches are automatically included in the next release of the product.
In cases where the interim patch is created too late in the development cycle
of the current release, it will be rolled into a subsequent patch set, bundle patch
or PSU.

The list of bug fixes included in a new release should be reviewed to make certain
all the fixes in the patches currently installed are included.
If a patch is missing, contact Support so that a new patch can be created
on the release required.

Error Correction Policy Oracle Corporation 28-Oct-2020 Page 18

8.1.2.6 Customer Considerations

 An interim patch is unit tested but not tested with other interim patches,
nor is the product regression tested as a whole with the interim patch included.
It is recommended to install and perform basic testing on a test system
before installing an interim patch in a production system.
 Install the requested patch promptly. If it is not planned to be installed promptly,
request the fix to be included in the next release or bundle.
 Report back to Oracle Support on the success of the patch,
so Support can update the bug.
 As a best practice, install a patch set with this fix as soon as it is available.

8.1.2.7 Interim Patches Available Via Self Service

Once an interim patch has been provided it is made available to other customers for
download via My Oracle Support at Oracle’s discretion.

IF THE PLAN IS TO INSTALL MORE THAN ONE INTERIM PATCH to an Oracle Home
directory, it is very important to contact Oracle Support before installing the patch.
Oracle Support will determine, based on the patches already installed,
whether a Merged Patch must be requested.
Failure to do so may result in reoccurrence of problems fixed by an earlier-installed
interim patch.

Error Correction Policy Oracle Corporation 28-Oct-2020 Page 19

9 DIAGNOSTIC PATCHES

9.1 DEFINITION

Diagnostic patches are patches created for the purpose of attempting to diagnose a product
or performance fault.

9.2 POLICIES
9.2.1 Install Only On Problem System

Diagnostic patches should not be installed on any other customer system than the one
they were specifically produced for unless so directed by Oracle Support personnel.

9.2.2 Diagnostic Patches Created On All Versions

Diagnostic Patches may (at Oracle’s discretion) be created for any supported version.
See section 6.2.1 above.

9.2.3 Remove Diagnostic Patches after Problem Resolution

Diagnostic patches should be removed from a production system once the situation
it was produced for has been resolved, unless otherwise directed by Oracle Support
personnel.

9.3 HISTORY

Sl. Document Date Comment

No. Version

1 1.0 28-OCT-2020 Initial Version

2 1.1 10-DEC-2021 Version 12.2.1.3 has been extended from SEP 2020 to DEC
2022

Error Correction Policy Oracle Corporation 28-Oct-2020 Page 20