Critical Patch Update Note
Release 11.1.0.7 for UNIX
Released: July 19, 2011
This document is accurate at the time of release. For changes, terminal Critical Patch Update plans, and additional information regarding CPUJul2011, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
Note 1323616.1 Patch Set Update and Critical Patch Update July 2011 Availability Document
Note 1323599.1 Critical Patch Update July 2011 Oracle Database Known Issues
This document includes the following sections:
You should administer one Oracle product, one Oracle home at a time, for its particular Critical Patch Update July 2011 (CPUJul2011) patch. Each Oracle home will have its own requirements.
Refer to My Oracle Support Note 1323616.1 Patch Set Update and Critical Patch Update July 2011 Availability Document to determine the order of applying CPU patches.
Critical patch update (CPU) patches are cumulative, which means fixes from previous Oracle security alerts and critical patch updates are included. It is not required to have previous security patches applied before applying the CPUJul2011 patches. However, you must be on the stated patch set level for a given product home before applying the CPUJul2011 patches for that release.
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 |
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 |
CPUApr2011 for certain configurations. See My Oracle Support Note: 1313771.1 TCPS configurations pertaining to the April 2011 CPU and PSU Patches for further information. CPUJul2009 for all other configurations. |
|
CRS (Cluster Ready Services) homes |
None |
Components patched by this Critical Patch Update:
Oracle Database
Oracle Database Vault
Oracle Net Services
Oracle OLAP
This section includes the following sections:
Section 3.2, "Patch Installation Instructions for Oracle Database Release 11.1.0.7"
Section 3.3, "Patch Deinstallation Instructions for Oracle Database Release 11.1.0.7"
You must use the OPatch utility version 11.1.0.6.2 or later to apply this patch. Oracle recommends that you use the latest released OPatch 11.1, which is available for download from My Oracle Support patch 6880880 by selecting the 11.1.0.0.0 release.
For information about OPatch documentation, including any known issues, see My Oracle Support Note 293369.1 OPatch documentation list.
N-apply CPUs are cumulative patches. For further information, refer to My Oracle Support Note 438314.1 Critical Patch Update - Introduction to Database n-Apply CPU Patches.
An n-apply CPU patch consists of groups of security fixes, where each group is called a molecule. Each molecule is an independent patch and does not conflict with any of the other molecule patches within the CPU. Prior to the patch installation, the following checks are performed for each molecule patch being installed:
Conflicts with other patches
Subset patches (patch to be installed is a subset of an existing patch in the Oracle Home)
Duplicates (patch to be installed is the same as an existing patch in the Oracle Home)
If a conflict is found, the installation will stop and you will be notified to file a merge request for the conflicting patches. To assist you in determining the best course of action when conflicts are reported, refer to My Oracle Support Note 835682.1, which documents the mapping of molecules to security vulnerabilities.
Select one of the following options:
Option 1: Resolve patch conflicts and install CPU together
File an SR for the merge request indicating all patches that conflict with the CPU as reported by OPatch.
Install the merge patches when they become available.
Install the CPU patch.
Option 2: Perform a partial installation of the CPU and resolve the conflicts later
At the conclusion of the aborted installation, OPatch returns the necessary command to install all molecules that do not conflict with patches in the Oracle home. Run this command to perform a partial CPU installation.
File an SR for the merge request indicating all patches that conflict with the CPU as reported by OPatch.
Install the merge patches when they become available.
If a subset or duplicate is found, the patch installation will continue. The subset and duplicate patches will not be installed as they are already installed.
These instructions are for both non-RAC environments and RAC environments.
Follow these steps:
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 Note 278641.1.
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 CPU 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.
Ensure that the $PATH 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 as follows:
export PATH=$PATH:/usr/ccs/bin
Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
unzip p12419265_111070_<platform>.zip
cd 12419265
opatch napply -skip_subset -skip_duplicate
Should OPatch return conflicts or subsets, refer to Section 3.1.1, "n-Apply CPUs and Patch Conflict Checking" for additional options.
If there are errors, refer to Section 4, "Known Issues".
Do not perform the operations in this section on ASM instances. However, if you shut down ASM as part of applying the CPU, 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 3.2.2.1.
Recompile views in the database, if necessary, as explained in Section 3.2.2.2.
The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.
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 cpu apply SQL> QUIT
The catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series CPU.
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_CPU_<database SID>_APPLY_<TIMESTAMP>.log catbundle_CPU_<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".
You may skip this section if you have recompiled views for this database during the installation of a previous CPU or if the database was created with Release 11.1.0.6 or later.
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 CPU installation. If you do this, your system will continue to work; however, the CPU 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 CPU 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 / as sysdba
SQL> STARTUP NOMOUNT
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
SQL> SHUTDOWN
SQL> STARTUP UPGRADE
SQL> @view_recompile_jan2008cpu.sql
Set the CLUSTER_DATABASE initialization parameter to TRUE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
SQL> EXIT
Restart the database:
$ sqlplus / as sysdba
SQL> SHUTDOWN
SQL> EXIT
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;
The setting of RECYCLEBIN is changed during the preceding steps due to bug 9768907; therefore, see My Oracle Support Note 9768907.8 STARTUP UPGRADE turns off RECYCLEBIN with SPFILE for details and workaround instructions.
These instructions are for a database that is created or upgraded after the installation of CPUJul2011.
You must execute the steps in Section 3.2.2.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 3.2.2.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 3.3.1, "Patch Deinstallation Instructions for a Non-RAC Environment"
Section 3.3.2, "Post Deinstallation Instructions for a Non-RAC Environment"
Section 3.3.3, "Patch Deinstallation Instructions for a RAC Environment"
Section 3.3.4, "Post Deinstallation Instructions for a RAC Environment"
Follow these steps:
Verify that an $ORACLE_HOME/rdbms/admin/catbundle_CPU_<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.2.2.1, "Loading Modified SQL Files into the Database" against the database before deinstalling the CPU.
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 using the specified rollback argument to rollback all molecule patches included in CPUJul2011. If a molecule is not installed in the Oracle Home, the rollback will ignore it. If a molecule is installed as part of a merge patch, it will not be rolled back. If it is desired to rollback merge patches that have been applied to your Oracle Home, the rollback needs to be issued separately.
opatch nrollback -idFile $ORACLE_HOME/cpu/CPUJul2011/rollback_all.lst
If you have applied CPUJul2011 on top of a previous CPU, you may instead want to rollback only the molecule patches that are new in CPUJul2011. To do so, use the following command:
opatch nrollback -idFile $ORACLE_HOME/cpu/CPUJul2011/rollback_new.lst
You may also rollback individual molecules or a list of molecules, as needed. Refer to the OPatch documentation on the nrollback command.
For information on the content of molecules when doing a rollback of CPUJul2011, refer to My Oracle Support Note 1323607.1 "Critical Patch Update July 2011 Database Patch Security Vulnerability Molecule Mapping.
If there are errors, refer to Section 4, "Known Issues".
Follow these steps:
Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)
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_CPU_<database SID>_ROLLBACK.sql
SQL> QUIT
Check the log file for any errors. The log file is found in $ORACLE_HOME/cfgtoollogs/catbundle and is named catbundle_CPU_<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".
Follow these steps:
Shut down the instance on one node. (Shut down all RDBMS instances before any ASM instances.)
Shut down all nodeapps services on the node in step 1:
srvctl stop nodeapps -n <node-name>
Roll back the patch on the node in step 1.
Run the OPatch utility using the specified rollback argument to rollback all molecule patches included in CPUJul2011. If a molecule is not installed in the Oracle Home, the rollback will ignore it. If a molecule is installed as part of a merge patch, it will not be rolled back. If it is desired to rollback merge patches that have been applied to your Oracle Home, the rollback needs to be issued separately.
opatch nrollback -idFile $ORACLE_HOME/cpu/CPUJul2011/rollback_all.lst -local
If you have applied CPUJul2011 on top of a previous CPU, you may instead want to rollback only the molecule patches that are new in CPUJul2011. To do so, use the following command:
opatch nrollback -idFile $ORACLE_HOME/cpu/CPUJul2011/rollback_new.lst -local
You may also rollback individual molecules or a list of molecules, as needed. Refer to the OPatch documentation on the nrollback command.
If there are errors, refer to Section 4, "Known Issues".
Start all nodeapps services on the node in step 1:
srvctl start nodeapps -n <node-name>
Start the instance on the node in step 1.
Repeat steps 1-5 on all the remaining nodes in the cluster.
For information on the content of molecules when doing a rollback of CPUJul2011, refer to My Oracle Support Note 1323607.1 "Critical Patch Update July 2011 Database Patch Security Vulnerability Molecule Mapping.
Follow these steps:
Go to the node that you used for the instructions in Section 3.3.1, "Patch Deinstallation Instructions for a Non-RAC Environment".
Follow the same set of instructions listed in Section 3.3.2, "Post Deinstallation Instructions for a Non-RAC Environment".
Users can start and access all other instances as usual while you are executing the steps from this instance.
Restart all nodeapps services on all nodes, one at a time:
srvctl start nodeapps -n <node-name>
Restart instances on all nodes.
You do not need to run post-deinstallation steps on other nodes. (That is, perform steps 1 and 2 only on the node selected in step 1, and perform steps 3 and 4 only once.)
For information about OPatch issues, see My Oracle Support Note 293369.1 OPatch documentation list.
For issues documented after the release of this CPU, see My Oracle Support Note 1323616.1 Critical Patch Update July 2011 Oracle Database 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-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
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.
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.
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
This patch includes the following molecules:
8342506 - DB-11.1.0.7-MOLECULE-003-CPUAPR2009
8563941 - DB-11.1.0.7-MOLECULE-004-CPUJUL2009
8563942 - DB-11.1.0.7-MOLECULE-005-CPUJUL2009
8563943 - DB-11.1.0.7-MOLECULE-006-CPUJUL2009
8563944 - DB-11.1.0.7-MOLECULE-007-CPUJUL2009
8563946 - DB-11.1.0.7-MOLECULE-009-CPUJUL2009
8563947 - DB-11.1.0.7-MOLECULE-010-CPUJUL2009
8563948 - DB-11.1.0.7-MOLECULE-011-CPUJUL2009
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
9118620 - DB-11.1.0.7-MOLECULE-018-CPUJAN2010
9458811 - DB-11.1.0.7-MOLECULE-021-CPUAPR2010
9458814 - DB-11.1.0.7-MOLECULE-022-CPUAPR2010
9458816 - DB-11.1.0.7-MOLECULE-023-CPUAPR2010
9458819 - DB-11.1.0.7-MOLECULE-024-CPUAPR2010
9702142 - DB-11.1.0.7-MOLECULE-028-CPUJUL2010
9702143 - DB-11.1.0.7-MOLECULE-029-CPUJUL2010
10009173 - DB-11.1.0.7-MOLECULE-030-CPUOCT2010
10009222 - DB-11.1.0.7-MOLECULE-032-CPUOCT2010
10009229 - DB-11.1.0.7-MOLECULE-033-CPUOCT2010
10009241 - DB-11.1.0.7-MOLECULE-034-CPUOCT2010
10009246 - DB-11.1.0.7-MOLECULE-035-CPUOCT2010
10336518 - DB-11.1.0.7-MOLECULE-036-CPUJAN2011
10336525 - DB-11.1.0.7-MOLECULE-037-CPUJAN2011
10336548 - DB-11.1.0.7-MOLECULE-038-CPUJAN2011
10336560 - DB-11.1.0.7-MOLECULE-039-CPUJAN2011
10336565 - DB-11.1.0.7-MOLECULE-040-CPUJAN2011
10336577 - DB-11.1.0.7-MOLECULE-041-CPUJAN2011
10426994 - DB-11.1.0.7-MOLECULE-042-CPUJAN2011
11807271 - DB-11.1.0.7-MOLECULE-043-CPUAPR2011
11807283 - DB-11.1.0.7-MOLECULE-045-CPUAPR2011
11807293 - DB-11.1.0.7-MOLECULE-047-CPUAPR2011
11807297 - DB-11.1.0.7-MOLECULE-048-CPUAPR2011
11807302 - DB-11.1.0.7-MOLECULE-049-CPUAPR2011
11829892 - DB-11.1.0.7-MOLECULE-050-CPUAPR2011
11829897 - DB-11.1.0.7-MOLECULE-051-CPUAPR2011
12560374 - DB-11.1.0.7-MOLECULE-052-CPUJUL2011
12560385 - DB-11.1.0.7-MOLECULE-053-CPUJUL2011
12560386 - DB-11.1.0.7-MOLECULE-054-CPUJUL2011
12560390 - DB-11.1.0.7-MOLECULE-055-CPUJUL2011
12560393 - DB-11.1.0.7-MOLECULE-056-CPUJUL2011
12560398 - DB-11.1.0.7-MOLECULE-057-CPUJUL2011
12560400 - DB-11.1.0.7-MOLECULE-058-CPUJUL2011
12560402 - DB-11.1.0.7-MOLECULE-059-CPUJUL2011
12560404 - DB-11.1.0.7-MOLECULE-060-CPUJUL2011
12560405 - DB-11.1.0.7-MOLECULE-061-CPUJUL2011
12560459 - DB-11.1.0.7-MOLECULE-062-CPUJUL2011
12560461 - DB-11.1.0.7-MOLECULE-063-CPUJUL2011
12687462 - DB-11.1.0.7-MOLECULE-065-CPUJUL2011
The preceding molecules include the following non-security bug fix:
6870937 - ORA-600 [729] "UGA SPACE LEAK" ERROR RESULTS IN SESSION OUT
9744092 - EXCESSIVE AMOUNT OF AUD FILES BEING GENERATED IN 11.1
6805009 - ORA-07445 WHEN USING DBMS_JAVA.GRANT_PERMISSION WITH AUDIT_TRAIL=DB_EXTENDED
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.
Oracle Database Critical Patch Update Note Release 11.1.0.7 for UNIX
Copyright © 2006, 2011, 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.