Patch 19271443 - Database Security Patch Update 11.2.0.4.0 (CPUOct2014)
Release 11.2.0.4 for UNIX
Released: October 14, 2014
This document is accurate at the time of release. For changes, terminal Critical Patch Update plans, and additional information regarding CPUOct2014, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
Document 1912224.1 Patch Set Update and Critical Patch Update October 2014 Availability Document
Document 1911781.1 Critical Patch Update October 2014 Oracle Database Known Issues
This document includes the following sections:
You should administer one Oracle product, one Oracle home at a time, for its particular Security Patch Update (SPU) October 2014 patch. Each Oracle home will have its own requirements.
Refer to My Oracle Support Document 1912224.1 Patch Set Update and Critical Patch Update October 2014 Availability Document to determine the order of applying CPU patches.
Starting from October 2012 onwards, Critical Patch Update (CPU) patches will now be called Security Patch Update (SPU) patches. The patches will still be released as part of the overall Oracle Critical Patch Update (CPU) Program. See My Oracle Support Document 1430923.1 - New Patch Nomenclature for Oracle Products.
Security Patch Update (SPU) patches are cumulative, which means fixes from previous Oracle security alerts and critical patch updates are included. It is not required to have previous security patches applied before applying this SPU patch. However, you must be on the stated patch set level for a given product home before applying the SPU patches for that release.
Table 1 describes installation types and SPU applicability. For each installation type, it indicates the most recent SPU 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 specific SPU is listed, then apply that SPU or any later SPU patch to be current with security fixes.
Table 1 Installation Types and SPU Applicability
| Installation Type | Latest SPU with Security Fixes |
|---|---|
|
Server homes |
SPU released for CPUOct2014 program. |
|
Client-Only Installations |
None |
|
Instant Client Installations |
None (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.) |
Components patched by this Security Patch Update:
Oracle Database
This section includes the following sections:
Section 3.2, "Patch Installation Instructions for Oracle Database Release 11.2.0.4"
Section 3.3, "Patch Deinstallation Instructions for Oracle Database"
These are pre-installation instructions for all Oracle Database installations.
From October 2014 onwards, the Oracle JavaVM Component 11.2.0.4.1 Database PSU patch is also available as a separate patch. This patch is not Oracle RAC Rolling Installable. For customers wanting to install both patches together during a single downtime window, follow the various Patching Options listed in the My Oracle Support Document 1929745.1 - Oracle Recommended Patches -- "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches.
You must use the OPatch utility version 11.2.0.3.4 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.
The n-Apply SPUs are cumulative patches. For further information, refer to My Oracle Support Document 438314.1 Critical Patch Update - Introduction to Database n-Apply CPU Patches.
An n-Apply SPU patch consists of groups of security fixes, where each group is called a molecule. Each molecule is an independent patch and does not conflict with any of the other molecule patches within the SPU. Prior to the patch installation, the following checks are performed for each molecule patch being installed:
Conflicts with other patches
Subset patches (patch to be installed is a subset of an existing patch in the Oracle Home)
Duplicates (patch to be installed is the same as an existing patch in the Oracle Home)
The My Oracle Support Conflict Checker tool enables you to upload an OPatch inventory and check the patches that you want to apply to your environment for conflicts.
If no conflicts are found, you can download the patches. If conflicts are found, the tool finds an existing resolution to download. If no resolution is found, it will automatically request a resolution, which you can monitor in the Plans and Patch Requests region of the Patches & Updates tab.
For more information, see Knowledge Document 1091294.1, How to use the My Oracle Support Conflict Checker Tool.
If a conflict is found during the installation, the installation will stop and you will be notified to file a merge request for the conflicting patches. To assist you in determining the best course of action when conflicts are reported, refer to My Oracle Support Document 835682.1, which documents the mapping of molecules to security vulnerabilities.
Select one of the following options:
Option 1: Resolve patch conflicts and install SPU together
File an SR for the merge request indicating all patches that conflict with the SPU as reported by OPatch.
Install the merge patches when they become available.
Install the SPU patch.
Option 2: Perform a partial installation of the SPU and resolve the conflicts later
At the conclusion of the aborted installation, OPatch returns the necessary command to install all molecules that do not conflict with patches in the Oracle home. Run this command to perform a partial SPU installation.
File an SR for the merge request indicating all patches that conflict with the SPU as reported by OPatch.
Install the merge patches when they become available.
If a subset or duplicate is found, the patch installation will continue. The subset and duplicate patches will not be installed as they are already installed.
These instructions are for all Oracle Database installations.
Follow these steps:
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.
If this is a RAC environment, install the SPU patch using the OPatch rolling (no downtime) installation method as the SPU patch is rolling RAC installable. Refer to My Oracle Support Document 244241.1 Rolling Patch - OPatch Support for RAC.
If this is not a RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
Ensure that the $PATH has the following executables: make, ar, ld, and nm.
The location of these executables depends on your operating system. On many operating systems, they are located in /usr/ccs/bin, in which case you can set your PATH as follows:
export PATH=$PATH:/usr/ccs/bin
Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
unzip p19271443_112040_<platform>.zip cd 19271443 opatch napply -skip_subset -skip_duplicate
Should OPatch return conflicts or subsets, refer to Section 3.1.2.1, "n-Apply SPUs and Patch Conflict Checking" for additional options.
If there are errors, refer to Section 4, "Known Issues".
After installing the patch, load modified SQL files into the database, as explained in Section 3.2.2.1.
The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.
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 cpu apply SQL> QUIT
The catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series CPU.
For information about the catbundle.sql script, see My Oracle Support Document 605795.1 Introduction to Oracle Database catbundle.sql.
Check the following log files in $ORACLE_BASE/cfgtoollogs/catbundle for any errors:
catbundle_CPU_<database SID>_APPLY_<TIMESTAMP>.log catbundle_CPU_<database SID>_GENERATE_<TIMESTAMP>.log
where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 4, "Known Issues".
These instructions are for a database that is created or upgraded after the installation of this SPU patch.
You must execute the steps in Section 3.2.2.1, "Loading Modified SQL Files into the Database" for any new database only if it was created by any of the following methods:
Using DBCA (Database Configuration Assistant) to select a sample database (General, Data Warehouse, Transaction Processing)
Using a script that was created by DBCA that creates a database from a sample database
There are no actions required for databases that have been upgraded.
These instructions apply if you need to deinstall the patch.
Section 3.3.1, "Patch Deinstallation Instructions for a Non-RAC Environment"
Section 3.3.2, "Patch Post-Deinstallation Instructions for a Non-RAC Environment"
Section 3.3.3, "Patch Deinstallation Instructions for a RAC Environment"
Section 3.3.4, "Patch Post-Deinstallation Instructions for a RAC Environment"
Follow these steps:
Verify that an $ORACLE_HOME/rdbms/admin/catbundle_CPU_<database SID>_ROLLBACK.sql file exists for each database associated with this ORACLE_HOME. If this is not the case, you must execute the steps in Section 3.2.2.1, "Loading Modified SQL Files into the Database" against the database before deinstalling the SPU.
Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
Run the OPatch utility using the specified rollback argument to rollback all molecule patches included in this SPU. If a molecule is not installed in the Oracle Home, the rollback will ignore it. If a molecule is installed as part of a merge patch, it will not be rolled back. If it is desired to rollback merge patches that have been applied to your Oracle Home, the rollback needs to be issued separately.
opatch nrollback -idFile $ORACLE_HOME/cpu/CPUOct2014/rollback_all.lst
If you have applied this SPU on top of a previous SPU, you may instead want to rollback only the molecule patches that are new in this SPU. To do so, use the following command:
opatch nrollback -idFile $ORACLE_HOME/cpu/CPUOct2014/rollback_new.lst
You may also rollback individual molecules or a list of molecules, as needed. Refer to the OPatch documentation on the nrollback command.
If there are errors, refer to Section 4, "Known Issues".
Follow these steps:
Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)
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_CPU_<database SID>_ROLLBACK.sql
SQL> QUIT
Check the log file for any errors. The log file is found in $ORACLE_BASE/cfgtoollogs/catbundle and is named catbundle_CPU_<database SID>_ROLLBACK_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 4, "Known Issues".
Follow these steps:
Shut down the instance on one node.
Shut down all nodeapps services on the node in step 1:
srvctl stop nodeapps -n <node-name>
Roll back the patch on the node in step 1.
Run the OPatch utility using the specified rollback argument to rollback all molecule patches included in this SPU. If a molecule is not installed in the Oracle Home, the rollback will ignore it. If a molecule is installed as part of a merge patch, it will not be rolled back. If it is desired to rollback merge patches that have been applied to your Oracle Home, the rollback needs to be issued separately.
opatch nrollback -idFile $ORACLE_HOME/cpu/CPUOct2014/rollback_all.lst -local
If you have applied this SPU on top of a previous SPU, you may instead want to rollback only the molecule patches that are new in this SPU. To do so, use the following command:
opatch nrollback -idFile $ORACLE_HOME/cpu/CPUOct2014/rollback_new.lst -local
You may also rollback individual molecules or a list of molecules, as needed. Refer to the OPatch documentation on the nrollback command.
If there are errors, refer to Section 4, "Known Issues".
Start all nodeapps services on the node in step 1:
srvctl start nodeapps -n <node-name>
Start the instance on the node in step 1.
Repeat steps 1-5 on all the remaining nodes in the cluster.
For information on the content of molecules when doing a rollback of this SPU, refer to My Oracle Support Document 1911780.1 "Critical Patch Update October 2014 Database Patch Security Vulnerability Molecule Mapping".
Follow these steps:
Go to the node that you used for the instructions in Section 3.3.1, "Patch Deinstallation Instructions for a Non-RAC Environment".
Follow the same set of instructions listed in Section 3.3.2, "Patch Post-Deinstallation Instructions for a Non-RAC Environment".
Users can start and access all other instances as usual while you are executing the steps from this instance.
Restart all nodeapps services on all nodes, one at a time:
srvctl start nodeapps -n <node-name>
Restart instances on all nodes.
You do not need to run post-deinstallation steps on other nodes. (That is, perform steps 1 and 2 only on the node selected in step 1, and perform steps 3 and 4 only once.)
For information about OPatch issues, see My Oracle Support Document 293369.1 OPatch documentation list.
For issues documented after the release of this SPU, see My Oracle Support Document 1911781.1 Critical Patch Update October 2014 Oracle Database Known Issues.
Other known issues are as follows.
The following ignorable errors may be encountered while running the catbundle.sql script or its rollback script:
ORA-29809: cannot drop an operator with dependent objects ORA-29931: specified association does not exist ORA-29830: operator does not exist ORA-00942: table or view does not exist ORA-00955: name is already used by an existing object ORA-01430: column being added already exists in table ORA-01432: public synonym to be dropped does not exist ORA-01434: private synonym to be dropped does not exist ORA-01435: user does not exist ORA-01917: user or role 'XDB' does not exist ORA-01920: user name '<user-name>' conflicts with another user or role name ORA-01921: role name '<role name>' conflicts with another user or role name ORA-01952: system privileges not granted to 'WKSYS' ORA-02303: cannot drop or replace a type with type or table dependents ORA-02443: Cannot drop constraint - nonexistent constraint ORA-04043: object <object-name> does not exist ORA-29832: cannot drop or replace an indextype with dependent indexes ORA-29844: duplicate operator name specified ORA-14452: attempt to create, alter or drop an index on temporary table already in use ORA-06512: at line <line number>. If this error follow any of above errors, then can be safely ignored. ORA-01927: cannot REVOKE privileges you did not grant
On HP-UX systems, the following ignorable warnings may be encountered during the relinking of the oracle binary:
WARNING:OUI-67215: OPatch found the word "failed" in the stderr of the make command.Please look at this stderr. You can re-run this make command. cc: warning 487: Possibly incorrect message catalog. total_lntt_bytes is 0, assuming size of .debug_lntt Failed to mmap lntt temp file.
On AIX systems, the following ignorable warnings may be encountered during the relinking of the oracle binary:
WARNING:OUI-67215: OPatch found the word "failed" in the stderr of the make command.Please look at this stderr. You can re-run this make command. ld: 0711-224 WARNING: Duplicate symbol: <symbol> ld: 0711-345 WARNING: Duplicate symbol: <symbol> ld: 0711-773 WARNING: Duplicate symbol: <symbol> ld: 0711-783 WARNING: Duplicate symbol: <symbol> ld: 0711-301 WARNING: Duplicate symbol: <symbol> ld: 0711-415 WARNING: Duplicate symbol: <symbol> ld: 0711-319 WARNING: Duplicate symbol: <symbol>
The following documents are references for this patch.
Document 293369.1 OPatch documentation list
Document 360870.1 Impact of Java Security Vulnerabilities on Oracle Products
Document 1561792.2 Patching Assistant: Oracle Database/Client - Select PSU/SPU (aka CPU)
This patch includes the following bug fixes.
SPU 11.2.0.4 for October 2014 contains all molecules previously released in previous SPU versions and the following new molecules:
| 19463893 - DB-11.2.0.4-MOLECULE-009-CPUOCT2014 | |
| 19463897 - DB-11.2.0.4-MOLECULE-010-CPUOCT2014 | |
| 19466309 - DB-11.2.0.4-MOLECULE-011-CPUOCT2014 | |
| 19544839 - DB-11.2.0.4-MOLECULE-012-CPUOCT2014 | |
| 19584068 - DB-11.2.0.4-MOLECULE-013-CPUOCT2014 |
The preceding CPUOct2014 molecules include the following bug fixes:
Enterprise Manager
18673304 - Fix for bug 18673304 18673325 - Fix for bug 18673325 18673342 - Fix for bug 18673342 19211724 - Fix for bug 19211724
JavaVM
19289642 - Fix for bug 19289642
PL/SQL
18641419 - Fix for bug 18641419
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/us/corporate/accessibility/index.html.
Access to Oracle Support
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.
Patch 19271443 - Database Security Patch Update 11.2.0.4.0 (CPUOct2014) for UNIX
Copyright © 2006, 2014, 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 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.