Patch 18031668 - 11.2.0.4.2 Patch Set Update
Released: April 15, 2014
This document is accurate at the time of release. For any changes and
additional information regarding PSU 11.2.0.4.2, see these related
documents that are available at My Oracle Support (http://support.oracle.com/):
Document 1618213.1 Patch Set Update and Critical Patch Update April 2014 Availability Document
Document 854428.1 Patch Set Updates for Oracle Products
Document 1615893.1 Oracle Database Patch Set Update 11.2.0.4.2 Known Issues
This document includes the following sections:
Patch Set Update (PSU) patches are cumulative. That is, the content of all previous PSUs is included in the latest PSU patch.
PSU 11.2.0.4.2 includes the fixes listed in Section 7, "Bugs Fixed by This Patch".
To install the PSU 11.2.0.4.2 patch, the Oracle home must have the 11.2.0.4.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 11.2.0.4.0 or any PSU with a lower 5th numeral version than the one being installed.
This patch is Oracle RAC Rolling Installable.
This patch is Data Guard Standby-First Installable. See My Oracle Support Document 1265700.1 Oracle Patch Assurance - Data Guard Standby-First Patch Apply for details on how to remove risk and reduce downtime when applying this patch.
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
And the policy condition is NULL
Table 1 describes installation types and security content. For each installation type, it indicates the most recent PSU 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 PSU is listed, then apply that or any later PSU patch to be current with security fixes.
Table 1 Installation Types and Security Content
| Installation Type | Latest PSU with Security Fixes |
|---|---|
|
Server homes |
PSU 11.2.0.4.2 |
|
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.) |
This section includes the following section:
You must use the OPatch utility version 11.2.0.3.6 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.
These instructions are for all Oracle Database installations.
Before you install PSU 11.2.0.4.2, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.
If you are installing the PSU to an environment that has a Grid Infrastructure (GI) home, note the following:
Grid Infrastructure PSU 11.2.0.4.2 Patch 18139609 should be applied to the Grid Infrastructure home and Database home using the readme instructions provided with the patch.
Ensure that the $PATH definition 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 definition as follows:
export PATH=$PATH:/usr/ccs/bin
For an introduction to the PSU one-off patch concepts, see "Patch Set Updates Patch Conflict Resolution" in My Oracle Support Document 854428.1 Patch Set Updates for Oracle Products.
The fastest and easiest way to determine whether you have one-off patches in the Oracle home that conflict with the PSU, and to get the necessary conflict resolution patches, is to use the Patch Recommendations and Patch Plans features on the Patches & Updates tab in My Oracle Support. These features work in conjunction with the My Oracle Support Configuration Manager. Recorded training sessions on these features can be found in Document 603505.1.
However, if you are not using My Oracle Support Patch Plans, follow these steps:
Determine whether any currently installed one-off patches conflict with the PSU patch as follows:
unzip p18031668_112040_<platform>.zip cd 18031668 opatch prereq CheckConflictAgainstOHWithDetail -ph ./
The report will indicate the patches that conflict with PSU 18031668 and the patches for which PSU 18031668 is a superset.
Note that Oracle proactively provides PSU 11.2.0.4.2 one-off patches for common conflicts.
Use My Oracle Support Document 1321267.1 Database Patch conflict resolution to determine, for each conflicting patch, whether a conflict resolution patch is already available, and if you need to request a new conflict resolution patch or if the conflict may be ignored.
When all the one-off patches that you have requested are available at My Oracle Support, proceed with Section 3.2, "Patch Installation Instructions".
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 an Oracle RAC environment, install the PSU patch using the OPatch rolling (no downtime) installation method as the PSU patch is rolling Oracle RAC installable. Refer to My Oracle Support Document 244241.1 Rolling Patch - OPatch Support for RAC.
If this is not a Oracle 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.
Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
unzip p18031668_112040_<platform>.zip
cd 18031668
opatch apply
If there are errors, refer to Section 5, "Known Issues".
After installing the patch, perform the following actions:
Apply conflict resolution patches as explained in Section 3.3.1.
Load modified SQL files into the database, as explained in Section 3.3.2.
Apply the patch conflict resolution one-off patches that were determined to be needed when you performed the steps in Section 3.1.3, "One-off Patch Conflict Detection and Resolution".
The following steps load modified SQL files into the database. For an Oracle 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 psu apply SQL> QUIT
The catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series PSU.
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_HOME/cfgtoollogs/catbundle or $ORACLE_BASE/cfgtoollogs/catbundle for any errors:
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".
There are no actions required for databases that have been upgraded or created after installation of PSU 11.2.0.4.2.
These instructions apply if you need to deinstall the patch.
Section 4.1, "Patch Deinstallation Instructions for a Non Oracle RAC Environment"
Section 4.2, "Patch Post-Deinstallation Instructions for a Non Oracle RAC Environment"
Section 4.3, "Patch Deinstallation Instructions for an Oracle RAC Environment"
Section 4.4, "Patch Post-Deinstallation Instructions for an Oracle RAC Environment"
Follow these steps:
Verify that an $ORACLE_HOME/rdbms/admin/catbundle_PSU_<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.3.2, "Loading Modified SQL Files into the Database" against the database before deinstalling the PSU.
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 specifying the rollback argument as follows.
opatch rollback -id 18031668
If there are errors, refer to Section 5, "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_PSU_<database SID>_ROLLBACK.sql
SQL> QUIT
In an Oracle RAC environment, the name of the rollback script will have the format catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql.
Check the log file for any errors. The log file is found in $ORACLE_BASE/cfgtoollogs/catbundle and is named catbundle_PSU_<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".
Follow these steps for each node in the cluster, one node at a time:
Shut down the instance on the node.
Run the OPatch utility specifying the rollback argument as follows.
opatch rollback -id 18031668
If there are errors, refer to Section 5, "Known Issues".
Start the instance on the node as follows:
srvctl start instance –d <db-unique-name> -n <nodename>
Follow the instructions listed in Section Section 4.2, "Patch Post-Deinstallation Instructions for a Non Oracle RAC Environment" only on the node for which the steps in Section 3.3.2, "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.
For information about OPatch issues, see My Oracle Support Document 293369.1 OPatch documentation list.
For issues documented after the release of this PSU, see My Oracle Support Document 1615893.1 Oracle Database Patch Set Update 11.2.0.4.2 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
Warnings may be returned during the re-link phase of 18031668. These warnings may be ignored.
warning: overriding commands for target `nmosudo' warning: ignoring old commands for target `nmosudo'
See the following document for additional information.
Document 1562458.1 Relinking the DB Control 11.2.0.3 Agent Displays a Warning Message "overriding commands for target 'nmosudo'"
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>
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 1321267.1 Database Patch conflict resolution
Document 18031668.8 Database 11.2.0.4.2 Patch Set Update (PSU)
Document 1449750.1 11.2.0.4 Patch Set Updates - List of Fixes in each PSU
Document 1561792.2 Patching Assistant: Oracle Database/Client - Select PSU/SPU (aka CPU)
This patch includes the following bug fixes.
CPU molecules in PSU 11.2.0.4.2:
PSU 11.2.0.4.2 contains the following new PSU 11.2.0.4.2 molecules:
| 18203835 - DB-11.2.0.4-MOLECULE-005-CPUAPR2014 | |
| 18203837 - DB-11.2.0.4-MOLECULE-006-CPUAPR2014 | |
| 18203838 - DB-11.2.0.4-MOLECULE-007-CPUAPR2014 |
See My Oracle Support Document 1611785.1 that documents all the non-security bugs fixed in each 11.2.0.4 Patch Set Update (PSU).
PSU 11.2.0.4.2 contains the following new fixes:
Automatic Storage Management
| 16618694 - PST PLACEMENT ON ODA DOES NOT TAKE INTO CONSIDERATION THE DISKGROUP REDUNDANCY | |
| 16875449 - GMON TRIES TO OPTIMIZE METADATA (PST) PLACEMENT IN AN INFINITE LOOP | |
| 17071721 - LNX64-112-CMT: ORA-600 [723], [313152], [MEMORY LEAK] DURING REBOOTING | |
| 17296856 - ORA-15405 - SLOT X IN ORACLE ASM APPLIANCE 'ODA' CONTAINS MORE THAN ON... | |
| 17385178 - ORA-600 [KFGPSET3], [HDD_E1_S10_966578543P2], [10], [65535], [4] | |
| 17783588 - KFDUPDTDSKHLTH DOES NOT CLEAR ERROR ORA-15001 |
Buffer Cache Management
| 17323222 - ORA-3170: DEADLOCKED ON READABLE PHYSICAL STANDBY (UNDO SEGMENT X) | |
| 17437634 - ORA-600[6856] FOR TEMP BLOCKS AFTER CTRL-C OR A SESSION KILL | |
| 17752121 - ADDITIONAL DIAGNOSTICS TO AVOID BUFFER MODIFIED IN SHARED MODE IN RAC | |
| 17761775 - JOINT OF TEMP AND PERMANENT TABLE IN RAC MIGHT LEAD TO CORRUPTION |
Generic
| 16043574 - AGGREGATE QUERY ON FIXED VIEWS FAIL WITH ORA-600 [ROWIRW CHECK RET VAL] | |
| 16180763 - INCORRECT LENGTH CALCULATION OF TYPE DESCRIPTORS WITH COLLECTIONS OF UDT | |
| 16731148 - ORA-01882 WHEN SELECTING TIMESTAMP LITERALS VIA DB-LINK OR USING INSERT | |
| 16929165 - ORA-900 / ORA-4045 WHEN DROPPING PACKAGE BODY IN OLD EDITION | |
| 17050888 - PERFORMING DDL ON A TABLE OR VIEW LEAVES BEHIND TRIGGERS THAT WERE DEFINED ON IT | |
| 17325413 - DROPPED COLUMN WRITTEN TO DISK BLOCK | |
| 17346671 - ORA-3106 WHEN SELECTING AN EMPTY LOB OVER THE LONG INTERFACE | |
| 17468141 - PL/SQL COMPILATION THROWS ERROR ORA-4063 |
High Availability
| 14133975 - LMS HIT ORA-600 [KJBMICLO:CREQ] AND INSTANCE CRASH | |
| 16220077 - PIECEWISE LOB UPDATE OF COMPRESSED INLINE LOB FAILS REPLICATE WITH INTENAL ERROR | |
| 16228604 - KGLUNLOCK-BAD-LOCK ERROR IN CAPTURE WHEN LOGMINER CAN'T FIND A MISSING REDO LOG | |
| 16399083 - TRANSPORT LAG IS SUDDENLY GOT HIGH VALUE | |
| 16472716 - LSBY: ORA-22920 OCCURS WHEN APPLYING PIECE-WISE LOB OPERATION | |
| 17186905 - FLASHBACK DB ON STANDBY SINGALS ORA-38861 UNNECESSARILY | |
| 17284817 - SWITCHOVER TO STANDBY HUNG USING BROKER VIA SITEGUARD | |
| 18094246 - INCORRECT USAGE OF SPARE KSPASV20 |
Oracle Security
| 17716305 - Fix for bug 17716305 |
Oracle Security Service
| 17865671 - Fix for bug 17865671 |
Oracle Space Management
| 10136473 - CELLSRV FAILS DUE TO ORA-7445 [KAF4F0RST9IR2SRP1] | |
| 14010183 - ORA-600 [KTSPFUNDO:OBJDCHK_KCBGCUR_3] DURING MERGE LOAD | |
| 16785708 - DBMS_REDEFINITION ON A TABLE WITH A LOB COLUMN CAN CAUSE INTERNAL ERROR |
Oracle Storage Server Service Layer
| 13364795 - COLUMNAR SMART SCAN CAN FAIL TO RECOVER FROM A CORRUPT BLOCK | |
| 16613964 - USELESS/IMPROPER INFO IN THE APX TRACE LOG | |
| 16837842 - OUT OF MEMORY ERROR (ORA-4030) WITH KCFIS REQUESTS | |
| 16863422 - ORA-600 [KXDAM_NOTIFY_CELL:IOCTLFAILED] DURING RPM UPGRADE | |
| 17080436 - DUMP MAP ELEMENTS OF COMPLETED BUFFERS IN KCFIS | |
| 17265217 - X2-8: INCONSISTENT ASMDEACTIVATIONOUTCOME DURING SCRUB RESILVERING | |
| 17465741 - ORA-600 KCFIS_DECR_OVERHEADMEM_LEN_1 WITH LARGE FILE CREATION / HIGH REDUNDANCY | |
| 17546761 - GRIDDISK RESILVERING TAKES FOREVER. | |
| 17602269 - ASM HUNG. DSKM WAITING ON SKGZNP_READ_MSG | |
| 17614227 - XDMG DOESN'T WAIT FOR RESYNC PREVENTING PROMPT RESILVER COMPLETION | |
| 17726838 - OSS TCP CONNECT ERROR IS INCORRECT |
Oracle Streams
| 14338435 - SR11.2.0.4HEAPCHECK512 - TRC - KNASALD | |
| 16912439 - OGG-2028 FAILED TO ATTACH: KNLCIDUMPCAPTUREVDOLLARVIEWINFO ERR 1403 | |
| 16943711 - XSTREAM INBOUND ENCOUNTERS ORA-60 DEADLOCK ERROR CONSISTENTLY ON EHCC TABLES | |
| 16956380 - ORA-7445 [KNALSALEX()+378] DURING LOB ASSEMBLY ERROR FOR INTEGRATED REPLICAT | |
| 17016369 - ORA-1: UNIQUE CONSTRAINT (SYS.STREAMS$_APPLY_ERROR_TXN_UNQ) | |
| 17027426 - IR DOESNT ABEND WHEN NULL VALUES ARE USED FOR DELTA RESOLUTION IN CDR | |
| 17040764 - XSTREAM INBOUND INCORRECTLY SKIPS THE DIRECT PATH APPLY SETTING IN OGG LCR | |
| 17082359 - ORA-60 DEADLOCK SEEN WHEN APPLYING INTO SECUREFILE COLUMNS WITH DEDUP ON | |
| 17205719 - OGG: IR SHOWS INCORRECT DML STATS NOT MATCHING WITH ACTUAL DMLS APPLIED | |
| 17235750 - OGG: IR HANGS REPEATEDLY WHEN APPLYING MIXED WORKLOAD TXNS | |
| 17341326 - OGG BETA: INTEG. REPLICAT - VARIOUS ORA-600/ORA-7445 ERRORS FROM XSTREAMS | |
| 17344412 - OGG: IR HANGS REPEATEDLY DURING BATCH TXNS | |
| 17375354 - OGG: IR APPLY SLAVES PERIODICALLY LOG 'KNALSGLCR:NIL LCR POINTER' IN AS TRACES | |
| 17389192 - OGG: IR ABENDS DUE TO ORA-00600 [KNLQGLCR:2] DURING REPEATED COLLISIONS HANDLIN | |
| 17390431 - DOWNSTREAM CAPTURE MAY DOWNGRADE TO NON RTM MODE UNNECESSARILY | |
| 17393683 - OGG: IR REPORTS NEGATIVE DAILY/HOURLY STATS & EVENTUAL TOTAL STATS MISTMATCH | |
| 17394950 - OGG: IR ABENDS DUE TO ORA-00600: [KNALSPXN:1]/ORA-00600[KNALFDEQUEUETXNLCRS: LCR | |
| 17441661 - OGG: IR REPEATEDLY ABENDS DUE TO ORA-26808/ORA-07445 [KNASPLCR()+248] | |
| 17545847 - IE V2 ORA-7445 [KNLUCOMPARENUMBERARRAYKNLPAR()+103 KNLU.C:12041] CAPTURE ABORTED | |
| 17546973 - XSTREAM DML HANDLER DOES NOT HONOR REPERROR HANDLERS | |
| 17622427 - XSTREAM OUTBOUND SERVER CORE DUMPED WHEN TESTING AGAINST OGG 12.1 USING IE V1 |
Oracle Virtual Operating System Services
| 17313525 - ORION WRITE HAS CORE DUMP ON X4-2 SOLARIS RACK | |
| 18180390 - AFTER APPLYING DBPSU 11.2.0.4.1 DB PROCESSES GET WARNING: ODM_MKDIR NOT FOUND |
Server Manageability
| 14852021 - SPAWRIO COMPUTES INCORRECT %READS AND %OPT | |
| 17721717 - Fix for bug 17721717 |
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 18031668 - 11.2.0.4.2 Patch Set Update Release 11.2.0.4.2 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.