Skip Headers

Oracle® Database

Patch 9654987 - 11.1.0.7.4 Patch Set Update

 

Released: July 13, 2010

This document is accurate at the time of release. For any changes and additional information regarding PSU 11.1.0.7.4, 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.1.0.7.4 includes all fixes previously included in PSU 11.1.0.7.2 and those listed in Section 5, "Bugs Fixed by This Patch".

To install the PSU 11.1.0.7.4 patch, the Oracle home must have the 11.1.0.7.0 Database patch set installed.

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


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 Database Concepts.)

ASM (Automatic Storage Management) homes

PSU 11.1.0.7.1

CRS (Cluster Ready Services) homes

None


2 Patch Installation and Deinstallation

This section includes the following sections:

2.1 Platforms for PSU 11.1.0.7.4

For a list of platforms that are supported in this Patch Set Update, see My Oracle Support Note 1060989.1 Critical Patch Update July 2010 Patch Availability Document for Oracle Products.

2.2 OPatch Utility Information

You must use the OPatch utility version 11.1.0.6.7 or later to apply this patch. Oracle recommends that you use the latest released OPatch 11.1, which is available for download from My Oracle Support patch 6880880 by selecting the 11.1.0.0.0 release.

For information about OPatch documentation, including any known issues, see My Oracle Support Note 293369.1 OPatch documentation list.

2.3 Patch Installation

These instructions are for both non-RAC environments and RAC environments.

2.3.1 Patch Pre-Installation Instructions

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

2.3.1.1 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
    
2.3.1.2 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 Note 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 Note 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 p9654987_11107_<platform>.zip
    opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./9654987
    
  2. The report will indicate the patches that conflict with PSU 9654987 and the patches for which PSU 9654987 is a superset. Refer to "Patch Set Updates Patch Conflict Resolution" in My Oracle Support Note 854428.1 Patch Set Updates for Oracle Products.

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

  3. Use My Oracle Support Note 1061295.1 Patch Set Updates - One-off 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 11.1.0.7.2 one-off patches that you have requested are available at My Oracle Support, proceed with Section 2.3.2, "Patch Installation Instructions".

2.3.2 Patch Installation Instructions

Follow these steps:

  1. If you are using a Data Guard Physical Standby database, you must first install this patch on the primary database before installing the patch on the physical standby database. It is not supported to install this patch on the physical standby database before installing the patch on the primary database. For more information, see My Oracle Support Note 278641.1.

  2. If you are patching an ASM instance, shut down all Oracle Database instances that use this ASM instance. (To see which Oracle Database instances are connected to this ASM instance, query the V$ASM_CLIENT view.)

  3. Do one of the following, depending on whether this is a RAC environment:

    • If this is a RAC environment, choose one of the patch installation methods provided by OPatch (rolling, all node, or minimum downtime), and shutdown instances and listeners as appropriate for the installation method selected.

      This PSU patch is rolling RAC installable. Refer to My Oracle Support Note 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.

  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 p9654987_11107_<platform>.zip
    cd 9654987
    opatch apply
    
  5. If there are errors, refer to Section 3, "Known Issues".

2.3.3 Post Installation Instructions

Do not perform the operations in this section on ASM instances. However, if you shut down ASM as part of applying the PSU, you must start ASM instances before you can perform any of the actions in this section on any database instances.

After installing the patch, perform the following actions:

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

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

  3. Recompile views in the database, if necessary, as explained in Section 2.3.3.3.

2.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 2.3.1.2, "One-off Patch Conflict Detection and Resolution".

2.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 Note 605795.1 Introduction to Oracle Database catbundle.sql.

  2. Check the following log files in $ORACLE_HOME/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 3, "Known Issues".

2.3.3.3 Recompiling Views in the Database

Recompiling views in the database is a one-time action that is required to complete the installation of CPU fixes that were initially released in January, 2008. It requires that the database be in upgrade mode, so this step is not rolling RAC installable. You may defer this step to a later downtime. If you do this, your system will continue to work; however, the installation of the January 2008 CPU fixes will not be complete until the view recompilation is completed.

Skip this section if you have recompiled views for this database during the installation of a previous PSU or CPU.

The time required to recompile the views and related objects depends on the total number of objects and on your system configuration. In one internal Oracle test with approximately 2000 views and 4000 objects, the total execution time for view_recompile_jan2008cpu.sql and utlrp.sql was about 30 minutes.

If you want to check whether view recompilation has already been performed for the database, execute the following statement:

SELECT * FROM registry$history where ID = '6452863';

If the view recompilation has been performed, this statement returns one or more rows. If the view recompilation has not been performed, this statement returns no rows.

The following steps recompile the views in the database. For a RAC environment, perform these steps on only one node.

  1. Run the pre-check script (so named because it was initially released in CPUJan2008), which reports the maximum number of views and objects that may be recompiled:

    cd $ORACLE_HOME/cpu/view_recompile
    sqlplus /nolog
    SQL> CONNECT / AS SYSDBA
    SQL> @recompile_precheck_jan2008cpu.sql
    SQL> QUIT
    

    The purpose of this step is to help you determine whether view recompilation should be done at the same time as the PSU install, or scheduled later.

  2. If the database is not in a RAC environment, perform this step and skip the next step. (If the database is in a RAC environment, go to the next step.)

    Run the view recompilation script. Note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA.

    cd $ORACLE_HOME/cpu/view_recompile
    sqlplus /nolog
    SQL> CONNECT / AS SYSDBA
    SQL> SHUTDOWN IMMEDIATE
    SQL> STARTUP UPGRADE
    SQL> @view_recompile_jan2008cpu.sql
    SQL> SHUTDOWN;
    SQL> STARTUP;
    SQL> QUIT
    
  3. If the database is in a RAC environment, run the view recompilation script as follows. Note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA. Stop all instances except the one where the view recompilation is being executed.

    cd $ORACLE_HOME/cpu/view_recompile
    sqlplus /nolog
    SQL> CONNECT / AS SYSDBA
    SQL> STARTUP NOMOUNT
    SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
    SQL> SHUTDOWN
    SQL> STARTUP UPGRADE
    SQL> @view_recompile_jan2008cpu.sql
    SQL> SHUTDOWN;
    SQL> STARTUP NOMOUNT;
    
    Set the CLUSTER_DATABASE initialization parameter to TRUE:
    
    SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
    
    Restart the database:
    
    SQL> QUIT
    cd $CRS_HOME/bin
    srvctl start database -d <database-name>
    
  4. Check the log file for any errors. The log file is in the current directory and is named: vcomp_<sid>_<timestamp>.log

  5. If any invalid objects were reported, run the utlrp.sql script as follows:

    cd $ORACLE_HOME/rdbms/admin
    sqlplus /nolog
    SQL> CONNECT / AS SYSDBA
    SQL> @utlrp.sql
    

    Then, manually recompile any invalid objects. For example:

    SQL> alter package schemaname.packagename compile;
    
  6. The setting of RECYCLEBIN is changed during the preceding steps due to bug 9768907; therefore, see My Oracle Support Note 9768907.8 STARTUP UPGRADE turns off RECYCLEBIN with SPFILE for details and workaround instructions.

2.3.4 Post Installation Instructions for Databases Created or Upgraded after Installation of PSU 11.1.0.7.4 in the Oracle Home

These instructions are for a database that is created or upgraded after the installation of PSU 11.1.0.7.4.

You must execute the steps in Section 2.3.3.2, "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

Upgraded databases require that you perform the steps in Section 2.3.3.3, "Recompiling Views in the Database" if these steps have not previously been performed; otherwise, no post-installation steps need to be performed.

2.4 Patch Deinstallation

These instructions are for both Non-RAC environments and RAC environments.

2.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 2.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 9654987
    
  4. If there are errors, refer to Section 3, "Known Issues".

2.4.2 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_HOME/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 3, "Known Issues".

2.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. (Shut down all RDBMS instances before any ASM instances.)

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

    opatch rollback -id 9654987
    

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

  3. Start the instance on the node. Depending on the type of home, enter the following commands or command.

    • For ASM homes:

      srvctl start listener
      srvctl start asm
      srvctl start instance
      
    • For RDBMS (non-ASM) homes:

      srvctl start instance
      

2.4.4 Post Deinstallation Instructions for a RAC Environment

Follow the instructions listed in Section Section 2.4.2, "Post Deinstallation Instructions for a Non-RAC Environment" only on the node for which the steps in Section 2.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.

3 Known Issues

For information about OPatch issues, see My Oracle Support Note 293369.1 OPatch documentation list.

For issues documented after the release of this PSU, see My Oracle Support Note 1089073.1 Oracle Database Patch Set Update 11.1.0.7.4 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
Issue 2   

The view recompilation pre-check script returns different results during subsequent runs (such as after the first time you ran it).

The results (the maximum number of views and objects that may be recompiled) may be more or less than reported in the previous running of the script. This is expected behavior, and is not a problem.

Issue 3   

If the view recompilation script has already been run, a message is displayed indicating that the script has already been applied.

This is not a problem, because as the instructions note, you do not need to run the script if it has already been run.

Issue 4   

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

The inventory list of patches for PSU 11.1.0.7.2 does not include fix 9250812, although the code for this fix is, in fact, included in the PSU. This situation can result in the following issues that do not require any action on your part:

  • If you install PSU 11.1.0.7.2 on top of PSU 11.1.0.7.1 and patch 9250812, OPatch will detect a conflict with patch 9250812. This conflict can be ignored, and you can proceed with the installation of PSU 11.1.0.7.2.

  • After PSU 11.1.0.7.2 is installed, fix for patch 9250812 will not be listed in the OPatch bug inventory, but the fix is included in the PSU.

4 References

The following documents are references for this patch.

Note 293369.1 OPatch documentation list

Note 360870.1 Impact of Java Security Vulnerabilities on Oracle Products

Note 468959.1 Enterprise Manager Grid Control Known Issues

Note 9209238.8 Bug 9209238 - 11.1.0.7.2 Patch Set Update (PSU)

5 Bugs Fixed by This Patch

This patch includes the following bug fixes.

5.1 CPU Molecules

CPU molecules in PSU 11.1.0.7.4:

PSU 11.1.0.7.4 contains all molecules previously released in PSU 11.1.0.7.3 and the following new PSU 11.1.0.7.4 molecules:

9702142 - DB-11.1.0.7-MOLECULE-028-CPUJUL2010

9702143 - DB-11.1.0.7-MOLECULE-029-CPUJUL2010

5.2 Bug Fixes

PSU 11.1.0.7.4 contains all fixes previously released in PSU 11.1.0.7.3 and the following new fixes:

Advanced Queuing

7207654 - ORA-600 [KWQBMCRCPTS101] AFTER DROP PROPAGATION WITH SPILLED MSGS

Automatic Storage Management

6434104 - XF11.1FGA - TRC - KFDSKALLOC

7828187 - ASMCMD CP FAILS WITH FILES BIGGER THAN 2GB

8476517 - ORA-600 [KFDRESYNCMAINSL:01] DURING ONLINE DISKS IN FAILGROUP

8755082 - ORA-00600: [KCFIS_TRANSLATE4:VOLUME LOOKUP], [2], [WRONG DEVICE NAME], [], [], [

9074535 - DATABASE IS HANGING IN STRETCH CLUSTER USING ASM STORAGE

9363145 - STBH: DB INSTANCES TERMINATED BY ASMB DUE TO ORA-00600 [KFDSKALLOC0]

9368549 - STRESS-BIGBH-DB: ORA-15195: INTERNAL ASM TESTING EVENT 15195 DURING REBALANCE

Buffer Cache

7202451 - MMAN TERMINATING INSTANCE DUE TO ORA-600 [KCBWRSZ_NOTSET] ERROR

8296070 - ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [KCBW_GET_BH_1], [0], [17680], [1034]

Data Guard Logical

7138523 - REGISTER LOGICAL LOGFILE DOES NOT CLEAR SRL INFO

Data Guard Physical

8481935 - RFS TRACE FILE GENERATES THE SAME TRACE INFORMATION EVERY COUPLE MINUTES

Data Guard Redo Transport

7417614 - APPLIED COLUMN IN V$ARCHIVED_LOG CAN ERRONEOUSLY INDICATE A LOG WAS NOT APPLIED

9399090 - STBH: CONSTANT/HIGH FREQUENT LOG SWITCHES ON BEEHIVE DATABASE IN THE LAST 3 DAYS

Flashback Database

8834425 - ORA-240 IN RVWR PROCESS CAUSING 5MIN TRANSACTIONAL HANG

9311954 - STRESS-BIGBH-DB:ORA-56710: DBRM PROCESS DIED UNEXPECTEDLY

Real Application Cluster

7835247 - TRACING IN KSWSSCS() CAN CAUSE A SIGSEGV

8399549 - TB:SH:WRONG MEMBER KILL WHEN LMD WAIT LONG TIME TO RECEIVE ALL FTDONES

8577450 - AROLTP-D: LMS1 HIT ORA-00600 [KJBLPWR:ID]

9229631 - STBH: LMS0 TERMINATING THE INSTANCE DUE TO ORA-00600 KCLEXPANDLOCK_1

9241202 - STRESS-BIGBH:ORA-600[KJBMSPING:FT], [], [], [], [], [], [], [], [], [], [], []

9246245 - STBH: MULTIPLE INSTANCES CRASHED WITH ORA-15064

9311909 - STRESS-BIGBH-DB:LMS ENCOUNTER ORA-7445 KJMSM &ORA-00484 TERMINATED INSTANCE

9776431 - TIMEOUT TO WAIT FOR LGWR TO WRITE IS UNEXPECTELY 1 SECONDS ON 11.1.0.7.3PSU

Row Access Method

7484102 - CORE DUMP [ACCESS_VIOLATION] [UNABLE_TO_TRANS_PC]

7662491 - INSTANCE CRASH / ORA-600 [KDDUMMY_BLKCHK] HIT DURING RECOVERY

Streams

8595043 - STREAMS CAPTURE ABORTS WITH ORA-26744 / ORA-26766

8650719 - DOWNSTREAM CAPTURE ABORTS WITH ORA-26766

Compression

9011088 - [11GR2]ADDING COLUMN TO COMPRESSED TABLE, DATA LOSS OCCURED.

9231605 - APPSST GSI 11G : BLOCK CORRUPTION ON A COMPRESSED TABLE.

9637033 - ORA-07445[KDR9IR2RST0] INSERT AS SELECT IN A COMPRESSED TABLE WITH > 255 COLUMNS

9275072 - APPSST GSI 11G : BUFFER BUSY WAITS INSERTING INTO TABLES

9341448 - APPSST GSI 11G : BUFFER BUSY WAITS AND LATCH: CACHE BUFFERS WAITS WHEN INSERTING

Secure Files

7171015 - ORA-3106 FROM OCILOBREAD WITH COMPRESSED SECUREFILE CLOBS

7185113 - GETTING ORA-600 [3:KDLW_PROCESS_REAP_WRITE], WRITING A TEMP LOB

7332001 - USING "STORE AS SECUREFILE TABLE_A_LOB_X" CLAUSE PRODUCES DIFFERENT RESULTS

7417140 - ORA-600 [KDLIREORGPE:1] IN FRAGMENTED SECUREFILE OVERWRITES

7461921 - ORA-600[KDLW:UGA STATE INCONSITENT] SIGNALLED

7508788 - METADATA ONLY COPY OF DEDUPED LOB INCORRECT IF SRCLEN SMALLER THAN DSTLEN

8263441 - SIGSEGV ON SECUREFILES WITH DIFFERENT BLOCK SIZES

8268330 - AROLTP-C: PMON CRASHED WITH ORA-07445 [KDLISODEL()+2181]

8517426 - SECURE FILES DO NOT CORRECTLY REUSE UNUSED BLOCKS

8603465 - AGGRESSIVE ALLOCATION OF SPACE IN SECUREFILES

8669679 - ET11.2LOB: DATA DISPARITY BETWEEN BASICFILE AND DEDUP SECUREFILE LOBS

8775066 - [11GR2-LNX-090731] SEVERAL ORA-600 ERRORS OCCURS IN SECUREFILES

9272086 - STBH: DATA PUMP WRITER SEEMS TO BE WAITING ON WAIT FOR UNREAD MESSAGE ON BROADCA

DB Recovery

7643632 - HIGH LOG FILE SYNC IN DATAGUARD MAXIMUM AVAILABILITY (SYNC) MODE

9145541 - ORA-600 [25027] / ORA-600 [4097] FOR ACTIVE TX IN A PLUGGED TABLESPACE

Space Management

8565359 - DBFS STRESS TEST FAILED WITH ORA-600 [KTSLGHB-1]

8737065 - 11.2.0.1: AIX : ORA- 600 [KCBRLS_1]

9166322 - SAME BLK RETURNED PERFORMANCE ISSUE (HIGH LOGICAL IOS AND BLOCK CHANGES)

9242411 - STRESS-BIGBH: LOTS OF OR-3113S IN BIGBH STRESS TEST

SQL Execution

7022234 - XF11.2CLOAD - TRC - MSQSUB

7307821 - QUERY RETURNS ORA-1791 WHEN NLS_SORT=BINARY_CI

7326645 - INDEX REBUILD GOT ORA-903

Parallel Execution

8315482 - PGA MEMORY CONSUMPTION INCREASING IN RACGIMON PROCESS

Partitioning

9165206 - ORA-600 [KKPOLLS1] / [KKDOILSF1] - DURING PARTITION MAINTANANCE

Shared Cursors

7648406 - CHILD CURSOR IS NOT SHARED IF SET NLS_LENGTH_SEMANTICS=CHAR.

8865718 - RECURSIVE CURSORS CONTAINING "AS OF SNAPSHOT" CLAUSE ARE NOT SHARED

8981059 - HIGH VERSION COUNT:BIND_MISMATCH,USER_BIND_PEEK_MISMATCH,OPTIMIZER_MODE_MISMATCH

Library Cache

6856345 - ORA-07445: EXCEPTION ENCOUNTERED: CORE DUMP [KGLDMP()+2595] [SIGSEGV]

Semantic Analysis

7172752 - ORA-00600 [QCSGPVC3]

PLSQL

7707103 - RECOMPILATION OF LIBRARY UNIT GIVES END-OF-FILE COMMUNICATION CHANNEL

7710260 - DBMS_UTILITY.COMPILE_SCHEMA DOESN'T USE SESSION SETTING OF PLSQL_DEBUG

9210925 - AFTER MANUAL UPGRADE TO 11.1.0.7 PL/SQL CALLS INCORRECT FUNCTION

DML Driver

7614692 - BULK FEATURE WITH 'SAVE EXCEPTIONS' DOES NOT WORK IN ORACLE 11G

9255542 - ARRAY INSERT TO PARTITIONED TABLE LOOSES ROWS DUE TO CONCURRENT DDL (ORA-14403)

9488887 - FORIEGN KEY VIOLATION WITH ARRAY-INSERT AND ONLINE IDX REBUILD AFTER BUG-9255542

Automatic Memory Management

7345543 - BATCH PROCESS WAITING IMMEDIATE MODE REQUESTS FOR SAME COMPONENT

Local and Distributed Transaction Mangement

7697360 - ORA-600[K2VCBK_6] SIGNALLED WITH XA WORKLOAD

8268775 - PERF: HIGH US ENQUEUE CONTENTION DURING A LOGIN STORM OR SESSION FAILOVER

8354686 - ORA-600 [KSS_GET_TYPE: NULL SO] IN PRIMARY DATABASE

Virtual Operating System

7278231 - APPSST 11G IMG: NO SPFILE READ/WRITE ERRORS REPORTED IN THE ALERT LOG

Message

9713537 - ENHANCE CAUSE/ACTION FIELDS OF THE INTERNAL ERROR ORA-00600

9714832 - ENHANCE CAUSE/ACTION FIELDS OF THE INTERNAL ERROR ORA-07445

6 Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

TTY Access to Oracle Support Services

To reach AT&T Customer Assistants, dial 711 or 1.800.855.2880. An AT&T Customer Assistant will relay information between the customer and Oracle Support Services at 1.800.223.1711. Complete instructions for using the AT&T relay services are available at http://www.consumer.att.com/relay/tty/standard2.html. After the AT&T Customer Assistant contacts Oracle Support Services, an Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process.


Patch 9209238 - 11.1.0.7.2 Patch Set Update Release 11.1.0.7.3 for UNIX

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