SAP Basis Tech Supports

Symptom

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
This note is issued as a Hot News. Check the note regularly for updates. Otherwise, you will not be aware of important changes regarding prerequisites, consequences and solutions. A new Hot News is not issued if a note is updated.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
General notes for Oracle Critical Patch Updates (CPU)
New as of 2005:Since 2005, Oracle provides Critical Patch Updates (CPU) for all product lines on a quarterly basis. The extensive patches contain corrections for significant security problems. You (as the customer) must install these patches unless they collide with another patch that SAP considers to be a mandatory requirement.
New as of Release 10.2.0.4:As of Release 10.2.0.4, the procedure for setting up CPUs has changed fundamentally. Oracle is changing the CPU patch procedure to “n-apply”. This means that the CPU patch now contains only pure security patches, and no longer contains functional patches. If a conflict occurs when you apply the CPU patch, Oracle Support provides a merge patch for the patch that causes the conflict. However, since only security patches are contained in the CPU patch, patch conflicts are much less likely to occur.
As of Oracle Version 10.2.0.4, CPU patches no longer consist of one single large merge patch (which was the case for earlier versions), but they consist of several “patch molecules” that are independent of each other. In principle, a patch molecule is like a single patch and can either be installed completely or not at all. If there is a conflict between a patch that was already installed and a patch molecule that is contained in the CPU, the DBA can either decide not to install the CPU at all, or to install at least those patch molecules that do not cause a conflict. The patch molecules that cause the conflict will be installed at a later time when the merge patch is available.
The advantage of this new procedure is that patch conflicts are less likely to occur. If a patch conflict still occurs, this does not prevent the entire CPU from being installed. Instead, it only prevents the affected patch molecule from being installed. However, due to technical problems, the system may not be able to perform a merge. In this situation, as before, the customer must decide whether to apply the CPU patch or the functional patch that was already recommended.
We do not support the installation of CPU patches using MOPatch (Note 1027012).

Other terms

CPU, Oracle, security patches, patch, Critical Patch Updates

Reason and Prerequisites

Critical Patch Updates contain corrections for moderately severe and very severe security issues, and for other “critical fixes”, generally:
- Prerequisites for the security patch
- Patches that have been requested by a large number of clients
- Patches that may already have been implemented and that
- may cause patch conflicts

Solution

********************
CPUs for 2009
********************

Oracle CPU from April 16, 2009
Oracle 10.2.0.4
For more information, see Note 1330253.
Oracle 9.2.0.8.
The CPUApr2009 conflicts with the previously recommended patch 5530583 (see Note 1043381). Patch 5530583 corrects a critical ASSM performance problem, and it is strongly recommended for customers who use the ASSM tablespaces.
If you do not use ASSM tablespaces and have not installed patch 5530583, you can import CPUApr2009.
Merging these two patches (CPUApr2009 and 5530583) is not possible for technical reasons, and it will not be possible for future CPU patches either.
For more information, see Note 1330253.

Oracle CPU January 16, 2009
Oracle 10.2.0.4
For more information, see Note 1295141.
Oracle 9.2.0.8.
The CPUJan2009 conflicts with the previously recommended patch 5530583 (see Note 1043381). Patch 5530583 corrects a critical ASSM performance problem, and it is strongly recommended for customers who use the ASSM tablespaces.
If you do not use ASSM tablespaces and have not applied patch 5530583, you can apply CPUJan2009.
Merging these two patches (CPUJan2009 and 5530583) is not possible for technical reasons, and it will not be possible for future CPU patches either.
For more information, see Note 1295141.

********************
CPUs for 2008
********************

Oracle CPU October 16, 2008
Oracle 10.2.0.4
For more information, see Note 1262717.
Oracle 9.2.0.8.
The CPUOct2008 has a conflict with the recommended patch 5530583 (see SAPNet Note 1043381). Patch 5530583 corrects a critical ASSM performance problem, and it is strongly recommended for customers who use the ASSM tablespaces.
If you do not use ASSM tablespaces and have not installed patch 5530583, you can import CPUOct2008.
You cannot merge both patches (CPUOct2008 and 5530583) for technical reasons, and merging will also not be possible for any future CPU patches.

Oracle CPU from July 16, 2008
Oracle 9.2.0.8.
The CPUJul2008 conflicts with the previously recommended patch 5530583 (see Note 1043381). Patch 5530583 corrects a critical ASSM performance problem, and it is strongly recommended for customers who use the ASSM tablespaces.
If you do not use ASSM tablespaces and have not applied patch 5530583, you can apply CPUJul2008.
Merging these two patches (CPUJul2008 and 5530583) is not possible for technical reasons, and it will not be possible for future CPU patches either.
Oracle 10.2.0.2
The CPUJan2008 was the last CPU patch for Oracle Release 10.2.0.2.
Oracle 10.2.0.4
For more information, see Note 1233304.

Oracle CPU from April 16, 2008
Oracle 9.2.0.8.
The CPUApr2008 conflicts with the previously recommended patch 5530583 (see Note 1043381). Patch 5530583 corrects a critical ASSM performance problem, and it is strongly recommended for customers who use the ASSM tablespaces.
If you still decide to import CPUApr2008, open an SAP customer message referring to this note and specify your platform, so that we can provide you with CPUApr2008.
Merging these two patches (CPUApr2008 and 5530583) is not possible for technical reasons, and it will not be possible for future CPU patches either.
Oracle 10.2.0.2
The CPUJan2008 was the last CPU patch for Oracle Release 10.2.0.2.
The CPUApr2008 is contained in Oracle patch set 10.2.0.4.

Oracle CPU January 16, 2008
Oracle 9.2.0.8.
For more information, see Note 1140644.
Oracle 10.2.0.2
For more information, see Note 1140644.

********************
CPUs for 2007
********************

Oracle CPU October 16, 2007
Oracle 9.2.0.8.
For more information, see Note 1107601.
Oracle 10.2.0.2
For more information, see Note 1107601.

Oracle CPU from April 16, 2007
Oracle 9.2.0.8.
For more information, see Note 1076362.
Oracle 10.2.0.2
For more information, see Note 1076362.

Oracle CPU April 16, 2007
Oracle 9.2.0.8.
See Note 1050193 for further information.
Oracle 10.2.0.2
The CPU patch from April 16, 2007 for Oracle Release 10.2.0.2 has not yet been released for SAP. There are some conflicts with other required patches.
We are currently examining the option to provide a merge fix that contains the CPU Patch April 2007 and the other patches that you require.
As soon as we have reached a decision, Note 1050193 will be changed accordingly.

Oracle CPU April 16, 2007
Oracle 9.2.0.8.
See Note 1050193 for further information.
Oracle 10.2.0.2
The CPU patch from April 16, 2007 for Oracle Release 10.2.0.2 has not yet been released for SAP. There are some conflicts with other required patches.
We are currently examining the option to provide a merge fix that contains the CPU Patch April 2007 and the other patches that you require.
As soon as we have reached a decision, Note 1050193 will be changed accordingly.

Oracle CPU January 16, 2007
Oracle 9.2.0.8.
The CPU patch from January 16, 2007 for Oracle Release 9.2.0.8 is the same as the CPU patch from October 16, 2006.
See Note 1019587 for further information.
Oracle 10.2.0.2
The CPU patch from January 16, 2007 for Oracle Release 10.2.0.2 has not been released for SAP. There are some conflicts with other required patches. These conflicts will also be present in the subsequent CPU patches (CPUApr2007, CPUJul2007).
Therefore, no CPU patch will be made available for Oracle Release 10.2.0.2.

********************
CPUs for 2006
********************

Oracle CPU from 17.10.06
Oracle 10.2.0.2
The CPUOct2006 Patch 5490848 for Release 10.2.0.2 has not been released for SAP. There are some conflicts with other required patches.
Oracle 9.2.0.7
Due to conflicts with earlier, but required patches, the patches for 9.2.0.7 will not be released until further notice.
Oracle 9.2.0.8.
The CPU patch from January 16, 2007 for Oracle Release 9.2.0.8 is the same as the CPU patch from October 16, 2006.

Oracle CPU from July 18, 2006
Refer to Notes 965912, 871096, 981875.
Do not apply or remove this patch because it is not compatible with the required Optimizer Merge Fix 5689095.

Oracle CPU from 18.04.06
See Note 949339.

Oracle CPU from 18.01.06
See Note 920781.

********************
CPUs for 2005
********************

Oracle CPU from 18.10.05
You can now download the patches for 9.2.0.7.
Due to conflicts with earlier, but required patches, the patches for 9.2.0.6 will not be released until further notice. Update to 9.2.0.7 if you require the CPU patches.
Read Note 894299.

Oracle CPU from 12.07.05
The availability of the patches has been delayed because the CPU patch that is currently valid would overwrite other interim patches that are already available. A merge fix has been requested, but it is not yet available.
No CPUs have yet been released by SAP for Oracle Database 10.1.

Oracle CPU from 12.04.05
Oracle 9.2.0.6
Do not install a CPU from April 2005 for Oracle 9.2.0.6 because the CPU patch would overwrite other interim patches that are already available.

Oracle CPU from 18.01.05
See Note 811174.