Skip Headers

Oracle® Database

Patch 9209238 - 11.1.0.7.2 Patch Set Update

 

Released: January 12, 2010

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

To install the PSU 11.1.0.7.2 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.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 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 and Components for Patch 9209238

The PSU is made available on the following platforms:

  • HP-UX Itanium

  • HP-UX PA-RISC (64-bit)

  • IBM AIX on POWER Systems (64-bit)

  • Linux x86

  • Linux x86-64

  • Sun Solaris SPARC (64-bit)

Components patched by this Patch Set Update:

  • Advanced Networking Option

  • Enterprise Manager for RDBMS

  • Oracle Data Mining

  • Oracle Database

  • Oracle Database Vault

  • Oracle Net Services

2.2 OPatch Utility Information

You must use the OPatch utility version 11.1.0.6.7 or later. 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.2, 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 your Oracle Database installation is the same base release for which you are applying this patch. In other words, only apply the PSU 11.1.0.7.2 patch to Oracle Database Release 11.1.0.7.0.

  2. 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
  1. Determine whether any currently installed one-off patches conflict with the PSU patch as follows:

    unzip p9209238_11107_<platform>.zip
    opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./9209238
    
  2. The report will indicate the patches that conflict with PSU 9209238 and the patches for which PSU 9209238 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. 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. Review Section 3, "Known Issues" before proceeding with this installation.

  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 p9209238_11107_<platform>.zip
    cd 9209238
    opatch apply
    
  5. If any currently installed one-off patches conflict with the PSU patch, 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".

  6. 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. Load modified .sql files into the database, as explained in Section 2.3.3.1.

  2. Recompile views in the database, if necessary, as explained in Section 2.3.3.2.

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

(Note that if there is a database in the Oracle home that you are patching, this will involve starting all database instances running from this Oracle home.)

  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
    

    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.2 Recompiling Views in the Database

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


Note:

Depending on these considerations and your downtime schedule, you can choose to schedule the recompilation of views independent of the rest of the PSU installation. If you do this, your system will continue to work; however, the PSU installation will not be complete until the view recompilation is completed.

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;
    

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

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

You must execute the steps in Section 2.3.3.1, "Loading Modified .sql Files into the Database" for any new database only if it was created by any of the following methods:

  • Using DBCA (Database Configuration Assistant) to select a sample database (General, Data Warehouse, Transaction Processing)

  • Using a script that was created by DBCA that creates a database from a sample database

Upgraded databases require that you perform the steps in Section 2.3.3.2, "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.1, "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 9209238
    
  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 that you had patched. (For more information, see Oracle Database Administrator's Guide.)

  2. For each database instance running out of the ORACLE_HOME that was patched, 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 9209238
    

    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.1, "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 967468.1 Oracle Database Patch Set Update 11.1.0.7.2 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-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.
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.2:

PSU 11.1.0.7.2 contains all molecules previously released in PSU 11.1.0.7.1 and the following new PSU 11.1.0.7.2 molecules:

9118620 - DB-11.1.0.7-MOLECULE-018-CPUJAN2010

9118622 - DB-11.1.0.7-MOLECULE-019-CPUJAN2010

5.2 Bug Fixes

PSU 11.1.0.7.2 contains all fixes previously released in PSU 11.1.0.7.1 and the following new fixes:

6407486 - ORA-600 [KOLE_T2U] USING A BLOB TABLE

6768362 - REGRESSION IN 11.1 FOR LOAD TESTS, SEGMENT HEADER CONTENTION

6784747 - WASTED SPACE - KOH-KGHU CALL ALLOCATION

6843972 - ORA-600 [KOLE_T2U] USING SYS.HTTPURITYPE

6903819 - PHSB: ORA-19648 RAISED DURING BACKUP ON READABLE STANDBY

6972189 - INVALID PACKAGE BODIES IN APPS 12.1

6991626 - APPSST11G:EXPORT DATAPUMP FAILS WITH ORA-39126 AND ORA-22813

7119382 - V$DATAGUARD STATS RETURNS MISLEADING AND INCONSISTENT RESULT

7253531 - ORA-7445 [TTCI2U] FOR SOME APPS FUNCTIONALITY AFTER UPGRADE

7257038 - USING DBMS_REDEFINITION ON STREAMS TABLE CAUSES "MISSING STR

7258928 - SCHEDULER JOBS THAT ARE HANGING, CANNOT BE STOPPED

7307972 - HIGH VALUE FOR LIBRARY CACHE: MUTEX X" IN AWR AS TOP WAIT E

7334226 - GES RECEIVERS ARE NOT HEALTHY

7377810 - APPS R12: LARGE BUFFER_GETS DURING HARD PARSE

7409110 - WARNING: ASYNCH I/O KERNEL LIMITS FROM LGWR & DBW0

7441663 - FIX MINIMUM BUFFER CACHE SIZE CALCULATION

7447559 - LIBRARY CACHE LOCKS ON ALL JOB PROCESSES

7462589 - RMAN BACKUP AS COPY REUSE DATAFILE 5 AUXILIARY FORMAT '+BAKG

7477246 - DISKS TAKEN OFFLINE DURING SYNCING PHASE OF THE ONLINE DISK

7500792 - HIGH GETS ON "KOKC DESCRIPTOR ALLOCATION LATCH" WITH MORE T

7630874 - PARALLEL ALLOCATION ACROSS ASM INSTANCES TAKES 6X LONGER

7639602 - HIGH SESSION ALLOCATION LATCH AND RECURSIVE CALLS FOR A JOB

7643188 - SQL VERSION COUNT REPORTED IN AWR DOES NOT MATCH SQLSTATS FO

7653579 - ASM INSTANCE EVICTED WITH ORA-29740

7690421 - INVALID TZ VALUE IN TIMEZONE COLUMN PRODUCES ORA-01875

7694979 - ORA-00904: RAISED FOR COMPLEX ADTS RESIDING IN DIFF. SCHEMAS

7715244 - COMPRESS WITH SQLLDR CONVENTIONAL PATH [KDBLKCHECKERROR], [4

7829321 - TB:SH: CKPT HIT ORA-00600: [KCBKLLRBA_1] ORA-00600:[KCBKVAQ_

8199107 - APPSST11107: GOT ORA-07445 DURING R12.1.1 XBUILD3 UPGRADE

8214576 - A PLACEHOLDER FOR THE SECOND FIX INCLUDED INTO 6897966

8217795 - PATCH 7409110 APPLIED STILL HAVING WARNING:COULD NOT SET TH

8221425 - STBH:HP:11G - ORA-04031: UNABLE TO ALLOCATE 912 BYTES OF SHA

8277580 - ORA-07445: [__INTEL_NEW_MEMCPY()+44]

8281906 - STBH: DBMS SCHEDULE JOB DUMPS HUGE TRACE FILE AND CONSUMES A

8287680 - OLTP TABLE COMPRESSION INSERT PERFORMANCE

8328853 - SR11.2EVENTLESS - COORDINATOR ARCH IN PARALLEL ARCHIVAL ORA-

8348464 - PACKAGE TURN TO INVALID BY CREATING SYNONYM

8348481 - TB_X64:SH: DBWR HIT ORA-00600: [KJBWRDONE:!OP], INSTANCE CRA

8364676 - ROW CACHE LOCK CONTENTION WHEN COMPRESSING TABLE USING ALTER

8483871 - SECUREFILE IS SLOWER WHEN DB_BLOCK_CHECKING=TRUE IS SET

8499043 - SET CONTEXT TRIGGERING DLM OVERHEAD ON SYNC CONTEXT KGL

8539335 - ORA-600 [KTCIRS:HDS] REPORTED ON MULTIPLE NODES IN A RAC CL

8549480 - APPSST GSI 11G: ORA-600[KDLIMEMVALIDATE] DURING DB UPGRADE

8565708 - STRESS SOA - ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [409

8588540 - ORA-08102: INDEX KEY NOT FOUND RETURNED ON SOME UPDATES.

8613137 - TABLE UPDATE GENERATES AN ORA-600 [6200]

8650661 - ORA-600[KDSGRP1] SIGNALLED IN MEDIATOR TEST WITH SOA IN FUSI

8674263 - TB_X64_ASM: ORA-00600: [KFIOTRANSLATEIO05] DURING ASM STRESS

8702535 - ORA-07445[KSLGETSL()+120] WHILE DUMPING SYSTEMSTATE AFTER AP

8717461 - ORA-00494 ON THE DB NODES HOSTED ON EXADATA WAIITING ON KSV

8790767 - APPSST GSI 11G: INSTANCE CRASHED WITH ORA-600[KCBKLLSCN_1] E

8834636 - CONCURRENT INSERTS INTO COMPRESSED TABLE CAUSES HIGH CPU AND

8851675 - STBH: BAD PARTNERING CAUSES PREMATURE ALLOCATION FAILURES

8876094 - APPSST GSI 11G :- ORA-00308 IN ALERT LOGS OF OUR ENVIRONMEN

8898852 - DATAFILE CORRUPTION WHEN FILE CREATED WITH COMPATIBLE.ASM LE

9066130 - APPSST GSI 11G :-ORA-00600: INTERNAL ERROR CODE, ARGUMENTS:

9135679 - INSTANCE TERMINATED WITH ORA-00600 [KGSKEXITSCH]

9188010 - CORE DUMP IN KGLDMP WHEN USING RAC AND DUMPING SYS.REGISTRY$

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