PSU 11.1.0.7.xx Conflict Handling - Proactive Merge Generation - Forms & Reports 11.1.1/11.1.2
(Doc ID 1562351.1)
Last updated on OCTOBER 13, 2022
Applies to:
Oracle Fusion Middleware - Version 11.1.1.2.0 to 11.1.1.2.0 [Release Oracle11g]Oracle Forms - Version 11.1.1.2.0 to 11.1.2.2.0 [Release 11g]
Oracle Reports Developer - Version 11.1.1.2.0 to 11.1.2.2.0 [Release 11g]
Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.1.0.7 [Release 11.1]
Information in this document applies to any platform.
Specific to UNIX platforms.
Goal
IMPORTANT UPDATE
This has been an ongoing issue and is now FIXED:
<Note 2020086.1> Invalid Conflict/Subset - PSU/BP FOR 11.1.0.7 REPLACES 11.1.1.7 CPU/NZ PATCHES WITH 11.1.0.7 FILES
Resolution:
-
You should not apply a previous 11.1.0.7 PSU, SPU, or Windows Bundle to 11.1.1.x or 11.1.2.x homes.
- This issue is now fixed beginning with CPU January 2016 (<Note 2074802.1>). PSU Patch #s will be placed in Oracle Fusion Middleware 11.1.2.2, 11.1.1.9 and 11.1.1.7 tables:
- PSU 11.1.0.7.24 <Patch 22290164> for Unix- Bundle Patch 61 <Patch 22607089> for Windows 32-Bit
- Bundle Patch 61 <Patch 22607090> for Windows x64
-
This will be the last PSU for the Oracle Database client and is only for FMW 11.1.1.x and 11.1.2.x homes. You should continue to apply other patches released by the CPU program, ensuring you also include patches labeled for OHS, OPMN, SSL/Networking, and other components installed in your home.
- OPatch may report a conflict with 9965029 or 10407723. You will have the option to roll them back and should do so. Download and apply <Patch 22733221> to replace these fixes.
- Resolved symptoms from above steps (UNIX only):
1) Patch(es) [ 9473270 7708340 ] are subset patch(es) of the Patch currently being installed [ 22290164 ].
-- Solution: You can ignore this because the fixes are a subset. Meaning, in the PSU. OPatch should roll them back automatically, as long as there isn't another issue preventing progress. If OPatch prompts for a decision, allow them to rollback and apply the new patch.
2) Patch(es) [ 9965029 10407723 ] conflict with the Patch currently being installed [ 22290164 ].
-- Solution: Roll these back and apply Patch 22733221 after you have applied Patch 22290164.
-- Explanation: This normally means you need a merge patch. In this case, these patches have been part of the proactive overlay program and you need to roll these back and then re-download new patches for the PSU 11.1.0.7.xx version. This is what this document was originally describing as regular process. This last PSU 11.1.0.7.24 (Patch 22290164) is for FMW homes only, and the required overlay patches are now rolled into Patch 22733221 only for FMW homes.
3) You will get the following error if applying the incorrect version of any overlay patch after the new FMW-only Patch 22290164:
Prerequisite check "CheckPatchApplyDependents" failed.
Interim patch 10407723 requires prerequisite patch(es) [ 20761024 ] which are not present in the Oracle Home.
Apply prerequisite patch(es) [ 20761024 ] before applying interim patch 10407723 .
Recommended actions: This patch requires some other patches to be installed in the Oracle Home.
OPatch cannot find those required patches in the Oracle Home.
-- Solution: Do not download and apply overlay patches for version 11.1.0.7.24, as these were built to enforce the DB-Only Patch 20761024. The popular Forms & Reports patches 9965029 and 10407723 are now replaced by Patch 22733221 with a new prerequisite. There are no other known 11.1.0.7 overlay patches you should apply to 11.1.1.x or 11.1.2.x homes.
THE REST IS FOR HISTORICAL REFERENCE - HOW IT FORMERLY WORKED TO RESOLVE CONFLICTS - NOW REPLACED BY ABOVE
Background Information
Oracle Fusion Middleware 11.1.1.x and 11.1.2.x homes have 11.1.0.7 components and may need the Patch Set Update (PSU) 11.1.0.7.xx applied. The PSU for Oracle Database Server 11.1.0.7 has security related 11.1.0.7 updates which also fix some Oracle Forms issues. Oracle Database Server patches include both server and client-side (including middleware) updates. It has become popular to apply the PSU to cover a potential security related issue between Middleware and Database homes when the Database is patched and configured a specific way (See <Note 1493990.1>, "Patching for CVE-2012-3137"). As time progresses, there may be more included security fixes for the Oracle Client 11.1.0.7.
When following Critical Patch Update instructions, Oracle Fusion Middleware 11.1.1.x and 11.1.2.x steps refer to Oracle Database 11.1.0.7 steps to apply a Patch Set Update (PSU) for the Oracle Client updates. Reference:
<Note 1073776.1> - Steps to Maintain Oracle Fusion Middleware 11g Release 1 (11.1.1)
<Note 1373061.1> - Steps to Maintain Oracle Forms & Reports 11g Release 2 (11.1.2)
Oracle Forms Requirements
There are two other popular Oracle Forms fixes where a previous one-off for each was supplied. (<Patch 9965029> / <Patch 10407723>). These didn't reach the PSU because they are not security related and/or didn't meet other criteria. The Forms & Reports 11.1.2.1 release actually applies these 11.1.0.7 one-off patches for Oracle Forms by default. If you apply the DB PSU, there will be a conflict with these. If there is a conflict, we normally file a Merge Request, and obtain the new patch required. Note the patches supplied today are no longer combined merges, they are "overlay patches" which get applied on top of the previously applied PSU.
You may get a message from OPatch like this:
Merge Patch needed - Patch [ 10407723 ] conflict with patch(es) [ 16610144 ] in the Oracle Home
or
Merge Patch needed - Patch [ 9965029 ] conflict with patch(es) [ 16610144 ] in the Oracle Home
-
- 9965029 and 10407723 are two known examples for Oracle Forms. There may be others.
- The 16610144 may different depending on the patch applied before, there are PSU and SPU patches for DB 11.1.0.7 available with different numbers.
- On Windows, PSU patching is different because of cumulative bundles supplied. Fixes for 9965029 and 10407723 have been provided in Bundle 38 onwards.
- The steps below will hep determine if you need to file a merge request with a PSU 11.1.0.7.xx or if a patch has already been made available.
- 9965029 and 10407723 are two known examples for Oracle Forms. There may be others.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
IMPORTANT UPDATE |
Background Information |
Oracle Forms Requirements |
Solution |
Proactive Merge Process |
Example When Applying a PSU After a DB Client 11.1.0.7 Patch for Oracle Forms |
Fresh Start Example Steps - Apply PSU Before DB Client 11.1.0.7 Patch for Oracle Forms |
References |