Release Notes for Oracle Unified Directory
11g Release 2 (11.1.2.1)
E23738-10
January 2017
This document contains the release information for Oracle Unified Directory 11g Release 2 (11.1.2.1). It describes the difference between Oracle Unified Directory (OUD) and its documented functionality.
Oracle recommends you review its contents before installing or working with OUD.
This document is accurate at the time of publication. Oracle will update the Release Notes periodically after the software release. You can access the latest information and additions to these Release Notes on the Oracle Technology Network at:
http://docs.oracle.com/cd/E49437_01/relnotes.111220/e23738/toc.htm
These Release Notes include the following topics:
Before performing any installation, you should read the system requirements and certification documents to ensure that your environment meets the minimum installation requirements for the products you are installing. The following documents are available on Oracle Technology Network (OTN):
This document contains detailed information related to hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches when installing OUD with other Oracle products.
Oracle Fusion Middleware Supported System Configurations
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
This landing page contains links to certification information for all products in Fusion Middleware suite.
Oracle Unified Directory (OUD) 11gR1 (11.1.2.x) Certification Matrix
This document contains the most detailed information about supported application servers, supported clients, JDK requirements, and IPv4/IPv6 certifications for installing OUD. This document is updated when new information becomes available.
To access this document, on the Oracle Fusion Middleware Supported System Configurations landing page, follow the link to "System Requirements and Supported Platforms for Oracle Unified Directory 11gR1."
Oracle® Fusion Middleware Installation Guide for Oracle Unified Directory 11g Release 2 (11.1.2)
Chapter 1, "Before You Install Oracle Unified Directory" contains pre-installation system notes and other information you should review prior to OUD installation.
The following sections describe additional information specific to OUD installation requirements:
As a general guideline, the following hardware is recommended:
| Hardware Component | Requirement |
|---|---|
|
RAM |
Evaluation purposes: At least 256 MB of free memory for a small database. Production: Minimum of 2 GB. |
|
Local disk space |
Evaluation purposes: For a small database and sufficient space for log files, your system should have at least 100 MB of free local disk space. Preferably, you should have at least 1 GB of disk space. Production: For a typical production deployment with a maximum of 250,000 entries and no binary attributes, such as images, 4 GB of disk space might be sufficient for the database only. You might need an additional 1 GB of disk space for log files. You need to determine disk space for the change log database (DB), which is dependent on the load (updates per second) and on the replication purge delay (that is, the time the server should keep information about internal updates). The change log DB can grow up to 30-40 GB with loads of 1,000 modifications per second. When you use global index replication, ensure that you have enough disk space for the replication change logs. By default, the change log stores changes from the last 100 hours. The configuration should be based on the expected size of the service. For example, you would need 150 GB for 5,000 modify/seconds. While the directory server can be used with databases and logs installed on NFS-mounted file systems, related files must not be accessed at same time from different systems. Sufficient space should be provided for the database. |
For optimal performance, your system must have sufficient RAM memory for the JVM heap and database cache. For more information about setting the JVM heap and database cache, see "Configuring the JVM, Java Options, and Database Cache" in Oracle Fusion Middleware Installation Guide for Oracle Unified Directory.
Your system should also have enough disk space to store the generated log files. The server log files can consume up to 1 GB of disk space with default server settings. In replicated environments, the change log database can grow up to 30-40 GB with loads of 1,000 mods/sec. For information about setting the log file size, see "Configuring Log Rotation Policies" in Oracle Fusion Middleware Administrator's Guide for Oracle Unified Directory.
You can configure Oracle Unified Directory in such a way that it uses substantially less, or more, disk space depending on your application and performance needs. Any setup considerations must determine the amount of memory for the server's database and log files.
On Solaris systems, the operating system should be configured to have at least twice as much virtual memory as JVM heap. To achieve this, you might need to increase the size of the operating system swap space.
In addition to the operating system, application server, and JDK requirements described in this document:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
be sure to resolve the following OS-specific requirements:
Section 1.2.1, "File Descriptor Requirements (Linux Systems)"
Section 1.2.2, "Specific Requirements for Installation in Solaris Zones"
The issue described in this section affects Linux systems only. All other supported platforms are unaffected.
To ensure optimal server performance, the total number of client connections, database files, and log files must not exceed the maximum file descriptor limit on the operating system (ulimit -n). By default, the directory server allows an unlimited number of connections but is restricted by the file descriptor limit on the operating system. Linux systems limit the number of file descriptors that any one process may open to 1024 per process.
After the directory server has exceeded the file descriptor limit of 1024 per process, any new process and worker threads will be blocked. For example, if the directory server attempts to open a Oracle Berkeley JE database file when the operating system has exceeded the file descriptor limit, the directory server will no longer be able to open a connection that can lead to a corrupted database exception. Likewise, if you have a directory server that exceeds the file descriptor limit set by the operating system, the directory server can become unresponsive as the LDAP connection handler consumes all of the CPU's processing in attempting to open a new connection.
To fix this condition, set the maximum file descriptor limit to 65535 per process on Linux machines.
To view the maximum file descriptor limit, run the following command:
/sbin/sysctl -a | grep file-max
If the file-max value is lower than 65535, then perform the following steps:
Using any text editor, create or edit the /etc/sysctl.conf file, and add or edit lines similar to the following:
fs.file-max = 65536
Enter the following command to change the current values of the kernel parameters:
/sbin/sysctl -p
Enter the command /sbin/sysctl -a | grep file-max to confirm that the values are set correctly.
Using any text editor, edit the /etc/security/limits.conf file, and add the following lines:
soft nofile 1024 hard nofile 65535
Note:
When you specify the values in the/etc/sysctl.conf or /etc/security/limits.conf file, they persist when you restart the system.The Oracle Unified Directory software treats global, full local, and sparse zones as an independent physical system. Installing the server in any type of Solaris zone is therefore like installing on an independent system. The software does not share services or file locations with other zones.
Oracle Unified Directory 11g Release 2 (11.1.2.1) is certified for the following languages:
Chinese (Simplified)
Chinese (Traditional)
French
German
Italian
Japanese
Korean
Spanish
Portuguese (Brazilian)
Note:
Certain error messages (specifically, the SEVERE and FATAL messages) are displayed in English only.The Oracle Unified Directory 11g Release 2 (11.1.2.1) software has some limitations that might affect the initial deployment of your directory server. Follow the recommendations for deployments in this section.
Administrators also should appropriately tune the Oracle Unified Directory directory server and its Java Virtual Machine (JVM) to ensure that adequately sized hardware is made available to support heavy write operations. For more information, see "Configuring the JVM, Java Options, and Database Cache" in Oracle Fusion Middleware Installation Guide for Oracle Unified Directory.
This section describes the following topics:
Section 2.1, "Oracle Unified Directory 11g Release 2 (11.1.2.1) Limitations"
Section 2.2, "Oracle Unified Directory Software Recommendations"
This section lists the limitations of Oracle Unified Directory 11g Release 2 (11.1.2.1). They are as follows:
The Oracle Unified Directory directory server provides full LDAP v3 support, except for alias dereferencing, and limited support for LDAPv2.
Oracle Unified Directory when setup for Enterprise User Security is currently validated for proxy for the following directory servers:
Sun Java System Directory Server Enterprise Edition 6.3
Microsoft Active Directory 2008 R2 and Active Directory 2012
Novell eDirectory 8.8
Oracle Unified Directory 11g Release 2
The proxy server provides the best search performance when the search queries ask for the specific required attributes (rather than all the attributes) of an entry.
This section lists the recommendations for using Oracle Unified Directory 11g Release 2 (11.1.2.1). They are as follows:
The directory server provides better performance when the database files are cached entirely into memory.
The default settings of the Oracle Unified Directory directory server are targeted initially at evaluators or developers who are running equipment with a limited amount of resources. For this reason, you should tune the Java virtual machine (JVM) and the directory server itself to improve scalability and performance, particularly for write operations. For more information, see "Configuring the JVM, Java Options, and Database Cache" in Oracle Fusion Middleware Installation Guide for Oracle Unified Directory.
If you want to import large LDIF files by using the import-ldif command, then it is recommended that you use the --skipDNvalidation option. However, if you are not certain that the LDIF file is valid, using this option is not advised.
The following sections describe known issues and limitations with the Oracle Unified Directory 11g Release 2 (11.1.2.1) core server at the time of this release.
When you setup Oracle Enterprise User Security with Oracle Unified Directory configured as a proxy, the Oracle Enterprise User Security context does not get installed.
The workaround is to apply a patch that addresses Bug 16529038 (Setup of EUS with OUD as a proxy does not install the EUS context). A patch for the current release is available as Patch ARU 16424146 (merge request on top of 11.1.1.2.1 for Bug 16529038). This patch can be downloaded from My Oracle Support.
You must perform the following steps for each new EUS suffix that was setup before applying the patch:
Create a copy of file of eusData.ldif file. You can obtain the file from the following location:
OUD_INSTALL_ROOT/OracleUnifiedDirectory/config/EUS/eusData.ldif
Edit the copy of eusData.ldif file as follows:
Replace all the occurrences (27) of 'dc=example,dc=com' with the DN of the EUS suffix.
Replace all the occurrences (6) of 'cn=orcladmin' with the Root User DN that you had provided in the setup.
Import the contents of the edited file in Step 2 using the import-ldif command as follows:
<OUD_INSTANCE_ROOT>/OUD/bin/import-ldif -n oraclecontext<SUFFIX_NUMBER> -l \ <PATH_OF_THE_EDITED_FILE> -F --hostname <OUD_HOST_NAME> \ --port <OUD_ADMINISTRATION_PORT> --bindDN <OUD_ROOT_USER_DN> \ --bindPasswordFile <PATH_OF_FILE_WITH_OUD_ROOT_USER_PASSWORD> \
After upgrading to 11g Release 2 PS1 (11.1.2.1.0) release, a warning about duplicate object class for configuration entries related to indexes ds-sync-hist and objectClass might be logged.
This warning might appear as output when you start the server or in the server.out log file.
You can safely ignore this warning as it has no impact on the server behavior.
Entry cache might not be correctly updated.
Disable the entry cache, running the following command:
dsconfig set-entry-cache-prop \ --cache-name FIFO \ --set enabled:false\ --port ADMIN_PORT \ --bindDN cn=Directory\ Manager \ --bindPassword ****** \ --no-prompt
After upgrading your directory service to the latest version, you need to copy the following files manually from the installation directory to the instance directory:
For Windows:
bat/split-ldif.bat
bat/gicadm.bat
bat/gicdump.bat
bat/dps2oud.bat
For Unix:
bin/split-ldif
bin/gicadm
bin/gicdump
bin/dps2oud
There is currently no workaround for this issue.
On Windows, while upgrading when you provide an installation location that contains an existing Oracle Unified Directory instance, then the installer does not throw any warning that the existing Oracle Unified Directory instance will be overwritten.
There is currently no workaround for this issue, because this is an upgrade operation. Therefore, it is recommended that you ensure your objective is to upgrade the existing Oracle Unified Directory instance.
When you install an Oracle database version 11.1.6.0 while setting up the Enterprise User Security (EUS) configuration, you might encounter the message "ORA-28030 Server encountered problems accessing LDAP directory service."
Launch Oracle Wallet Manager, and open the wallet which is by default stored under:
$ ORACLE_BASE/admin/<SID>/ wallet
Provide the password for wallet which was given while registering using DBCA.
Select the auto-login check box from the wallet manager File > Auto-login menu.
Save the wallet again to create the cwallet.sso.
The server does not start after an upgrade on Microsoft Windows.
The workaround for this issue is to manually copy the INSTALL_DIR\bat\start-ds.bat file into the instance that needs to be upgraded.
You can then run the start-ds.bat --upgrade command, and finally the start-ds.bat command to start the server.
In a replicated topology, the dsreplication status command displays incorrect port and information when you stop a replicated server.
There is currently no workaround for this issue.
AddOutboundTransformation definition contains a dot, then a search request might fail.When you configure an AddOutboundTransformation with virtualAttr={%sn%.%cn%@o.com}where the definition contains a dot, then a search request with a filter on the virtualAttr parameter might not work correctly.
For instance, the sn and cn backend attribute values contain a dot, such as "sn:sn.light" and "cn:cn.light." Here, a search request with a filter on the virtualAttr, for example "virtualAttr=sn.light.cn.light@o.com" might not work correctly.
There is currently no workaround for this issue.
AddOutboundTransformation.If you omit the curly brackets {} while configuring the client-attribute value for an AddOutboundTransformation, for instance client-attribute:"cn=%sn%.%cn%" instead of "cn={%sn%.%cn%}" then the dsconfig command does not throw any warning. However, the transformation does not work correctly.
Be sure to use curly brackets {} while configuring the client-attribute value for AddOutboundTransformation.
addoutboundattr transformation, the ldapcompare command might erroneously return FALSE.When you use the addoutboundattr transformation, for instance cn=%sn% with conflict behavior set to Merge-real-and-virtual, then the ldapcompare command might erroneously return FALSE, because comparison is done only on sn values and not on cn values.
There is currently no workaround for this issue.
gicadm command should check server versionThe gicadm command is not compatible with earlier Oracle Unified Directory versions.
There is currently no workaround for this issue.
When you export data using JDK1.7.0_05 or higher the server is stopped.
The issue arises, because of an issue with JDK1.7. Until this is solved in an upcoming JDK1.7 release the workaround is to use the following option:
-XX:-OptimizeStringConcat
The following error may be written to the log files when running Java 6 Update 32 or later in a Windows environment:
category=JEB severity=SEVERE_WARNING msgID=8519808 msg=An error occurred while setting file permissions for the backend database directory C:\OUD\db\userRoot: org.opends.server.types.DirectoryException: One or more updates to the file permissions for C:\OUD\db\userRoot failed, but at least one update was successful. Some of the permissions for the file may have been altered.
When running Java 6 or later in a Windows environment you should use Windows' native security tools to assign access control on any folders containing sensitive information after the Oracle Unified Directory install is complete.
Access permissions in Windows are inherited, you should assign access control restrictions to the top-level Oracle Unified Directory folder, and ensure that all running Oracle Unified Directory processes are granted full access to that folder.
moveplan interface does not have a field to update the path for keystore pin file.The moveplan interface does not have a field to update the path for keystore pin file during the cloning process.
Use the dsconfig command on the cloned instance to update the key-store-pin-file value of JKS Key Manager Provider while cloning.
Oracle Unified Directory does not support translation of both messages and Help for oudCopyConfig, oudExtractMovePlan, and oudPasteConfig commands.
There is currently no workaround for this issue.
-j, --rootUserPasswordFile is provided as a relative path, commands fail.On Windows system, if the value for parameter -j, --rootUserPasswordFile is provided as a relative path, then oud-setup, oud-proxy-setup, and oud-replication-gateway-setup commands fail.
Provide an absolute path for -j, --rootUserPasswordFile parameter.
For example:
-j C:\local\Password.txt
gicadm command does not import a catalog.The gicadm command does not import a catalog when you specify a relative path.
Specify an absolute path to import a catalog.
The -tih, -targetInstanceHomeLoc option of the oudPasteConfig command allows you to specify the location of the cloned server instance. If you specify an alternative location, for the cloned server instance, the instance is still created in the default location (TARGET_ORACLE_HOME/../TARGET_INSTANCE_NAME) and no error message is generated. However, the cloned server is configured partially as some custom parameters are not updated in the cloned server instance.
To successfully clone the server instance, as the -tih parameter is mandatory, you must explicitly provide the default location for the -tih parameter as follows:
-tih TARGET_ORACLE_HOME/../TARGET_INSTANCE_NAME
ldapsearch.bat client incorrectly handles a trailing asterisk character.On a Windows system with a JDK 1.7 (previous to Update 11) JVM instance running, the ldapsearch.bat client might not handle the trailing "*" correctly.
Download the latest JDK version to leverage the fixes and updates that are added to the Java SE platform.
The error log may contain servere_warning while setting the file permissions on Microsoft Windows using Java 7.
The workaround for this issue is to apply access-control restrictions from the top-level folder of any Oracle Unified Directory instance. In addition any Oracle Unified Directory process running on Microsoft Windows should be granted FULL access to the selected folder.
This issue does not appear in Java 7, because Oracle Unified Directory uses Java 7 File APIs to set permissions.
runInstaller command is executed on SuSE Linux Enterprise Server 11.When you run the Oracle Unified Directory installer using the runInstaller command on SuSE Linux Enterprise Server 11, the prerequisite checks are not executed and an error is generated.
Use the -ignoreSysPrereqs flag while running the runInstaller command.
rebuild-index decreases as the IDs become unordered.The performance of the rebuild-index command decreases as the database IDs become unordered over time.
If possible, avoid reindexing large databases or import the database again. For more information, see rebuild-index in Oracle Fusion Middleware Administrator's Guide for Oracle Unified Directory.
stop-ds command with no credentials.On Windows systems no SNMP trap is sent if the server is stopped by using stop-ds with no credentials. The server is, however, stopped correctly.
The SNMP trap is sent if the server is stopped by using stop-ds -D bindDN -p password.
There is currently no workaround for this issue.
When a distribution is using a GIC, and the GIC indexes the entry DNs, the ModifyDN operation is not supported.
If DNs are not indexed in the global index catalog, the modify DN operation is supported. Otherwise, only the modify RDN operation is supported.
Although indexing the DN is recommended for performance reasons, as a workaround in this situation, do not index the DN.
If you delete the load balancing workflow element or the load balancing algorithm, the load balancing routes are also deleted without any warning.
There is currently no workaround for this issue.
Under heavy and sustained load the database cleaning process does not end.
Configure a larger database cache. For more information, see "Tuning the Server Configuration" in Oracle Fusion Middleware Administrator's Guide for Oracle Unified Directory.
On Windows system, if the path to your Java installation in the -jreLoc option includes a space character, then the installer does not run appropriately and terminates.
Provide the path to your Java installation in DOS 8.3 format.
For example:
-jreloc C:\Progra~1\Java\jdk1.6.0_21
For more information, see "Installing Oracle Unified Directory" in Oracle Fusion Middleware Installation Guide for Oracle Unified Directory.
If DN or attribute values of returned entries contain non-ASCII characters, the DN or values are displayed base64-encoded.
There is currently no workaround for this issue.
In a replicated topology, if the server has a heavy workload, then the following error message is recorded in the error log: "The server failed to obtain a read lock on the parent entry dc=example, dc=com after multiple attempts."
Configure a larger database cache. For more information, see "Tuning the Server Configuration" in Oracle Fusion Middleware Administrator's Guide for Oracle Unified Directory.
oud-setup command fails when appropriate file permissions are not set.When you run the oud-setup command and set the INSTANCE_NAME variable to a path for which you do not have the appropriate file permissions, the command fails.
Set the required file permissions for the path to which INSTANCE_NAME variable points.
The following sections describe known issues with Oracle Directory Services Manager at the time of Oracle Unified Directory 11g Release 2 (11.1.2.1) release.
Microsoft Internet Explorer 7 does not render some Web pages of Oracle Directory Services Manager properly. It does not lead to any loss of functionality, but some Web pages display with unnecessary scroll bars or wrapped field names.
Upgrade the browser to Microsoft Internet Explorer 8 or Microsoft Internet Explorer 9. While using Microsoft Internet Explorer 8 or Microsoft Internet Explorer 9, you need to disable the compatibility view mode in the browser. For more information about how to disable the compatibility view mode in the browser, refer to the following Web page: http://support.microsoft.com/kb/956197
When you are in the screenreader mode, the Create, Apply, and Cancel buttons in the Oracle Directory Services Manager interface does not get focus after modification.
The workaround is to press the Tab key till you get the focus on the required button. Alternatively, you can use the mouse to activate the required button.
When this NullPointer exception is encountered, the contents of that particular changelog entry cannot be accessed from ODSM. You can continue to use ODSM to perform other tasks and access other entries.
To access a changelog entry with no objectclasse specified, use a different LDAP client.
Objectclass is clicked.When you click any item of type Objectclass on the Schema tab in Microsoft Internet Explorer, then the browser hangs and does not respond.
You might observe the same behavior for Content Rules in the Schema tab and Virtual Attributes in the Configuration tab.
The workaround is to apply a patch that addresses Bug 13417997 (v1 non_edg:script on the pg is causing ie to run slowly' err running qtp scripts). A patch for the current release is available as Patch 16478722 (merge request on top of 11.1.1.6.0 for Bugs 16011916 and 13417997). This patch can be downloaded from My Oracle Support.
On the Advanced Search page, when you click an entry in the Search Results table, the Show Attributes button does not appear if Optional Attributes is already expanded. However, if you collapse Optional Attibutes and then expand, the Show Attributes button appears. But, when you click the button the Select Attributes dialog box is blank.
To view the entry details, you can select the same entry from Data Browser tab.
On the Advanced Search page, from the Fetched Attributes list when you select Pick Attributes and click Search, then the entries are displayed in the Search Results table as expected. If you select an entry all the information is displayed correctly in the next page. However, if you click Refresh, then all the Mandatory Attributes values and Optional Attributes values disappear.
There is currently no workaround available for this issue.
On the Advanced Search page, from the Fetched Attributes list when you select Pick Attributes then the Object Class and Common Name(cn) columns are blank when you click Next to go to the second page.
There is currently no workaround available for this issue.
was_config is used on IBM WebSphereWhen you deploy Oracle Directory Services Manager on IBM WebSphere using the was_config script, then the deployed application does not have the shared library references.
The workaround is to add the missing shared library references, adf.oracle.domain and oracle.jsp.next in Oracle Directory Services Manager manually using the IBM WebSphere Administrative console. Perform the following steps:
Log in to the IBM WebSphere Administrative Console using the following URL:
http://HOSTNAME:PORT/ibm/console
Here, PORT is port number for the WebSphere administrative HTTP transport (WC_ adminhost). The default value is 9060.
In the console navigation tree, expand Applications, and then Application Types and then click WebSphere enterprise applications to open the list of applications.
In the Enterprise Applications page, click the application that needs to refer to the shared library.
In this scenario, select odsm_11.1.2.1.0.
Under Configurations, click Shared library references.
Note: The Shared Libraries column is empty for the Application odsm_11.1.2.1.0.
In the Shared Library Mapping for Modules section, select the check box for odsm_11.1.2.1.0 application, and then click the Reference shared libraries button above the table.
Select the following shared library from the Available list and move it to the Selected list:
adf.oracle.domain_1.0_11.1.1.2.0
oracle.jsp.next_11.1.1_11.1.1
Click OK.
Verify the Shared Libraries column for the row Application odsm_11.1.2.1.0 in the table.
Click OK.
On the Configuration main page, click Save to commit the changes.
Click OK.
Perform the following steps to restart the application that references the shared library:
Select the check box for odsm_11.1.2.1.0 application.
Click Stop.
Select the check box for odsm_11.1.2.1.0 application.
Click Start.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle® Fusion Middleware Release Notes for Oracle Unified Directory, 11g Release 2 (11.1.2.1)
E23738-10
Copyright © 2016, 2017, 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, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
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 of The Open Group.
This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.