Skip Headers

Oracle® Database

Patch 14275621 - 11.2.0.2.8 Patch Set Update

 

Released: October 16, 2012

This document is accurate at the time of release. For any changes and additional information regarding PSU 11.2.0.2.8, see these related documents that are available at My Oracle Support (http://support.oracle.com/):

This document includes the following sections:

1 Patch Information

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.2.8 includes the fixes listed in Section 7, "Bugs Fixed by This Patch".

To install the PSU 11.2.0.2.8 patch, the Oracle home must have the 11.2.0.2.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 11.2.0.2.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:

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.2.8


Client-Only Installations

PSU 11.2.0.2.8 to address CVE-2012-3137 and CVE-2012-3151.

Prior to installing this PSU you MUST read My Oracle Support Document: 1493990.1 - Patching for CVE-2012-3137.

Instant Client Installations

PSU 11.2.0.2.8 to address CVE-2012-3137 for certain configurations.

Prior to installing this PSU you MUST read My Oracle Support Document: 1493990.1 - Patching for CVE-2012-3137.

(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.)


2 Prerequisites

This section includes the following section:

2.1 OPatch Utility

You must use the OPatch utility version 11.2.0.3.0 or later to apply this patch. Oracle recommends that you use the latest released OPatch 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.

3.1 Patch Pre-Installation Instructions

Before you install PSU 11.2.0.2.8, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.

3.1.1 Environments with Grid Infrastructure

If you are installing the PSU to an environment that has a Grid Infrastructure home, note the following:

  • Grid Infrastructure PSU 11.2.0.2.8 Patch 14192201 should be applied to the Grid Infrastructure home and Database home using the readme instructions provided with the patch.

3.1.2 Environment Checks

  1. 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
    

3.1.3 One-off Patch Conflict Detection and Resolution

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:

  1. Determine whether any currently installed one-off patches conflict with the PSU patch as follows:

    unzip p14275621_11202_<platform>.zip
    cd 14275621
    opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./
    
  2. The report will indicate the patches that conflict with PSU 14275621 and the patches for which PSU 14275621 is a superset.

    Note that Oracle proactively provides PSU 11.2.0.2.8 one-off patches for common conflicts.

  3. 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.

  4. When all the one-off patches that you have requested are available at My Oracle Support, proceed with Section 3.2, "Patch Installation Instructions".

3.2 Patch Installation Instructions

Follow these steps:

  1. 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.

  2. If this is a RAC environment, install the PSU patch using the OPatch rolling (no downtime) installation method as the PSU patch is rolling RAC installable. Refer to My Oracle Support Document 244241.1 Rolling Patch - OPatch Support for RAC.

    • If 11.2.0.2.0 or 11.2.0.2.1 is currently installed, then refer to Document 1318986.1 ORA-600 or Data Corruption possible during shutdown normal/transactional/immediate of RAC instances in a rolling fashion for a one-time special shutdown instructions.

  3. 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.

  4. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:

    unzip p14275621_11202_<platform>.zip
    cd 14275621
    opatch apply
    
  5. If there are errors, refer to Section 5, "Known Issues".

3.3 Patch Post-Installation Instructions

After installing the patch, perform the following actions:

  1. Apply conflict resolution patches as explained in Section 3.3.1.

  2. Load modified SQL files into the database, as explained in Section 3.3.2.

  3. Upgrade Oracle Recovery Manager catalog, as explained in Section 3.3.3.

3.3.1 Applying Conflict Resolution Patches

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".

3.3.2 Loading Modified SQL Files into the Database

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 PSU.

    For information about the catbundle.sql script, see My Oracle Support Document 605795.1 Introduction to Oracle Database catbundle.sql.

  2. 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".

3.3.3 Upgrade Oracle Recovery Manager Catalog

If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it:

$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;

3.4 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of PSU 11.2.0.2.8 in the Oracle Home

There are no actions required for databases that have been upgraded or created after installation of PSU 11.2.0.2.8.

4 Deinstallation

These instructions apply if you need to deinstall the patch.

4.1 Patch Deinstallation Instructions for a Non-RAC Environment

Follow these steps:

  1. 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.

  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.

  3. Run the OPatch utility specifying the rollback argument as follows.

    opatch rollback -id 14275621
    
  4. If there are errors, refer to Section 5, "Known Issues".

4.2 Patch Post-Deinstallation Instructions for a Non-RAC Environment

Follow these steps:

  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_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".

4.3 Patch Deinstallation Instructions for a RAC Environment

Follow these steps for each node in the cluster, one node at a time:

  1. Shut down the instance on the node.

  2. Run the OPatch utility specifying the rollback argument as follows.

    opatch rollback -id 14275621
    

    If there are errors, refer to Section 5, "Known Issues".

  3. Start the instance on the node as follows:

    srvctl start instance
    

4.4 Patch Post-Deinstallation Instructions for a RAC Environment

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.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.

5 Known Issues

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 1477881.1 Oracle Database Patch Set Update 11.2.0.2.8 Known Issues.

Other known issues are as follows.

Issue 1   

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

6 References

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 468959.1 Enterprise Manager Grid Control Known Issues

Document 14275621.8 Database 11.2.0.2.8 Patch Set Update (PSU)

Document 1340011.1 11.2.0.2 Patch Set Updates - List of Fixes in each PSU

7 Bugs Fixed by This Patch

This patch includes the following bug fixes.

7.1 CPU Molecules

CPU molecules in PSU 11.2.0.2.8:

PSU 11.2.0.2.8 contains all molecules previously released in PSU 11.2.0.2.7 and the following new PSU 11.2.0.2.8 molecules:

14461356 - DB-11.2.0.2-MOLECULE-036-CPUOCT2012

14461357 - DB-11.2.0.2-MOLECULE-037-CPUOCT2012

14461358 - DB-11.2.0.2-MOLECULE-038-CPUOCT2012

14683459 - DB-11.2.0.2-MOLECULE-039-CPUOCT2012

7.2 Bug Fixes

See My Oracle Support Document 1340011.1 that documents all the non-security bugs fixed in each 11.2.0.2 Patch Set Update (PSU).

PSU 11.2.0.2.8 contains all fixes previously released in PSU 11.2.0.2.7 and the following new fixes:

Advanced Queuing

12899768 - PROCESSED MESSAGES REMAIN IN QUEUE CAUSING SPACE ISSUES

Automatic Storage Management

14467061 - FAILED INSTANCE RECOVERY MAY CAUSE ASM METADATA CORRUPTION/ORA-600[KFCRCVREAD10]

Buffer Cache Management

10207551 - RAC INSTANCE CRASH WITH ORA-600 [KCLEXPANDLOCK_1], [183621] ERROR BY LMS0

Generic

9373370 - DATA BASE RETURNS WRONG CURSORID WHEN THERE IS AN ORA-01013

9877980 - USING INDICATOR VARIABLES/RMAN WITH CURSOR SHARING EXACT/SMLR CAN CAUSE SIGSEGV

9952554 - UNDETECTED DEADLOCK 'LIBRARY CACHE LOCK'/'ROW CACHE LOCK'

10021111 - IN MTS ENV,SESSION USING MIGRATABLE TXN AND REMOTE OPERATION CAN RAISR INT. ERR

10140809 - EXPORT ON-COMMIT MVS FROM 10.2.0.4 AND IMPORT INTO 11.2 WE MAY HIT INTERNAL ERR

10171273 - EXPLAIN PLAN TAKES LONG WITH NON-EQUI SUBPARTITIONING UNDER INTERVAL PARTITIONIN

10210507 - ORA-2019 AFTER ALTER SYSTEM FLUSH SHARED_POOL

10213073 - INVALIDATION OF OBJECT WHEN OBJECT IS CREATED WITH SAME NAME AS PUBLIC SYNONYM

10228393 - ORA-07445: EXCEPTION ENCOUNTERED: CORE DUMP [QSMQSETUPREMOTEOBJECTS()+237]

11063821 - SQL%BULK_EXCEPTIONS GIVES WRONG RESULTS WITH PARTITIONED TABLE ORA-1

11734067 - QUERY WITH DECODE AND DISTINCT FUNCTIONS RETURNS DIFFERENT RESULTS

11878443 - CONVERSIONS OF AN INVALID NUMBER TO A STRING MAY RESULT IN SIGSEGV

12326708 - WRONG RESULTS (WRONG TRANSACTION) WITH MATERIALIZED TABLE FUNCTION

12374212 - WITH CURSOR_SHARING SET TO FORCE WE MIGHT HIT A SIGSEGV

12409916 - EXADA-RAC: M001 PROCESS HIT ORA-07445: [KGLIC0()+1137]

12649442 - RE-USING AGED OUT CURSOR WITH UNSAFE/NON-DATA LITERAL BINDS MIGHT CAUSE SIGSEGV

12764337 - XSTRM : ORA-7445 [KGLDTIN()+150] DURING IMPORT/VIEW CREATION DDL

13080778 - ORA-00942 RETURNED IN SQL ON MULTIPLE SCHEMAS DATABASE

13250244 - ORA-4031 ERRORS SEEN WHEN PARAMETER _KGHDSIDX_COUNT IS SET TO >1 DUE TO MEM LEAK

14613900 - POSSIBLE CORE DUMP WHILE SCANNING FOR A CHILD FOR SHARABLE CURSOR

14624146 - PMON MAY CRASH WHILE CLEANING UP TEMP TABLE STATE SCN INFORMATION

High Availability

7312717 - ORA-600 [KRCCAUB_2] WITH NO APPARENT REASON

10114837 - RMAN DELETES THE UNAPPLIED ARCHIVED REDO LOGS

10172453 - DUPLICATE FOR STANDBY FAILS ORA-19625 DURING RESTORE OF LEVEL 1 BACKUP PIECE

11686968 - INSTANCE CRASHED WITH ORA-600 [KRCCAUB_3] ERROR

11883472 - DBMV2: REDO APPLY RATE DEGRADATION CAUSED BY LOG READ IN 11.2.0.2

12794305 - REDO SHIPMENT COULD FAIL AT THE STANDBY WITH ORA-600:[KRSR_PIC_COMPLETE.8]

12834027 - ORA-600 [KJBMPRLST:SHADOW] & [KJBRASR:PKEY] IN A READ MOSTLY & SKIP LOCK ENV

12894807 - SELECT FOR UPDATE WITH DBLINK RECEIVES ORA-16000 ON STANDBY OF ACTIVE DATA GUARD

13737746 - MRP0: BACKGROUND MEDIA RECOVERY TERMINATED

Oracle Security

9956835 - INTERNAL ERROR RAISED WHEN RETRIEVING USERENV USING SYS_CONTEXT IN PL/SQL

10373013 - SHARED SERVER GENERATE HUGE TRACE FILE FOR CURSOR REPARSE DIAGNOSIS

Oracle Space Management

9470768 - USING DATAPUMP TO IMPORT A TABLE HAVING CACHE/NOCHACHE LOB MIGHT CAUSE SIGSEGV

13326736 - ORA-959 RENAMING A TABLESPACE TO ALREADY DROPPED TABLESPACE NAME

Oracle Streams

11775474 - DBMS_REDEFINITION DOES NOT PRODUCE DEFERRED SEGMENTS SINCE 11.2.0.2

12713993 - APPLY PARALLEL PROCESSING IMPACTED BY CONSTRAINTS (Included in PSU 11.2.0.2.8 instead of PSU 11.2.0.2.7)

14473913 - SOURCE 11.2.0.2 TO TARGET 11.2.0.3, ISSUE OF TTC PROTOCOL ERR WHEN USING DTYSTZ

PL/SQL

9478199 - EXECUTION OF ANONYMOUS BLOCKS, SOMETIMES LEAD TO MEMORY CORRUPTION, CRASHES.

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.

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 14275621 - 11.2.0.2.8 Patch Set Update Release 11.2.0.2.8 for UNIX

Copyright © 2006, 2012, 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.