Professional Documents
Culture Documents
201020
-----------------------------------------------------------
WLS Patch ID - NA7A
WLS Patch Number - 31641257
This README provides information about how to apply WLS Patch Set Update
10.3.6.0.201020.
It also provides information about reverting to the original version.
- My Oracle Support NOTE: 1306505.1 Announcing Oracle WebLogic Server PSUs (Patch
Set Updates)
�https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1306505.1
- My Oracle Support NOTE: 1470197.1 Master Note on WebLogic Server Patch Set
Updates (PSUs)
�https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1470197.1
- Download the Error Correction Policy document and see "4.2 Policies - Critical
Patch Update Program"
https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=944866.1
- It is required to use Java SE 7 with WLS 10.3.6 as Java SE 6 has reached the end
of Extended Support
https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=952075.1
- WebLogic Server Patch Set Update (PSU) can be applied on a per-domain basis (or
on a more fine-grained basis), Oracle recommends that PSU
� be applied on an installation-wide basis. PSU applied to a WebLogic Server�
installation using this recommended practice affect all domains and
� servers sharing that installation.
- Remove any previously applied WebLogic Server Patch Set Update and associated
overlay patches
� JDK 7 Update 191 (JDK 7u191) or later (for WebLogic Server versions that are
supported on JDK 7)
� Refer to the following for further information: Doc ID 1506916.1 Obtaining Java
SE (JDK/JRE) for Oracle Fusion Middleware Products
� https://support.oracle.com/rs?type=doc&id=1506916.1
https://support.oracle.com/epmos/faces/DocumentDisplay?id=2458832.1
WLS BSU (Smart Update) Takes a Very Long Time to Apply Patches - Especially When
Checking for Patch Conflicts
https://support.oracle.com/epmos/faces/DocumentDisplay?id=2271366.1
Diagnosing "Encountered unrecognized patch ID" Failures When Trying to Patch WLS
Using BSU
https://support.oracle.com/epmos/faces/DocumentDisplay?id=1186923.1
Conflict Detected - New PSU for WLS 10.3.6 is "mutually exclusive and cannot
coexist with patch(es)"
https://support.oracle.com/epmos/faces/DocumentDisplay?id=2267696.1
�
Native Windows Zip/Unzip Tools Fail to Extract Patch Zip Files - "Path Too Long"
or "is Invalid" Errors
https://support.oracle.com/epmos/faces/DocumentDisplay?id=2259579.1
�� If you are using a Java security manager (for example, you use -
Djava.security.manager to start up WebLogic Server),
��you must ensure that the codeBase in your policy file points to the location
where the patches are installed.
��The policy file is specified by -Djava.security.policy during server startup.
��By default, this is weblogic.policy file and resides in WL_HOME/server/lib,
where WL_HOME is the WebLogic Server installation directory.
�
�� This is an example of what should be added to the weblogic.policy file for the
installed patches:
�
�� grant codeBase "file:<path-to-WLS-patch-jars>/patch_wls1036/patch_jars/-" {
������� permission java.security.AllPermission;
�� };
�
� The default weblogic.policy file is a sample. If you use it, you must modify it.
Refer to the following URL for additional information:
�
� http://download.oracle.com/docs/cd/E17904_01/web.1111/e13711/server_prot.htm �
�
4. A note about FMW 11g installations using PSU patch 10.3.6.0.201020 or later
versions.
�� You may see this error after starting the Admin Server :
-----------------------------------------------------------------------------------
------------------
DISCLAIMER:
Oracle recommends this Patch Set Update (PSU) for development and production
systems in accordance with Doc ID 1306505.1.
�
This PSU may conflict with an interim patch(es) that has been applied to customer
systems. If a patch conflict is identified, customers should determine, through
review of the bugs fixed list, whether the interim patch was included in the PSU.
If the interim patch is included in the PSU, the interim patch does not need to be
applied to systems where the PSU is applied.��� If the interim patch is not
included in the PSU, the conflict probably arises because the PSU modifies the same
module as the interim patch. In such cases, customers should contact Oracle
Support, provide information about all patches applied to the system, and request
an overlay patch(es) that will resolve the conflict.
�
This software and related documentation are provided under a license agreement
containing restrictions on use and disclosure and are protected by intellectual
property laws. Except as expressly permitted in your license agreement or allowed
by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form,
or by any means. Reverse engineering, disassembly, or decompilation of this
software, unless required by law for interoperability, is prohibited.
�
The information contained herein is subject to change without notice and is not
warranted to be error-free. If you find any errors, please report them to us in
writing.
�
If this software or related documentation is delivered to the U.S. Government or
anyone licensing it on behalf of the U.S. Government, the following notice is
applicable:
�
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation
and technical data delivered to U.S. Government customers are "commercial computer
software" or "commercial technical data" pursuant to the applicable Federal
Acquisition Regulation and agency-specific supplemental regulations. As such, the
use, duplication, disclosure, modification, and adaptation shall be subject to the
restrictions and license terms set forth in the applicable Government contract,
and, to the extent applicable by the terms of the Government contract, the
additional rights set forth in FAR 52.227-19, Commercial Computer Software License
(December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
�
This software is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous
applications, including applications which may create a risk of personal injury. If
you use this software in dangerous applications, then you shall be responsible to
take all appropriate fail-safe, backup, redundancy, and other measures to ensure
the safe use of this software. Oracle Corporation and its affiliates disclaim any
liability for any damages caused by use of this software in dangerous applications.
�
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
Other names may be trademarks of their respective owners.
�
This software and documentation may provide access to or information on content,
products, and services from third parties. Oracle Corporation and its affiliates
are not responsible for and expressly disclaim all warranties of any kind with
respect to third-party content, products, and services. Oracle Corporation and its
affiliates will not be responsible for any loss, costs, or damages incurred due to
your access to or use of third-party content, products, or services.
Copyright���2020,�Oracle�and/or�its�affiliates.�All�rights�reserved.