Skip Headers
 
 

Oracle® Database Server Version 11.2.0.2 Patch 8

Bundle Patch Update Note

Release 11.2.0.2 for Microsoft Windows (32-Bit)

 

Released: Jul, 2011

This document includes the following sections:

1 Getting Started

You should administer one Oracle product, one Oracle home at a time, for its particular Bundle Patch Update. Each Oracle home will have its own requirements.

After you have read the Bundle documentation and collected your product information, you need to prioritize all of the systems you need to update. Plan to update systems that have the highest risk first. For example, start with systems that are external to a firewall before updating systems within an internal network.

1.1 System Requirements

The following are the system requirements for this bundle patch:

2 Patch Information

Bundle patches are cumulative, which means fixes from previous Oracle security alerts and Bundle patch updates are included. It is not required to have previous security patches applied before applying the Bundle patches. However, you must be on the stated patch set level for a given product home before applying the Bundle patches for that release.

If assistance is required from Oracle Global Product Support, then provide complete information for the products being patched. Because you are administering one Oracle product, one Oracle home at a time for its one Bundle patch, there is generally one Support Service Request per Oracle home.

Table 1 describes installation types and CPU applicability. For each installation type, it indicates the most recent CPU 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 CPU is listed, then apply that CPU or any later CPU patch to be current with security fixes.

Table 1 Installation Types and CPU Applicability

Installation Type Latest CPU with Security Fixes

Server homes

CPUJUL2011


Client-Only Installations

CPUJUL2011

Instant Client Installations

CPUJUL2011

(The Instant Client installation is not the same as the client-only Installation. For additional information about Instant Client installations, see Oracle Database Concepts.)

2.1 Bugs Fixed by This Patch

This patch fixes the following bugs.

2.1.1 Bugs Fixed for DB 11.2.0.2 Patch 8: 12714462

DB 11.2.0.2 Patch 8 includes all bugs fixed in 11.2.0.2 Patch1 to 11.2.0.2 Patch7. It must be applied on top of the 11.2.0.2 base release or on top of any earlier bundle patches 11.2.0.2 Patch 1 through Patch7.

For a more descriptive list of the bug fixes included in this bundle patch, refer to My Oracle Support Note 1114533.1.

9572787 - LONG WAITS FOR ENQ AM CONTENTION FOLLOWING CELL CRASH CAUSED CLUSTERWIDE OUTAGE

12431716 - UNEXPECTED CHANGE IN MUTEX WAIT BEHAVIOUR IN 11.2.0.2.2 PSU (HIGHER CPU POSSIBLE

10278372 - TB X CONSISTENTLY PRINT WARNING ELAPSED TIME DID NOT ADVANCE IN ASM ALERT LOG

1170769 - INVALID APPLSYS.ENV CONFGURATION WHEN USING ARBUS ( D1159450.DRV )

11695285 - ORA-15081 I/O WRITE ERROR OCCURED AFTER CELL NODE FAILURE TEST

9078442 - ORA-19762 FROM ASMCMD CP COPYING FILE WITH DIFFERENT BYTE ORDER FROM FILESYSTEM

10157249 - CATALOG UPGRADE TO 11.2.0.2 FAILS WITH ORA-1

9897335 - TB-ASM UNNECCESSARY OCR OPERATION LOG MESSAGES IN ASM ALERT LOG WITH ASM OCR

9936659 - LNX64-11202-CRS ORACLE HOME PUT ON ACFS, DB INST FAILS TO RESTART AFTER CRASH

12544032 - QUERY RETURNS WITH ERROR - ORA-03113 END-OF-FILE ON COMMUNICATION CHANNEL

10160615 - SQL METHOD 4 ORA-1461 ERROR WHEN WRITING MORE THAN 4000 BYTES TO CLOB COLUMN

10015652 - PSRPERF CONNECT BY NO FILTERING WITH START-WITH LEADS TO BAD PLAN

11740670 - SUBQUERY FACTORING PREVENTS COST-BASED TRANSFORMATION EVEN IF VIEW IS REFED ONCE

11883804 - RC11 HIGH HARD PARSING OBSERVED WITH AQ JMS SQL STATEMENTS

12332340 - INCORRECT INDONESIAN LOCALE DEFINITION (MONTH/DAY NAMES)

10165223 - ORA-29553 CLASS IN USE SYS.JAVAX/MAIL/FOLDER

9589791 - GET PEER CREDENTIALS FAILS IN MCS-BASED SSL

12579349 - PSRPERF ORA-600 KTCN_POLICY_DEFN_CHG_UNKNOWN_OBJ DURING ADD/DROP POLICY FUSION

8532430 - ASMCMD SPCOPY CAN COPY DB SPFILE AS ASM SPFILE

10621549 - ASM ORA-01265 UNABLE TO DELETE CHANGE TRACKING FILE

9073910 - SQL*LOADER DOESN'T CREATE ABSTRACT LOBS OF THE CORRECT TYPE IN KLA.C

10371288 - TB_X64 HIT ORA-00600 [KTSPGSB-INC]

12345717 - MERGE FAILS WITH ORA-600 [13013]

11074393 - REGRESSION TRACKING BUG FOR 8752691

9916260 - WRONG RESULTS LED BY NOT IS NOT NULL FILTER AND INLINE VIEW

11797217 - WRONG RESULTS WITH FUNCTION INDEX

11683713 - INVALID NAMESPACE ERROR WHEN UPDATE NAMESPACE ATTRIBUTES

9913542 - ORA-00001 UNIQUE CONSTRAINT (SYS.I_TABPART_BOPART$) VIOLATED

10365159 - QUERY RETURNS WRONG RESULTS WITH FILTER PUSH AND PREDICATE TRANSITIVITY

10620808 - FULL TABLE SCAN FOR SELECT .. FOR UPDATE CAUSES POOR PERFORMANCE ON 11G.

11801609 - ORA-00600 [KNLLCV2ANY809] WHEN PRINT LCR WITH XMLTYPE FROM APPLY ERROR QUEUE

9285259 - MERGE IGNORES CHECK CONSTRAINT

12591120 - WRONG TABLE SELECTIVITY WITH INLISTS, OUT OF BOUND VALS AND EXTENDED STATISTICS

11733205 - INVALID ORA-31095 RECOMPILING INVALID SCHEMAS DUE TO INCLUDE / IMPORT CYCLE

11727498 - SECOND WALLET CREATED AFTER DELETE ORIGINAL DOES NOT HAVE TS MASTER KEY

10625485 - ORA-600 [KSS_GET_TYPE BAD CONTROL] FROM CUSTOM PACKAGE USING DBMS_PIPE

10239480 - TB X REBOOT 1 CELL NODE AND KILL ASM LMS, DB INSTS ABORT DUE TO ORA-15081.

11814891 - ORA-600 [7999] [9] [1] [ LOB BLOCK RDBA ] DOUBLE ALLOCATED LOB BLOCK

10284570 - CRASH RECOVERY FAILS DUE TO ORA-15081, DISK GROUP IS MOUNTED BUT WAS RESYNC-ING

11788856 - INSERT HANG 11.2.0.1 SPINNING ON QKSHTSTMTINF0

11927239 - ORA-00001 UNIQUE CONSTRAINT (PERFSTAT.STATS$FILE_HISTOGRAM_PK) VIOLATED

10149919 - APPSST GSI 11G HIGH LATCH FREE WAITS 'ACTIVE SERVICE LIST' WITH HIGH LOAD AVG

10420891 - W00 PROCESS GETS TRACE FILES WITH

9943960 - TTX ID1 %X ID2 %X RET %D WAITOPT %D MESSAGE IN TRACE FILE

12340808 - NEED INTERNAL METHODS TO RENAME ASM SYSTEM ALIASES

11876260 - FULLY QUALIFIED INDEX NOT USED - REGRESSION FROM 11.2.0.1

12400751 - UPDATE STATEMENTS DOES NOT WORK.

11939823 - SDO_CONTAINS(LINE1, LINE2) COULD RETURN WRONG RESULTS

9859425 - ORA-7445 [SDBGRFUIO_IS_OWNER]

10114391 - UPDATE OF AN OBJECT ATTRIBUTE IN PRESENCE OF A TRIGGER FAILS

9823660 - ORA-603 ORA-604 ORA-1001 ORA-28003 WHEN PASSWORD_VERIFY_FUNCTION RETURNS FALSE

10235640 - ORA 7445 EVAOPN3 ON QUERY WITH INLINE VIEW AND NVL FUNCTION

2.1.2 Bugs Specific NOTES:

1) bug 6904068

The fix for bug 6904068 is effective only if parameter _first_spare_parameter is set to a suitable value (such as 1). If this parameter is not set then the patch has no effect.

    _first_spare_parameter = 1

3 Patch Installation Procedures for Oracle Database Release 11.2.0.2 Patch8

This section includes the following sections:

3.1 Components patched by Oracle Database Release 11.2.0.2 Patch8

    Components patched by this Bundle Patch Update:

    • Oracle Database

    • PL/SQL

    • XDB - XML Database

    • Network

    • Context

    • Javavm

    • Winprod

    • Spatial

3.2 OPatch Utility Information

You must use the OPatch utility release 11.2.0.1.3 or later. You can download it from My Oracle Support with patch 6880880.

Prior to the patch installation, the following checks are performed

  • Conflicts with other patches

  • Conflicts with subset patches (existing patch is a subset of the patch being installed)

If a conflict is found, then stop the installation and contact Oracle Support Services.

If a subset is found, then continue the installation. All fixes for the subset patch are included in the patch being installed. The subset patches will be automatically rolled back prior to the installation of the new patch.

If the Oracle inventory is not setup correctly, this utility will fail. To check accessibility to the inventory you can use the opatch lsinventory command. The utility must be in the PATH definition, or you must call it specifying its full path. For example:

    %ORACLE_HOME%/OPatch/opatch lsinventory

3.3 Patch Installation Instructions for Oracle Database Release 11.2.0.2 Patch8

This section includes the following topics.

3.3.1 Preinstallation Instructions

Follow these steps:

  1. Ensure that your Oracle Database installation is the same release for which you are applying this patch. In other words, only apply the Release 11.2.0.2 Bundle patch to an Oracle Database Release 11.2.0.2.

  2. This patch must be applied on top of the 11.2.0.2 base release.

  3. Review Section 4, "Known Issues" before proceeding with this installation.

  4. Back up the current database that is installed, the %ORACLE_HOME% directory and Oracle inventory under c:\Program files\oracle directory.

    This will help if there are problems applying the patch, and to restore the Inventory in case of an issue with the patch.

  5. Perform a clean shutdown of all Oracle services (databases, Oracle listeners, Oracle agents, and so on.) that run from the Oracle Home where you install this patch.

  6. Stop all Oracle services, Recovery catalog, ODBC applications, and other applications that use Oracle Client. This may include Web servers that load the Oracle client in the mid-tier environment.

  7. Explicitly stop the Distributed Transaction Coordinator service (which is not an Oracle service) if it is running.

3.3.2 Patch Installation Instructions for Single Instance

Follow these steps:

  1. Cleanly shut down all processes running from the ORACLE_HOME.

  2. Set the ORACLE_HOME environment variable to the correct Oracle home that needs to be patched.

    > set ORACLE_HOME=<Oracle Home Path> 
    
  3. Go to the directory where you downloaded the patch:

    > cd 12714462
    
  4. Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:

    > opatch apply 
    
  5. Inspect the opatch<timestamp>.log file generated in %ORACLE_HOME%\cfgtoollogs\opatch for any errors.

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

3.3.3 Patch Installation Instructions for Oracle Instant Client

For OUI based Client-Admin installations, the 'opatch apply' takes care of updating your installation with these latest Instant Client binaries.

For Other types of Instant Client installations, Follow these steps:

  1. Backup and replace oraociei11.dll file in the Instant Client installation with oraociei11.dll from the 12714462\files\instantclient directory.

  2. Backup and replace oraociei11.sym file in the Instant Client installation with oraociei11.sym from the 12714462\files\instantclient directory.

  3. Backup and replace oraociicus11.dll file in the Instant Client installation with oraociicus11.dll from the 12714462\files\instantclient\light directory.

  4. Backup and replace oraociicus11.sym file in the Instant Client installation with oraociicus11.sym from the 12714462\files\instantclient\light directory.

  5. Backup and replace sqora32.dll, sqoras32.dll and sqresus.dll file in the Instant Client installation with sqora32.dll, sqoras32.dll and sqresus.dll from the 12714462\files\bin directory.

3.3.4 ODP.NET 2.x Installation Instructions

Follow these steps only if you are using ODP.NET:

  1. Open a command prompt. (Open via "Run As Administrator" if applying on Windows 7 or 2008R2 and User Account Control is enabled).

  2. Navigate to the %ORACLE_HOME%\ODP.NET\bin\2.x directory.

  3. Execute the following to install the new ODP.NET assembly:

     oraprovcfg.exe /action:gac /providerpath:Oracle.DataAccess.dll
    

3.3.5 ODP.NET 4.0 Installation Instructions

Follow these steps only if you are using ODP.NET:

  1. Open a command prompt. (Open via "Run As Administrator" if applying on Windows 7 or 2008R2 and User Account Control is enabled).

  2. Navigate to the %ORACLE_HOME%\ODP.NET\bin\4 directory.

  3. Execute the following to install the new ODP.NET assembly:

     oraprovcfg.exe /action:gac /providerpath:Oracle.DataAccess.dll
    

3.3.6 Post Installation Instructions

After installing the patch, perform the following actions:

  1. Load modified .sql files into the database, as explained in Section 3.3.6.1.

3.3.6.1 Loading Modified .sql Files into the Database

To load modified .sql files into the database, follow these steps:

  1. If Database Vault is installed, disable Database Vault before proceeding to the next step. See Section 3.5.1 for instructions to disable Database Vault.

  2. Start the OracleService<SID> and Oracle Listener Services if already not started.

  3. Start all database instances running out of the ORACLE_HOME that you just patched.

  4. For each database instance running out of the ORACLE_HOME being patched, connect to the database using SQL*Plus as SYSDBA and run catcpu.sql as follows:

    > cd %ORACLE_HOME%\Bundle\Patch8
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA 
    SQL> STARTUP
    SQL> @catcpu.sql
    SQL> QUIT 
    
  5. Check the following log files in $ORACLE_BASE/cfgtoollogs/catbundle for any errors:

    catbundle_WINBUNDLE_<database SID>_APPLY_<TIMESTAMP>.log
    catbundle_WINBUNDLE_<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".

  6. If Database Vault is installed, enable Database Vault before proceeding to the next step. See Section 3.5.2 for instructions to enable Database Vault.

  7. To ensure all dependant objects are valid after running catcpu.sql:

    (For large numbers of objects, this compilation step can take some time. If you are applying this patch through the Oracle Enterprise Manager console, you will be prompted to run this compilation script.)

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

    To check for invalid objects, execute the following statement:

    SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID'; 
    

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


Note:

For all Oracle Database releases, you must run the post-installation steps (that is, the catcpu.sql script) for any new database you create or database upgraded to this release since the Bundle patch was applied.

3.3.7 Post Installation Instructions for Databases Created or Upgraded after Installation of Bundle Patch8 in the Oracle Home

These instructions are for both RAC environments and non-RAC environments when a database is created or upgraded after the installation of Bundle Patch8.

You must execute the steps in Section 3.3.6.1, "Loading Modified .sql Files into the Database" for any new database that 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

  • Cloning a database that was created by either of the two preceding methods, and if Section 3.3.6.1, "Loading Modified .sql Files into the Database" was not executed after Bundle Patch8 was applied

Upgraded databases require that you perform the steps in Section 3.3.6.1, "Loading Modified .sql Files into the Database" if these steps have not previously been performed; otherwise, no post-installation steps need to be performed.

3.4 Patch Deinstallation Instructions for Oracle Database Release 11.2.0.2 Patch8

This section includes the following topics.

3.4.1 Patch Deinstallation Instructions for Single Instance

Follow these steps:

  1. Verify that an $ORACLE_HOME/rdbms/admin/catbundle_WINBUNDLE_<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.6.1, "Loading Modified SQL Files into the Database" against the database before deinstalling the patch.

  2. Cleanly shut down all processes running from the ORACLE_HOME.

  3. Stop all Oracle Services, Distributed Transaction Coordinator (which is not an Oracle service), and all applications accessing the database to which you are applying the patch.

  4. Set the ORACLE_HOME environment variable to the correct Oracle home that was patched.

    > set ORACLE_HOME=<Oracle Home Path> 
    
  5. Go to the directory where you downloaded the patch:

    > cd 12714462
    
  6. Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:

    > opatch rollback -id 12714462 
    
  7. Inspect the opatch<timestamp>.log file generated in %ORACLE_HOME%\cfgtoollogs\opatch for any errors.

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

3.4.2 Patch Deinstallation instructions for Oracle Instant Client

Follow these steps:

  1. If you patched the Oracle Instant Client installation by following the steps in Section 3.3.3, "Patch Installation Instructions for Oracle Instant Client", you can roll back this patch by re-copying the oraociei11.dll, oraociei11.sym, oraociicus11.dll, oraociicus11.sym, sqora32.dll, sqoras32.dll and sqresus.dll, file to the installation.

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

3.4.3 ODP.NET 2.x Deinstallation Instructions

Follow these steps only if you are using ODP.NET:

  1. Open a command prompt. (Open via "Run As Administrator" if applying on Windows 7 or 2008R2 and User Account Control is enabled).

  2. Navigate to the %ORACLE_HOME%\ODP.NET\bin\2.x directory.

  3. Execute the following to install the previous ODP.NET assembly:

     oraprovcfg.exe /action:gac /providerpath:Oracle.DataAccess.dll
    

3.4.4 ODP.NET 4.0 Deinstallation Instructions

Follow these steps only if you are using ODP.NET:

  1. Open a command prompt. (Open via "Run As Administrator" if applying on Windows 7 or 2008R2 and User Account Control is enabled).

  2. Navigate to the %ORACLE_HOME%\ODP.NET\bin\4 directory.

  3. Execute the following to install the previous ODP.NET assembly:

     oraprovcfg.exe /action:gac /providerpath:Oracle.DataAccess.dll
    

3.4.5 Post Deinstallation Instructions

Follow these steps:

  1. Start the OracleService<SID> and Oracle Listener Services.

  2. Start all database instances running out of the ORACLE_HOME that you just patched.

  3. If Database Vault is installed, disable Database Vault before proceeding to the next step. See Section 3.5.1 for instructions to disable Database Vault.

  4. For each database instance running out of the ORACLE_HOME being patched, connect to the database using SQL*Plus as SYSDBA and follow these steps:

    > cd %ORACLE_HOME%\rdbms\admin
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA 
    SQL> STARTUP
    SQL> @catbundle_WINBUNDLE_<database_SID>_ROLLBACK.sql
    SQL> QUIT
    
  5. Check the log file for any errors. The log file is found in $ORACLE_BASE/cfgtoollogs/catbundle and is named catbundle_WINBUNDLE_<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".

  6. If Database Vault is installed, enable Database Vault before proceeding to the next step. See Section 3.5.2 for instructions to enable Database Vault.

  7. If catcpu_rollback.sql reports any Invalid Objects, compile the invalid objects as follows.

    (For large numbers of objects, this compilation step can take some time. If you are applying this patch through the Oracle Enterprise Manager console, you will be prompted to run this compilation script.)

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

    To check for invalid objects, execute the following statement:

    SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID'; 
    
  8. If there are errors, refer to Section 4, "Known Issues".

3.5 Disabling and Enabling Database Vault

This section applies if you were instructed earlier to disable or enable Database Vault.

3.5.1 Disabling Database Vault

To disable Database Vault, follow these steps. (For RAC systems, perform steps 1 and 2 for each node on which the database is installed.)

  1. Ensure that the OracleService and Oracle Listener Services are not running.

  2. Rename %ORACLE_HOME%\bin\oradv11.dll to %ORACLE_HOME%\bin\oradv11.dll_backup.

  3. Start the OracleService<SID> and Oracle Listener Services.

3.5.2 Enabling Database Vault

To enable Database Vault, follow these steps. (For RAC systems, perform steps 1 and 2 for each node on which the database is installed.)

  1. Ensure that the OracleService and Oracle Listener Services are not running.

  2. Under %ORACLE_HOME%\bin, name the backup of the oradv11.dll file to its original name. For example, if you named it oradv11.dll_backup, then name it back to oradv11.dll.

  3. Start the OracleService<SID> and Oracle Listener Services.

4 Known Issues

This section includes the following information:

4.1 Issues Common to All Releases

This section includes issues common to all Oracle Database releases:

4.1.1 Generic Issues

The following are generic issues common to all platforms:

  • Issue 1: The following ignorable errors may be encountered while running the catcpu.sql and catcpu_rollback.sql scripts

    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-01951: ROLE 'CONNECT' not granted to 'WKSYS'
    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-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-02289: sequence does not exist 
    ORA-20002: Unable to create table IMPDP_STATS: already exists
    
  • Issue 2: If the NLS_LANG environment variable is set to Japanese_Japan.JA16EUC or Japanese_Japan.JA16SJIS, while executing catcpu.sql (and catcpu_rollback.sql), the following errors may occur:

    SP2-0768: Illegal SPOOL commandSP2-0768: Illegal SPOOL command
    Usage: SPOOL { <file> | OFF | OUT }
    where <file> is file_name[.ext] [CRE[ATE]|REP[LACE]|APP[END]]
    

    Workaround:

    Before running the catcpu.sql or catcpu_rollback.sql scripts, run the following SQL statement to change the nls_language setting:

    SQL>ALTER SESSION SET nls_language='American';
    
  • Issue 3: If you are applying the patch using a Terminal Services or Remote Desktop Connection and experiencing problems, attempt to apply the patch locally at the console of the machine against which the patch is being applied before filing a Service request with Oracle Global Product Support.

4.1.2 Platform-specific Issues

There are no known platform-specific issues.

4.2 Issues Specific to Oracle Database Release 11.2.0.2 Patch8

There are no known issues specific to 11.2.0.2 release.

4.3 Issues Specific to OPatch

There are no known issues specific to OPatch.

4.4 Issues Specific to this Patch

There are no known issues specific to this patch.

5 Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. 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

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, 7 days a week. For TTY support, call 800.446.2398. Outside the United States, call +1.407.458.2479.


Oracle Database Bundle Patch Update Note Release 11.2.0.2 for Microsoft Windows (32-Bit)

Copyright © 2006, 2010, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States 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, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.