Skip Headers

Oracle® Database

Patch 17478514 - 11.2.0.4.1 Patch Set Update

 

Released: January 14, 2014

This document is accurate at the time of release. For any changes and additional information regarding PSU 11.2.0.4.1, 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.4.1 includes the fixes listed in Section 8, "Bugs Fixed by This Patch".

To install the PSU 11.2.0.4.1 patch, the Oracle home must have the 11.2.0.4.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 11.2.0.4.0 or any PSU with a lower 5th numeral version than the one being installed.

This patch is Oracle RAC Rolling Installable.

This patch is Data Guard Standby-First Installable. See My Oracle Support Document 1265700.1 Oracle Patch Assurance - Data Guard Standby-First Patch Apply for details on how to remove risk and reduce downtime when applying this patch.

This patch contains a security fix due to which a SELECT query's plan MAY change under the following conditions:

  • The SELECT queries a table protected with a Fined Grained Auditing policy

  • And the policy condition is NULL

Table 1 describes installation types and security content. For each installation type, it indicates the most recent PSU patch to include new security fixes that are pertinent to that installation type. If there are no security fixes to be applied to an installation type, then "None" is indicated. If a specific PSU is listed, then apply that or any later PSU patch to be current with security fixes.

Table 1 Installation Types and Security Content

Installation Type Latest PSU with Security Fixes

Server homes

PSU 11.2.0.4.1


Client-Only Installations

None

Instant Client Installations

None

(The Instant Client installation is not the same as the client-only Installation. For additional information about Instant Client installations, see Oracle Call Interface Programmer's Guide.)


2 Prerequisites

This section includes the following section:

2.1 OPatch Utility

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

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

3 Installation

These instructions are for all Oracle Database installations.

3.1 Patch Pre-Installation Instructions

Before you install PSU 11.2.0.4.1, 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 (GI)

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

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 p17478514_11204_<platform>.zip
    cd 17478514
    opatch prereq CheckConflictAgainstOHWithDetail -ph ./
    
  2. The report will indicate the patches that conflict with PSU 17478514 and the patches for which PSU 17478514 is a superset.

    Note that Oracle proactively provides PSU 11.2.0.4.1 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 an Oracle RAC environment, install the PSU patch using the OPatch rolling (no downtime) installation method as the PSU patch is rolling Oracle RAC installable. Refer to My Oracle Support Document 244241.1 Rolling Patch - OPatch Support for RAC.

  3. If this is not a Oracle RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.

  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 p17478514_11204_<platform>.zip
    cd 17478514
    opatch apply
    
  5. If there are errors, refer to Section 6, "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 an Oracle 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 6, "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.4.1 in the Oracle Home

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

4 Deinstallation

These instructions apply if you need to deinstall the patch.

4.1 Patch Deinstallation Instructions for a Non Oracle 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 17478514
    
  4. If there are errors, refer to Section 6, "Known Issues".

4.2 Patch Post-Deinstallation Instructions for a Non Oracle 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 an Oracle 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 6, "Known Issues".

4.3 Patch Deinstallation Instructions for an Oracle 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 17478514
    

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

  3. Start the instance on the node as follows:

    srvctl start instance
    

4.4 Patch Post-Deinstallation Instructions for an Oracle RAC Environment

Follow the instructions listed in Section Section 4.2, "Patch Post-Deinstallation Instructions for a Non Oracle RAC Environment" only on the node for which the steps in Section 3.3.2, "Loading Modified SQL Files into the Database" were executed during the patch application.

All other instances can be started and accessed as usual while you are executing the deinstallation steps.

5 Instructions for Patching a Grid Infrastructure (GI) Home

This section describes patch installation and deinstallation instructions for a Grid Infrastructure (GI) home.

5.1 Patch Installation Instructions for a GI Home

Use the following instructions to install this patch in an Oracle GI home.

Case 1: Shared GI Home

Follow these instructions in this section if the GI home is shared.


Note:

Patching a shared GI home requires shutdown of Oracle GI stack on all the remote nodes in the cluster. This also means you need to stop all Oracle RAC databases that depend on the GI stack, ASM for data file, or ACFS file system for database software.

  1. Make sure to stop the Oracle databases running from the Oracle RAC or Oracle RAC One Node database homes.

    As Oracle database home owner:

    $ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>
    
  2. Make sure the ACFS file systems are unmounted on all the nodes.

    Follow the instructions in the following My Oracle Support Document for unmounting ACFS file systems:

    • 1494652.1 How to Mount or Unmount ACFS File System While Applying GI Patches?

  3. As root user, execute the following on all the remote nodes to stop the CRS stack:

    # <GI_HOME>/bin/crsctl stop crs
    
  4. Execute the following command on the local node

    As root user execute:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -ocmrf <ocm response file>
    
  5. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  6. On each remote node:

    1. As root user, run:

      # <GI_HOME>/crs/install/rootcrs.pl -patch
      
    2. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

    3. Start the Oracle GI stack on all the remote nodes.

      As root user execute:

      # <GI_HOME>/bin/crsctl start crs
      
  7. Mount ACFS file systems.

    Follow the instructions in the following My Oracle Support Document for mounting ACFS file systems:

    • 1494652.1 How to Mount or Unmount ACFS File System While Applying GI Patches?

  8. Restart the Oracle databases that you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start database –d <db-unique-name>
    

Case 2: Non-Shared GI Home

If the GI home is not shared then use the following instructions to patch the home.

Case 2.1: ACFS File System Is Not Configured

Follow these instructions in this section if the GI home is not shared and none of the Oracle database homes use ACFS file system for its software files.

Execute the following on each node of the cluster.

As root user execute:

# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -ocmrf <ocm response file>

Case 2.2: ACFS File System Is Configured

Repeat Steps 1 through 6 for each node in the cluster:

  1. From the Oracle database home, stop the Oracle RAC database running on that node.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl stop instance –d <db-unique-name> -n <node_name>
    
  2. Unmount all ACFS file systems on this node.

    Follow the instructions in the following My Oracle Support Document for unmounting ACFS file systems:

    • 1494652.1 How to Mount or Unmount ACFS File System While Applying GI Patches?

  3. Apply the patch to the GI home on that node using the opatch auto command.

    Execute the following command on that node in the cluster.

    As root user execute:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -ocmrf <ocm response file>
    
  4. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  5. Remount ACFS file systems on that node.

    Follow the instructions in the following My Oracle Support Document for mounting ACFS file systems:

    • 1494652.1 How to Mount or Unmount ACFS File System While Applying GI Patches?

  6. Restart the Oracle database on that node that you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename>
    

5.2 Patch Deinstallation Instructions for a GI Home

Use the following instructions to roll back the patch in an Oracle GI home

Case 1: Shared GI Home

Follow these instructions in this section if the GI home is shared.


Note:

An operation in a shared GI home requires shutdown of Oracle GI stack on all the remote nodes in the cluster. This also means you need to stop all Oracle RAC databases that depend on the GI stack, ASM for data file, or ACFS file system for database software.

  1. Make sure to stop the Oracle databases running from the Oracle RAC database homes.

    As Oracle database home owner:

    $ <ORACLE_HOME>/bin/srvctl stop database -d <db-unique-name>
    
  2. Make sure the ACFS file systems are unmounted on all the nodes.

    Follow the instructions in the following My Oracle Support Document for unmounting ACFS file systems:

    • 1494652.1 How to Mount or Unmount ACFS File System While Applying GI Patches?

  3. As root user, execute the following on all the remote nodes to stop the CRS stack:

    # <GI_HOME>/bin/crsctl stop crs
    
  4. Execute the following command on the local node.

    As root user execute:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback -ocmrf <ocm response file>
    
  5. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  6. Start the Oracle GI stack on all the remote nodes.

    As root user execute:

    # <GI_HOME>/bin/crsctl start crs
    
  7. Mount ACFS file systems.

    Follow the instructions in the following My Oracle Support Document for mounting ACFS file systems:

    • 1494652.1 How to Mount or Unmount ACFS File System While Applying GI Patches?

  8. Restart the Oracle databases that you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start database -d <db-unique-name>
    

Case 2: Non-Shared GI Home

If the GI home is not shared, then use the following instructions to roll back the patch from the GI home.

Case 2.1: ACFS File System Is Not Configured

Follow these instructions in this section if the GI home is not shared and none of the Oracle database homes is shared.

Execute the following on each node of the cluster.

As root user execute:

# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback -ocmrf <ocm response file>

If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

Case 2.2: ACFS File System Is Configured

Repeat Steps 1 through 6 for each node in the cluster:

  1. From the Oracle database home, stop the Oracle RAC database running on that node.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl stop instance –d <db-unique-name> -n <node_name>
    
  2. Make sure the ACFS file systems are unmounted on that node.

    Follow the instructions in the following My Oracle Support Document for unmounting ACFS file systems:

    • 1494652.1 How to Mount or Unmount ACFS File System While Applying GI Patches?

  3. Roll back the patch to the GI home on that node using the opatch auto command.

    Execute the following command on each node in the cluster.

    As root user execute:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback -ocmrf <ocm response file>
    
  4. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  5. Remount ACFS file systems on that node.

    Follow the instructions in the following My Oracle Support Document for mounting ACFS file systems:

    • 1494652.1 How to Mount or Unmount ACFS File System While Applying GI Patches?

  6. Restart the Oracle database on that node that you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start instance -d <db-unique-name> -n <node_name>
    

6 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 1593200.1 Oracle Database Patch Set Update 11.2.0.4.1 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   

Warnings may be returned during the re-link phase of 17478514. These warnings may be ignored.

warning: overriding commands for target `nmosudo'
warning: ignoring old commands for target `nmosudo'

See the following document for additional information.

Document 1562458.1 Relinking the DB Control 11.2.0.3 Agent Displays a Warning Message "overriding commands for target 'nmosudo'"

Issue 3   

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.

7 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 1321267.1 Database Patch conflict resolution

Document 17478514.8 Database 11.2.0.4.1 Patch Set Update (PSU)

Document 1449750.1 11.2.0.4 Patch Set Updates - List of Fixes in each PSU

Document 1561792.2 Patching Assistant: Oracle Database/Client - Select PSU/SPU (aka CPU)

8 Bugs Fixed by This Patch

This patch includes the following bug fixes.

8.1 Bug Fixes

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

PSU 11.2.0.4.1 contains the following new fixes:

Automatic Storage Management


12905058 - REBOOT 2 CELL NODES, CHECKFILE FOUND CORRUPTION BLOCK IN 3 UNDO DATAFILES

16850630 - EXCESSIVE KFODAAPPLIANCE TRACING IN GMON

17443671 - EXADATA: OUTPUT BUFFER FOR READ CONTROL MESSAGE PAYLOAD TOO SMALL

Generic


17332800 - WRONG RESULTS WHERE QUERIES INVOLVES IOTS WITH SECONDARY INDEXES.

16450169 - Fix for bug 16450169

16721594 - Fix for bug 16721594

High Availability


16069901 - LNX64-12.1-RAC-CDB:DB INST RMV PROC HANG SINCE WAITING FOR LATCH: GC ELEMEN

Oracle Spatial


17088068 - Fix for bug 17088068

Oracle Storage Server Service Layer


17446237 - KCFIS BLOCK REPAIR SHOULD BE SUPPRESSED UPON GETTING 'BLOCK TO BE RESILVERED'

Oracle Streams


16285691 - OCIPOGGCAPTURE API ABORTED WITH KPEDBGCRASH WHEN DIAG_DDE_ENABLED IS TRUE

Oracle Transaction Management


13944971 - Fix for bug 13944971

Oracle Utilities


17288409 - W2K8_11204_UD:11202=>11204 RAC HIT EVENT OR _TRACE_EVENT PARAMETERS SET WARNING

Oracle Virtual Operating System Services


17501491 - ODM API VERSION IS NOT CORRECT FOR ODM_MKDIR CALL IN 11.2.0.4.0

17612828 - WRONG BUFFER ALLOCATION SIZE FOR REPLAY IN KSFDSS.C CRASHES LIBC MALLOC

PL/SQL


17610798 - ORA-65020 CAN OCCUR IN RMAN EXECUTING ALTER PLUGGABLE DATABASE CLOSE IMMEDIATE

Patch Automation


13866822 - REGISTRY$HISTORY NOT UPDATED CORRECTLY AFTER RB OF 11.2.0.3.2 THEN 11.2.0.3.1

XML Utilities


17239687 - [11204-AIX-130715] NLS: ORA-31061 AND ORA-19202 REPORTED WHEN RUNNING DBUA

9 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 17478514 - 11.2.0.4.1 Patch Set Update Release 11.2.0.4.1 for UNIX

Copyright © 2006, 2014, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.