Patch 8833297 - 11.1.0.7.1 Patch Set Update
Released: October 20, 2009
This document is accurate at the time of release. For any changes and additional information regarding PSU 11.1.0.7.1, see these related documents that are available at My Oracle Support (http://myoraclesupport.oracle.com/):
Note 854428.1 Patch Set Updates for Oracle Products
Note 881732.1 Oracle Database Patch Set Update 11.1.0.7.1 Known Issues
This document includes the following sections:
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.1 includes the following previously released bundle patches:
Generic Recommended Bundle #1 (Patch 8362693)
Generic Recommended Bundle #2 (Patch 8658581)
Data Guard Logical Recommended Bundle #1 (Patch 7628387)
Data Guard Physical Recommended Bundle #1 (Patch 7676737)
RAC Recommended Bundle #1 (Patch 8461420) except for 7373877 and 7438445
To install the PSU 11.1.0.7.1 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.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 Database Concepts.) |
|
ASM (Automatic Storage Management) homes |
PSU 11.1.0.7.1 |
|
CRS (Cluster Ready Services) homes |
None |
This section includes the following sections:
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
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.
These instructions are for both non-RAC environments and RAC environments.
Before you install PSU 11.1.0.7.1, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.
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.1 patch to Oracle Database Release 11.1.0.7.0.
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
Determine whether any currently installed one-off patches conflict with the PSU patch as follows:
unzip p8833297_11107_<platform>.zip opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./8833297
The report will indicate the patches that conflict with PSU 8833297 and the patches for which PSU 8833297 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.1 one-off patches for common conflicts.
When all the 11.1.0.7.1 one-off patches that you have requested are available at My Oracle Support, proceed with Section 2.3.2, "Patch Installation Instructions".
Follow these steps:
Review Section 3, "Known Issues" before proceeding with this installation.
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.)
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.
Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
unzip p8833297_11107_<platform>.zip
cd 8833297
opatch apply
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".
If there are errors, refer to Section 3, "Known Issues".
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:
Load modified .sql files into the database, as explained in Section 2.3.3.1.
Recompile views in the database, if necessary, as explained in Section 2.3.3.2.
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.)
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.
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".
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.
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.
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
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>
Check the log file for any errors. The log file is in the current directory and is named: vcomp_<sid>_<timestamp>.log
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;
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.1.
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.
These instructions are for both Non-RAC environments and RAC environments.
Section 2.4.1, "Patch Deinstallation Instructions for a Non-RAC Environment"
Section 2.4.2, "Post Deinstallation Instructions for a Non-RAC Environment"
Section 2.4.3, "Patch Deinstallation Instructions for a RAC Environment"
Section 2.4.4, "Post Deinstallation Instructions for a RAC Environment"
Follow these steps:
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.
Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
Run the OPatch utility specifying the rollback argument as follows.
opatch rollback -id 8833297
If there are errors, refer to Section 3, "Known Issues".
Follow these steps:
Start all database instances running from the Oracle home that you had patched. (For more information, see Oracle Database Administrator's Guide.)
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.
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".
Follow these steps for each node in the cluster, one node at a time:
Shut down the instance on the node. (Shut down all RDBMS instances before any ASM instances.)
Run the OPatch utility specifying the rollback argument as follows.
opatch rollback -id 8833297
If there are errors, refer to Section 3, "Known Issues".
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
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.
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 881732.1 Oracle Database Patch Set Update 11.1.0.7.1 Known Issues.
Other known issues are as follows.
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.
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.
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.
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 8833297.8 Bug 8833297 - 11.1.0.7.1 Patch Set Update (PSU)
This patch includes the following bug fixes.
CPU molecules in PSU 11.1.0.7.1:
PSU 11.1.0.7.1 contains all molecules previously released in CPUJul2009 and the following new PSU 11.1.0.7.1 molecules:
8855553 - DB-11.1.0.7-MOLECULE-012-CPUOCT2009
8855559 - DB-11.1.0.7-MOLECULE-013-CPUOCT2009
8855565 - DB-11.1.0.7-MOLECULE-014-CPUOCT2009
8855570 - DB-11.1.0.7-MOLECULE-015-CPUOCT2009
8855575 - DB-11.1.0.7-MOLECULE-016-CPUOCT2009
8855577 - DB-11.1.0.7-MOLECULE-017-CPUOCT2009
Note that the following CPUJul2009 molecules were replaced in PSU 11.1.0.7.1 and therefore are not included:
8306933 - DB-11.1.0.7-MOLECULE-001-CPUAPR2009
8563945 - DB-11.1.0.7-MOLECULE-008-CPUJUL2009
PSU 11.1.0.7.1 contains all fixes previously released in Generic Recommended Bundles #1 and #2 and the following new fixes:
6812439 - EXTERNAL TABLE FILES READ IN RANDOM ORDER
6981690 - CURSOR NOT SHARED WHEN RUNNING PX QUERY ON MOUNTED RAC SYSTE
7378322 - ORA 600 - 6704 GENERATED FOR A JOIN QUERY ON A HASH PARTITI
7420394 - ORA-00600: ARGUMENTS: [KGIINB_INVALID_OBJ] DURING DATABASE C
7496908 - ORA-600 [KCFNEW_2]
7497640 - WRONG RESULTS WITH 'UNION ALL PUSHED PREDICATE'
7586451 - STBH:AROLTP-C:LMS0 DIED AFTER HITTING ORA-00600 [KCLCHKINTEG
7706138 - HANG OCCURRED BY WAITING FOR "LIBRARY CACHE LOAD LOCK" IN RE
7708340 - PLS-00908 ERROR WHEN OBJECTS ARE ACCESSED ACROSS DBLINK.
7716219 - HASH GROUP BY INEFFICIENT AND GENERATING MUCH MORE TEMP THAN
8284438 - ADAPTIVE SHRUNK AGGREGATION PERFORMS THE CHECK 2 SWITCH TO S
8284633 - SHRUNK AGGREATION NEEDS TO BE ENABLED WHEN ADAPTIVE FETCH KI
8318050 - AUTOEXTEND INCREMENT OF 16 GBYTE DOES NOT INCREMENT FILES BY
8419383 - MLR OF 7716219, 8284438 AND 8284633 FOR 11.1.0.7
8499600 - ORA-01555 ERRORS ON SECUREFILES READS EVEN UNDER LOW LOADS/N
8543737 - SPACE LEAK AFTER PARTITION MIGRATION OF TABLE WITH LOB COLUM
8940197 - ORA-00600: [QKEXRXFORMOPN_COL1] AFTER APPLY PATCH 8658581
7652888 - QUEUE SPILLAGE AT SOURCE DATABASE AFTER UPGRADE TO 11.1.0.7
7719668 - STREAMS MEMORY ACCOUNTING INCORRECT, LEADING TO CAPTURE 'PAU
8211920 - STREAMS APPLY FAILS WITH ORA-00600: [KGQMDEQ788]
8243648 - LOGMNR CHECKPOINT MAY BE TURNED OFF COMPLETELY BY CERTAIN I
8462173 - STREAMS APPLY _TXN_BUFFER_SIZE AUTO-TUNE REDUCES APPLY THOUG
8542307 - INTERNAL ERROR WHILE LOGMINING SESSION EXIT ON CERTAIN WORKL
PSU 11.1.0.7.1 contains all fixes previously released in Generic Recommended Bundle #1 except for 7373877 and 7438445, and it contains the following new fix:
8856696 - AROLTP-D: INSTANCES HANG WITH 'FREE BUFFER WAITS' OR HIT ORA
All fixes previously released in Data Guard Logical Recommended Bundle #1 and Data Guard Physical Recommended Bundle #1 are included in PSU 11.1.0.7.1. There are no new Data Guard bug fixes.
6618461 - DBRM ACTIVE SESSION POOL WITH QUEUING CAUSES UNEXPECTEDLY LO
7348847 - BLOOM FILTER IN STORAGE DOES NOT APPEAR TO REDUCE DATABASE C
7366290 - LNX11.2: BLOCK, ORA-353 LOG CORRUPTION ERRORS
7373196 - ORA-600 [KRR_INIT_LBUFS_1] DURING DATABASE RECOVERY
7393258 - EXP PLAN DOESN'T SHOW OFFLOAD FOR GLOBAL TEMPORARY TABLES WH
7412296 - SHUTDOWN ABORT SHOULD NOT START HANG ANALYSIS
7416901 - DEADLOCK BETWEEN QC AND SLAVES WHEN CELL_PARTITION_LARGE_EXT
7432556 - PQ FAILED WITH ORA-8103
7462112 - ORA-600 [KCBL_PREDPUSH_GET_STATUS]
7477246 - DISKS TAKEN OFFLINE DURING SYNCING PHASE OF THE ONLINE DISK
7515145 - [KCFIS_WAIT()+878] [SIGSEGV]
7515779 - DIRECT PATH LOAD OPERATIONS INCUR WAITS FOR CONTROL FILE SEQ
7572069 - PDML INSERT RESULTS IN ORA-60002 - MAXSIZE IS TOO SMALL
7628866 - ORA-600 [KCFIS_PUSH1] OCCURS WHEN NUMBER OF GRID-DISKS ON A
7630416 - INVALID VALUES FOR "BUFFER CACHE HIT RATIO" IN SYSMETRIC VI
7639121 - ORA 600 [KCFIS_PROCESS_COMPLETED_REQ_INVALID_ELEMENT]
7705669 - INCREASE _KCFIS_READ_BUFFER_LIMIT DEFAULT..
7720494 - KCFIS: WAITED TOO LONG TO READ DATA. MESSAGES IN TRACE FILE
7834195 - DATABASE NODE CRASHES; PX PROCESSES SPIN ON ANOTHER NODE
8213302 - ORA-7445 [KFIS_SET_ERROR()+16] DURING BENCHMARK ON EXADATA
8224083 - ORA-07445: EXCEPTION ENCOUNTERED: CORE DUMP [MEMCPY()+96] [S
8236851 - ORA-600 [25025] [65536] DURING PQ EXECUTION
8242410 - EXADATA : HPI : ASM TEST : ORA- 600 [KCFIS_PUSH_DISKFD_MISMA
8250643 - EXCHANGE DOES NOT EXCHANGE DBMS_STAT STATISTICS FOR TABLE WI
8251486 - BUFFER SORT APPEARS FOR PARALLEL DML INCLUDING A SEQUENCE
8257122 - KCFIS SESSION CACHING FOR INDEX FAST FULL SCAN IS NOT FUNCTI
8301559 - SMART SCAN MAY DEGRADE PERFORMANCE IN CASE NON-OFFLOADABLE O
8324760 - EXADATA: OLTP TEST RAISES ORA-00600 [KCFIS_READ:PENDING_CWRI
8367827 - ORA-600 [KCFIS_TRANSLATE_MISMATCH0], [10]
8369094 - INCORRECT BUFFER SIZE AND ALIGNMENT FOR RMAN BACKUPS
8433270 - INTERNAL ERROR WHEN EXECUTING PQ USING BLOOM FILTER IF UNBALANCED SLAVE GROUPS
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 8833297 - 11.1.0.7.1 Patch Set Update Release 11.1.0.7.1 for UNIX
Copyright © 2006, 2009, 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.