PATCH 28186730 - OPATCH 13.9.4.2.13 FOR EM 13.4, 13.5 and FMW/WLS 12.2.1.3.0, 12.2.1.4.0 AND 14.1.1.0.0
Platform : Generic
Product Patched : Oracle Fusion Middleware 12c / Oracle WebLogic Server 12c AND 14.1.1 / EM 13.4, 13.5
Product Version : FMW versions : 12.2.1.3.0, 12.2.1.4.0 AND 14.1.1.0.0
: EM version : 13.4.0.0.0, 13.5.0.0.0
This is the README file for OPatch 13.9.4.2.13, the Oracle Interim One-off Patch Installer.
Notes
-----
Historically, OPatch was updated by unzipping and replacing ORACLE_HOME/OPatch directory.
For versions greater than or equal to 13.6, it now uses the OUI installation tooling.
This ensures that the installer both executes the file updates and logs the components and
file changes to the OUI meta-data. A pure unzip install means the OUI tooling is
not aware of these changes, which has on occasions led to upgrade related issues.
When extracted, this contains a 6880880 directory. This is because previous OPatch downloads
are available as Patch 6880880. To avoid confusion with downloads not applicable to FMW/WLS,
this new OPatch 13.9.4.2.13 placeholder was created as Patch 28186730.
Pre-Installation Instructions
-----------------------------
1. Backup of the ORACLE_HOME and Central Inventory must be taken as there is no mechanism to rollback to the older OPatch version.
2. Unzip this patch into your PATCH_HOME staging directory.
3. This installer must be executed using a Java Development Kit (JDK).
- Set your PATH to include your <JDK_LOCATION>/bin
4. All the processes which are using files from ORACLE_HOME must be stopped before OPatch upgrade.
Installation
-----------------------------
NOTE: If you are upgrading the OPatch on Oracle Enterprise Manager (OEM), please follow the instructions specified in the Doc ID 2728285.1
1. Install the software with the following steps.
UNIX Only:
----------
Use the standard command to upgrade the OPatch utility:
* java -jar <PATCH_HOME>/6880880/opatch_generic.jar -silent oracle_home=<ORACLE_HOME_LOCATION>
where ORACLE_HOME_LOCATION is the absolute path where you have installed FMW/WLS products.
If using a custom Inventory location, install the software with the following command:
* java -jar <PATCH_HOME>/6880880/opatch_generic.jar -silent oracle_home=<ORACLE_HOME_LOCATION> -invPtrLoc <INVENTORY_LOCATION>
where INVENTORY_LOCATION is the absolute path to the oraInst.loc file.
If you have /tmp set with a noexec flag for security, or prefer to set a custom location for the logs, you can override the tmp with the -D argument:
* java -Djava.io.tmpdir=/opt/oracle -jar <PATCH_HOME>/6880880/opatch_generic.jar -silent oracle_home=<ORACLE_HOME_LOCATION>
Log location:
* For a successful OPatch upgrade session, logs will be copied under <CENTRAL_INVENTORY>/logs.
* For an unsuccessful OPatch upgrade session, logs will be under /tmp/OraInstall<TIMESTAMP>
* If you have specified a custom log location, refer to the console output for the log location.
* Refer to Doc ID 2759112.1 if you encounter any OPatch upgrade issues.
Windows Only:
-------------
Use the standard command to upgrade the OPatch utility:
* java -jar <PATCH_HOME>\6880880\opatch_generic.jar -silent oracle_home=<ORACLE_HOME_LOCATION>
where ORACLE_HOME_LOCATION is the directory where you have installed FMW/WLS products.
This is the default option setting permissions within the Oracle Home as defined by the original product installer.
- This usually works for most of the cases and for newer installations is the best approach.
If you have modified the original permissions, the following option enables users to proceed with the installation without any permission modification:
* java -jar <PATCH_HOME>\6880880\opatch_generic.jar -skipACLSetting -silent oracle_home=<ORACLE_HOME_LOCATION>
Use the following option when the proper permissions in the Oracle Home is not allowing the installation to proceed.
- This option will overwrite the ACL settings:
* java -jar <PATCH_HOME>\6880880\opatch_generic.jar -J-Doracle.installer.oh_admin_acl=true -silent oracle_home=<ORACLE_HOME_LOCATION>
Log location:
* For a successful OPatch upgrade session, logs will be copied under <CENTRAL_INVENTORY>\logs.
* For an unsuccessful OPatch upgrade session, logs will be under %TMP%\OraInstall<TIMESTAMP> or %TEMP%\OraInstall<TIMESTAMP>.
* If you have specified a custom log location, refer to the console output for the log location.
* Refer to Doc ID 2759112.1 if you encounter any OPatch upgrade issues.
2. To validate the installation:
cd <ORACLE_HOME>/OPatch
opatch version
opatch lsinventory
Post-installation Instructions
----------------------------------
Follow interim patch readmes for other installation steps to apply patches.
Note on NGINST Dependency Patches
----------------------------------
There is no need to apply the following NGINST patches as the fixes are available as part of OPatch 13.9.4.2.13:
31101362, 29137924, 29909359
Refer to the "Details about NGINST Patches" section for further details.
Deinstallation
--------------
There is no mechanism to revert OPatch to an older version.
To revert OPatch, restore the backup for your ORACLE_HOME and Central Inventory.
Documentation and Help
-----------------------
To obtain command names or options from the command prompt, use:
opatch -help
opatch napply -help
To learn about patching with the OPatch utility with FMW/WLS 12c:
Doc ID 1587524.1 Using OUI NextGen OPatch 13 for Oracle Fusion Middleware 12c (12.1.2+)
New Features and Bugs Fixed List
---------------------------------
13.9.4.2.13
----------
35332356: DELETE INACTIVE PATCHES SHOULD WORK WITH MULTIPLE SUPERSET CHAIN IN A GIVEN ORACLE HOME IN NEXTGEN BASED HOMES
35124156: OPATCH APPLY IS FAILING WITH ERROR CODE 73 IN GA+N-1+N SCENARIO FOR WLS PSU 12.2.1.4.230225
35307976: BDA Suites blocked - Agent Push failure Initialization > SSH connection check failed
35346354: Provide option to not include filemap contents in component inventory object memory
35283184: FOR WLS PSU 14.1.1.0.230411- OPATCH APPLY IS FAILING WITH ERROR CODE 73 IN GA+N-1+N SCENARIO
35383056: Patch apply failure with cryptoj 6.2.6.2
35509483: OPATCH13: OPATCH ROLLBACK FAILS WITH ERROR CODE 73 IN N TO N-1 SCENARIO IN FIRST ATTEMPT
35486283: CAPTURE OOP RELATED MESSAGES IN OPATCH CORE LOGS
35206055: PREVIOUS SGF PATCH (12.2.1.3.230312) IS GETTING ROLLED BACK BEFORE APPLYING LATEST 12.2.1.3 WLS PATCH.
35205311: INSTALLATION OF LATEST 12214 WLS PATCHES IS BEING IGNORED WHEN APPLIED ON TOP OF PREVIOUS SGF PATCH (12.2.1.4.230312) DUE TO FILE CONFLICTS
13.9.4.2.12
----------
35277035: OPATCH UTIL SHOWINACITVEPATCHES TO BE BUILT TO SHOW ALL INACTIVE AND OVERALYS FOR NEXTGEN BASED HOMES
35087070: ADD NEW OPATCH UTIL OPTIONS LISTORDEREDINACTIVEPATCHES AND DELETEINACTIVEPATCHES FOR NEXTGEN BASED HOMES
35078251: OPATCH UTIL DELETE OPTION TO DELETE INACTIVE PATCHES FROM PATCH_STORAGE AND ORACLE NEXTGEN HOMES
35060241: PERFORMANCE IMPROVEMENT FOR ROLLBACK WITH OBFUSCATED PATCH STORAGE
35127276: ODI BP AND SPB APPLIED USING OPATCH 13.9.4.2.11 ARE MISSING FUNCTIONALITY
34873831: napply/rollback merged compDef.xml file is not updated if it had been exist
13.9.4.2.11
----------
34678476: CVE-2022-42003
32920864: Disable loading dll from current directory
34820519: CVE-2022-45047
34521456: OBFUSCATE BACKED UP FILES DURING APPLY IN .PATCH_STORAGE
34752911: OPATCH FAILED WITH ERROR CODE 3
34637305: SKIP FUSER IN REPORT MODE DURING PATCHING
33845786: VULNERABLE LOG4J FILES ARE FOUND UNDER ORACLE_HOME/.PATCH_STORAGE
34574534: GETTING JAR NOT APPLIED ERROR MESSAGE DURING LATEST WLS PATCH APPLIED USING OPATCH 13.9.4.2.11 ON WINDOWS PLATFORM
34616719: OPatch version 1394211 13.5 RU09 NZDT Patch 34471058
34678
