Académique Documents
Professionnel Documents
Culture Documents
Skip Header s
Section 2, "Prerequisites"
Section 3, "Installation"
Section 4, "Deinstallation"
Section 6, "References"
1 Patch Information
Windows Bundle Patch (BP) patches are cumulative. That is, the content of all previous BPs is included in the latest BP patch.
BP 11.2.0.4.170531 includes the fixes listed in Section 7, "Bugs Fixed by This Patch".
To install the BP 11.2.0.4.170531 patch, the Oracle home must have the 11.2.0.4.0 Database installed. Subsequent BP patches can be installed
on Oracle Database 11.2.0.4.0 or any BP with a lower 5th numeral version than the one being installed.
This patch contains a security fix due to which a SELECT query's plan MAY change under the following conditions:
The SELECT queries a table protected with a Fined Grained Auditing policy
Windows Server 2003 R2, Standard, Enterprise and Datacenter x64 Edition
Windows 7
Windows 8
Windows 2012
Windows 2012 R2
Table 1 describes installation types and security content. For each installation type, it indicates the most recent BP patch to include new security
fixes that are pertinent to that installation type. If there are no security fixes to be applied to an installation type, then "None" is indicated. If a
1 of 11 9/4/2019, 1:52 PM
Oracle® Database Patch for Microsoft Windows (x64) https://updates.oracle.com/Orion/Services/download?type=readme&aru...
specific BP is listed, then apply that or any later BP patch to be current with security fixes.
(The Instant Client installation is not the same as the client-only Installation. For additional information about
Instant Client installations, see Oracle Call Interface Programmer's Guide.)
IMPORTANT NOTES
-----------------------------
1. For customers using Oracle Advanced Security Transparent Data Encryption with auto-login wallets on Oracle Database 11.2.0.4:
If you use Oracle Advanced Security Transparent Data Encryption, and use auto-login wallets, then note the following when turning on
FIPS configuration in the database via setting "_use_fips_mode=TRUE" in the init.ora parameter.
1). Remove the auto-login wallet file cwallet.sso (please be careful not to remove the pkcs12 wallet, ewallet.p12),
2). Perform the rekey operation using for instance ALTER SYSTEM SET ENCRYPTION KEY IDENTIFIED BY "y0ur_Mall3t_bmp!",
3). Use orapki to generate a new auto-login wallet using for instance orapki wallet create -wallet . -auto_login -compat_v12
or orapki wallet create -wallet . -auto_login_local -compat_v12.
This will ensure that the auto_login wallet is also using a FIPS approved algorithm.
In 11.2.0.4 Orapki uses “MD5” as default to sign certificates if no “–sign_algo” is specified. Since ACCEPT_MD5_CERTS
is set to FALSE by default, customers would need to specify the “-sign_algo” option to Orapki to sign the certificates
using “SHA256”. If ACCEPT_MD5_CERTS is set to TRUE, then “-sign_algo” does not need to be specified.
2 Prerequisites
This section includes the following section:
2 of 11 9/4/2019, 1:52 PM
Oracle® Database Patch for Microsoft Windows (x64) https://updates.oracle.com/Orion/Services/download?type=readme&aru...
You must use the OPatch utility version 11.2.0.3.5 or later to apply this patch. Oracle recommends that you use the latest released OPatch version
for 11.2, which is available for download from My Oracle Support patch 6880880 by selecting the 11.2.0.0.0 release.
For information about OPatch documentation, including any known issues, see My Oracle Support Document 293369.1 OPatch documentation
list.
3 Installation
These instructions are for all Oracle Database installations.
Section 3.4, "Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of BP 11.2.0.4.170531 in the Oracle
Home"
Before you install BP 11.2.0.4.170531, perform the following actions to check the environment.
1. Perform a clean shutdown of all Oracle services (databases, Oracle listeners, Oracle agents, and so on.) that run from the Oracle Home
where you install this patch.
2. Stop all Oracle services, Recovery catalog, ODBC applications, and other applications that use Oracle Client. This may include Web
servers that load the Oracle client in the mid-tier environment.
4. Make sure %ORACLE_HOME%\perl\bin appears in your PATH setting. if not please follow the below step
set PATH=%ORACLE_HOME%\perl\bin;%PATH%
5. Query current_scn from v$database, make sure it's less than 15169738620928
Note: If you are using a Data Guard Physical Standby database, you must install this patch on both the primary database and the physical
standby database, as described by My Oracle Support Document 278641.1.
1. Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database
Administrator's Guide.
2. Set the ORACLE_HOME environment variable pointing to your Database Home, go to the directory where the patch is located and then run
the OPatch utility by entering the following commands:
unzip p25874796_112040_MSWIN-x86-64.zip
cd 25874796
opatch apply
Important: Follow these steps on each node in the cluster, one node at a time.
The order of patching in RAC environment is Grid Home followed by Database Home
3 of 11 9/4/2019, 1:52 PM
Oracle® Database Patch for Microsoft Windows (x64) https://updates.oracle.com/Orion/Services/download?type=readme&aru...
1. Before patching Grid Home, stop OCR related resources, 'unlock' the Grid Home to prepare it for patching and stop Oracle High Availability
Services (OHASD) & all Oracle Services:
> srvctl stop service -d <database name> -s <configured workload management service> -i <instance name>
> srvctl stop instance -d <database name> -i <instance name>
> set ORACLE_HOME=<path to Grid Infrastructure home>
> %ORACLE_HOME%\perl\bin\perl -I%ORACLE_HOME%\perl\lib -I%ORACLE_HOME%\crs\install %ORACLE_HOME%\crs
\install\rootcrs.pl -unlock
Note: 'rootcrs.pl -unlock' includes stopping Oracle Clusterware on the local node.
2. Verify that there are no longer any resources running on the node to be patched, run the following command from another node with Grid
running:
3. Use the Computer Management Services GUI (services.msc) to ensure ALL 'Oracle' services are stopped on that node by running
If any service is found running , then use the Computer Management Services GUI or the net stop command to stop them. Example-
4. Explicitly disable and stop the (non-Oracle) Windows Management Instrumentation service.
5. Apply the patch to Grid Home using steps: (make sure ORACLE_HOME is pointing to the Grid Infrastructure home.)
unzip p25874796_112040_MSWIN-x86-64.zip,
cd 25874796
<path to latest version of opatch>\opatch apply -local
6. Apply the patch to Database Home using steps: (make sure ORACLE_HOME is pointing to the Database home.)
cd 25874796
<path to latest version of opatch>\opatch apply -local
10. Distributed Transaction Coordinator and Windows Management Instrumentation Service can now be started.
a. %ORACLE_HOME%\bin\crssetup deinstallfence
b. Reboot the node for change to take effect.
c. %ORACLE_HOME%\bin\crssetup installfence
d. Reboot the node for change to take effect.
4 of 11 9/4/2019, 1:52 PM
Oracle® Database Patch for Microsoft Windows (x64) https://updates.oracle.com/Orion/Services/download?type=readme&aru...
Ensure all services and resources listed in step 1 have been stopped before copying the ocfs.sys
replace ocfs.sys with ocfs.sys.w2k364 supplied in the patch 24591648. Note that the filename in %SystemRoot%\System32\drivers is
required to be ocfs.sys and reboot the node.
When copying OCFS drivers you may need to reboot the node.
6. To patch 2nd or more remote nodes, make sure to the make patch staging area (and any newer opatch download) or unzipped patch
available locally. Then repeat all steps from this section (3.2.2) on all nodes
1. Load modified SQL files into the database, as explained in Section 3.3.1
The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.
1. For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as SYSDBA
and run the catbundle.sql script as follows:
cd %ORACLE_HOME%\rdbms\admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle.sql PSU apply
SQL> QUIT
The catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series.
For information about the catbundle.sql script, see My Oracle Support Document 605795.1 Introduction to Oracle Database
catbundle.sql.
catbundle_PSU_<database SID>_APPLY_<TIMESTAMP>.log
catbundle_PSU_<database SID>_GENERATE_<TIMESTAMP>.log
where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 5, "Known Issues".
If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it:
Set the following parameter in init.ora in order to use the new RSA MES libraries in FIPS compliant mode
_use_fips_mode=true
OR
_use_fips_mode=TRUE
3.4 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of BP 11.2.0.4.170531 in the
5 of 11 9/4/2019, 1:52 PM
Oracle® Database Patch for Microsoft Windows (x64) https://updates.oracle.com/Orion/Services/download?type=readme&aru...
Oracle Home
There are no actions required for databases that have been upgraded or created after installation of BP 11.2.0.4.170531
For OUI based Client-Admin installations, the 'opatch apply' takes care of updating your installation with these latest Instant Client binaries.
For Other types of Instant Client installations, refer Document 1072125.1 How to Apply a Patch to an Oracle Instant Client Installation.
Oracle does not add its patched .NET assemblies to the Global Assembly Cache (GAC) by default. These assemblies include:
You can add these assemblies to the GAC by following these steps:
To remove an Oracle .NET assembly from the GAC, follow steps 1 and 2. For the next step, execute the following:
4 Deinstallation
These instructions apply if you need to deinstall the patch.
2. Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database
Administrator's Guide.
unzip p25874796_112040_MSWIN-x86-64.zip
cd 25874796
opatch rollback -id 25874796
6 of 11 9/4/2019, 1:52 PM
Oracle® Database Patch for Microsoft Windows (x64) https://updates.oracle.com/Orion/Services/download?type=readme&aru...
1. Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)
2. For each database instance running out of the ORACLE_HOME, connect to the database using SQL*Plus as SYSDBA and run the rollback
script as follows:
cd %ORACLE_HOME%\rdbms\admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle_PSU_<database SID>_ROLLBACK.sql
SQL> QUIT
In a RAC environment, the name of the rollback script will have the format catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql.
3. Check the log file for any errors. The log file is found in %ORACLE_BASE%\cfgtoollogs\catbundle and is named
catbundle_BP_<database SID>_ROLLBACK_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If
there are errors, refer to Section 5, "Known Issues".
Important: Follow these steps on each node in the cluster, one node at a time.
The order of uninstalling in RAC environment is Database Home followed by Grid Home
1. Uninstalling patch from database home: Before uninstalling the patch from Database Home, the ASM and GRID services can be
running
> srvctl stop service -d <database name> -s <configured workload management service> -i <instancename>
> srvctl stop instance -d <dbname> -i <instance name>
2. Set the ORACLE_HOME environment variable pointing to your Database Home and then run the OPatch utility by entering the following
command
3. Uninstalling patch from Grid home: Before uninstalling the patch from Grid Home, 'unlock' the Grid Home to prepare it for patching and
stop Oracle High Availability Services (OHASD) & all Oracle Services:
To verify that there are no longer any resources running on the node to be un-patched, run the following command from another node with
GRID running:
Then use the Computer Management Services GUI or the net stop command to stop ALL Oracle services running on that node:
4. Set the ORACLE_HOME environment variable pointing to your Grid Home and then run the OPatch utility by entering the following command
7 of 11 9/4/2019, 1:52 PM
Oracle® Database Patch for Microsoft Windows (x64) https://updates.oracle.com/Orion/Services/download?type=readme&aru...
5. Start Oracle HASD Services (OHASD) and the oracle instance on the node by running the following commands
Follow the instructions listed in Section Section 4.2, "Patch Post-Deinstallation Instructions for a Non-RAC Environment" only on the node for
which the steps in Section 3.3.1, "Loading Modified SQL Files into the Database" were executed during the patch application.
All other instances can be started and accessed as usual while you are executing the deinstallation steps.
5 Known Issues
For information about OPatch issues, see My Oracle Support Document 293369.1 OPatch documentation list.
For information on Known Issues with 11.2.0.4 Windows bundles, refer to Oracle Database Windows Bundle Patches 11.2.0.4 Known Issues
Document 2003218.1
Issue 1
The following ignorable errors may be encountered while running the catbundle.sql script or its rollback script:
Issue 2
Following object will be left invalid after running through Patch Post-deinstallation steps.
OWNER OBJECT_TYPE OBJECT_NAME
--------- ------------------- ------------------------------
SYS PACKAGE BODY DBMS_CAPTURE_ADM_IVK
Issue 3
Following object will be left invalid after running through Patch Post-deinstallation steps.
OWNER OBJECT_TYPE OBJECT_NAME
8 of 11 9/4/2019, 1:52 PM
Oracle® Database Patch for Microsoft Windows (x64) https://updates.oracle.com/Orion/Services/download?type=readme&aru...
Issue 4
Following bug(s) will be listed in opatch lsinventory output. These are not part of the bundle patch and have been pulled out.
18973907 - REMOVE NEW RPC FOR NULL INDEX STATS ADDED IN BUG 5702977
18006980 - LISTENER INTERMEDIATE(NOT ALL ENDPOINTS REGISTERED) WHEN USE DNS TO RESOLVE SCAN
21201481 - LISTENER LISTENS SCAN VIP IP ADDRESS ON WIN2012R2
6 References
The following documents are references for this patch.
Document 2003218.1 Oracle Database Windows Bundle Patches 11.2.0.4 Known Issues.
See My Oracle Support Document 1114533.1 that documents all the non-security bugs fixed in each 11.2.0.4 Windows Bundle Patch (BP).
Advance Queuing
25029022 - ORA-4031 WITH LARGE ALLOCATION TO KTC LATCH SUBH ON DEQUEUE
25182817 - INCORRECT BROWSE COUNT IN V$PERSISTENT_QUEUES WHEN DEQUEUE ROLLS BACK
Generic
18892426 - ORA-600 [QERNSROWP] ON SELECT DISTINCT
21918368 - JPPD IS REJECTED IF TABLE EXPRESSION IS INSIDE UNION ALL IN 11.2.0.4
22113854 - EXADATA: ON 12.1.0.2- CLIENT QUERY EXPERIENCING VERY POOR PERFORMANCE
23102157 - A LOT OF KKJCRE1P MESSAGES DURING SHUTDOWN
25335790 - EXADATA:ORA-600 [KKSGAGETNOALLOC_INT0] ON ACTIVE DATABASE
25423453 - Fix for bug 25423453
High Availability
17532245 - LNX64-12.1-ASM, LMS0 HIT ORA-600 [KJBLFR:!CLN],DB INST CRASH
17607713 - ORA-270 WHEN FAL SHIPS LOGS WITH MAX_CONNECTIONS=4
Oracle Security
24469107 - MISSING LOGIN DELAY (_SYS_LOGON_DELAY) WHEN FAILED_LOGIN_ATTEMPTS IS UNLIMITED
25639019 - TDE NOT INITIALIZING FIPS FOR NZ PROPERLY
25790353 - ADD SQLNET.ORA PARAMETERS ACCEPT_MD5_CERTS AND ACCEPT_SH1_CERTS
26091622 - MES:11.2.0.4 MEM LEAK IN SSL CLIENT APPLICATION PERFORMING LOGIN,LOGOUT IN LOOP
9 of 11 9/4/2019, 1:52 PM
Oracle® Database Patch for Microsoft Windows (x64) https://updates.oracle.com/Orion/Services/download?type=readme&aru...
Server Manageability
23089357 - APPSST12102:SHUTDOWN FAILS WITH ORA-449 "BACKGRND PROCESS ''MMNL' UNEXPECTEDLY
8 Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/us/corporate
/accessibility/index.html.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html
or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.
Copyright © 2006, 2017, Oracle and/or its affiliates. All rights reserved.
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 is software or related documentation that 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 America, Inc., 500
Oracle Parkway, Redwood City, CA 94065.
This software or hardware 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 that may create a risk of personal injury. If you use this software or hardware
in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
10 of 11 9/4/2019, 1:52 PM
Oracle® Database Patch for Microsoft Windows (x64) https://updates.oracle.com/Orion/Services/download?type=readme&aru...
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous
applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or
registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd.
This software or hardware 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 © 2006, 2017, Oracle and/or its affiliates. All rights reserved.
11 of 11 9/4/2019, 1:52 PM