How To Install Oracle Critical Patch Update Advisory - April 2021
How To Install Oracle Critical Patch Update Advisory - April 2021
1. Oralce account
You can register a new one with your own email.
Or, utilize below
Account [email protected]
Password iMAN@0611
Find the folder matching your Weblogic Server version, and download.
Prerequisites
1. Minimum Java Version Check
There is an expected minimum version of Java SE (JDK\JRE) before installing the WLS SPB.
In order to maintain security, it is strongly encouraged to upgrade to the Java SE released with the
Critical Patch Update program:
Doc ID 2762944.1 Oracle Critical Patch Update (CPU) April 2021 for Oracle Java SE
Refer to the following table for minimum and recommended Java SE versions:
Platform JDK Vendor Major JDK Expected Minimum Version
Version
Doc ID 1492980.1 on How to Install and Maintain the Java SE Installed or Used with FMW 11g\
12c\14.1.1 Products
https:\\support.oracle.com\epmos\faces\DocumentDisplay?id=1492980.1
2. Backup
IMPORTANT: Create a complete backup of ORACLE_HOME and CENTRAL INVENTORY
Refer the following Backing Up Your Environment for Oracle recommended backup strategies.
Restoring from backup is the only way to rollback the SPB.
%ORACLE_HOME%\OPatch\opatch version
Install
The SPB makes use of two OPatch features:
a. The patch installation is performed by the "opatch napply" command, where the napply can install multiple
patches using the list configured in the <platform>_patchlist.txt.
b. OPatch gives you an option to run with the flag -report. This option will not install the patches but will show
you the result of what would happen if you did apply the patches.
Note: This report may be useful to run if you are unsure of any conflicts or issues applying the SPB may have.
Running the OPatch with -report is not required, it is optional and meant to provide meaningful information
before actually applying the patches.
The report does not have to be submitted to Support when no conflicts or issues are found. If no conflicts are
found in the report, you may proceed to apply the SPB.
1. This step is optional to perform a report of what would happen when applying the SPB. Run the
following commands with the -report flag to produce a log to review:
cd <tmp_path_of_OPatch_packages>\WLS_SPB_12.2.1.3.<VERSION>\binary_patches
%ORACLE_HOME%\OPatch\opatch napply -report -oh %ORACLE_HOME% -
phBaseFile windows64_patchlist.txt
(Note: The windows64_patchlist.txt file is bundled into the SPB and you do not need to provide a path to
the file)
Once the opatch napply -report command is executed, review the output of the command and the logs it
produces to be aware of any possible issues.
No changes have been made to your Oracle home even though the command output may say that
patches were successfully applied.
cd <tmp_path_of_OPatch_packages>\WLS_SPB_12.2.1.3.<VERSION>\binary_patches
Once the opatch napply command is executed, review the output of the command and the logs it produces
to be aware of any possible issues.
Changes have been made to your Oracle home if this command was successful.
Refer to the SPB Patch list under Section 2 above to understand the list of expected patches in the lspatches
output.
%ORACLE_HOME%\OPatch\opatch lspatches
Note: For example the most popular Generic installation will have a minimum of the WLS PSU, Coherence
and ADR patches. Other patches are optional.
2. Refer the following document for Post-Install advice:
Doc ID 2764668.1 for Security Advice and Post-Install Information for Oracle WebLogic Server
PSUs
https:\\support.oracle.com\epmos\faces\DocumentDisplay?id=2764668.1
Rollback Steps
For complete rollback, use the backups (created before the application of SPB) to restore the
ORACLE_HOME and CENTRAL INVENTORY.