Release 2.5.5
E27168-05
 Home |  Contents |  Contact Us |
Go to main content
| Oracle® Database Appliance Oracle Database Appliance Setup HTML Release 2.5.5 E27168-05 |
|
Oracle Database Appliance Setup HTML
Release 2.5.5
E27168-05
April 2013
This document provides an HTML text description for Oracle Database Appliance Setup Poster, part number E35554.
This document consists of the following topics:
Page One: Cabling the Interconnect and Storage for Oracle Database Appliance X3-2
Page Two: Preparing to Deploy Oracle Database Appliance X3-2
Page Four: Oracle Database Appliance X3-2 Virtualized Platform Setup
The Oracle Database Appliance setup and configuration poster document is a four-page PDF in Tabloid size format (11 x 17) with the page number at the bottom left corner of each page. Each page shows Oracle Database Appliance configuration tasks. The upper right corner on pages 2, 3, and 4 of the poster contains a quick response (QR) code to link to the documentation, and URL addresses for the documentation are located at the bottom of page 4 of the poster.
This document provides a text equivalent for that poster that can be read with assistive technology tools. There is a separate section for each page of the poster. Each section title contains the related poster page title and the section content is an alternate text description of the page content.
Page 1, "Cabling the Interconnect and Storage for Oracle Database Appliance X3-2," describes how to connect each server node to the storage shelf and storage expansion shelf, and how to connect the interfaces of each cluster node for the interconnect network. The poster consists of two images of the Oracle Database Appliance and three tables describing the cabling.
The image at the top left of the page shows the back of Oracle Database Appliance with its two nodes (node 1 on top and node 0 below it) and a storage shelf underneath node 0. The storage shelf has two I/O modules that sit on top of each other between the power modules that are at either end of the shelf. By convention, the top module is known as I/O module (or controller) 1, and the bottom module is known as I/O module (or controller) 0.
The image at the top right of the page includes the same configuration as the left-hand image, also shown from the back, but with a storage expansion shelf at the bottom of the stack of components. The storage expansion shelf also has two I/O modules, positioned and identified in the same way as the I/O modules for the storage shelf.
Both images include lines that represent the cables to be installed. All these cables start from one of the sockets that are arranged in pairs along the top of the back panel on the server nodes. (There is a second row of sockets on each node, but these are not required for the cabling shown on this page.) Each pair of sockets is identified with a numbered label and the text "PCIe3" under the number. The numbers, from left to right, are 1, 2, and 3. There are four SAS cables shown in the left-hand image and they terminate in sockets in the storage shelf. There are also two CAT-6 cables in the left-hand image, and they run between the two nodes. In the right-hand image, there are four more SAS cables that connect the server nodes to the storage expansion shelf.
The lines are identified with callout numbers so that they can be identified in the tables that describe where they are connected. For convenience, the lines are colored to match the colors of the labels used on the sockets where they are to be attached. These same colors are also used on the cables that you receive with Oracle Database Appliance so that, if you wish, you can match the cable with the images on the poster. However, this again for convenience: the four SAS cables are identical and can be used for any of connections described on this page. Similarly, you can use either of the colored CAT-6 cables when making the connections shown by callouts 5 and 6.
The detailed cabling instructions in the tables on this page use both the callout number and the color to identify a cable. In each table, there are three columns:
Column 1 contains the callout number and color of the cable and socket labels
Column 2 identifies the component and socket label at the start of the cable
Column 3 identifies the component and socket label at the end of cable
The text description of the tables is provided in the following sections, each of which has the same title as the related table.
The table describes the locations for the start and end of each SAS cable that connects Oracle Database Appliance server nodes to the storage shelf. There is one row in the table for each of the four SAS cables shown in the left-hand image on this page.
Row 1 is for the dark blue SAS cable identified by callout 1. The cable starts from node 0 and is plugged into the SAS0 socket of the number 2 PCIe3 pair, and the cable ends on I/O module 1 and is plugged into port 0.
Row 2 is for the light blue SAS cable identified by callout 2. The cable starts from node 0 and is plugged into the SAS1 socket of the number 3 PCIe3 pair, and the cable ends on I/O module 0 and is plugged into port 0.
Row 3 is for the dark red SAS cable identified by callout 3. The cable starts from node 1 and is plugged into the SAS1 socket of the number 2 PCIe3 pair, and the cable ends on I/O module 1 and is plugged into port 1.
Row 4 is for the light red SAS cable identified by callout 4. The cable starts from node 1 and is plugged into the SAS0 socket of the number 3 PCIe3 pair, and the cable ends on I/O module 0 and is plugged into port 1.
The table describes the locations for the start and end of each CAT-6 cable that provide the cluster interconnect for the two server nodes in Oracle Database Appliance.
Row 1 is for the green CAT-6 cable identified by callout 5. The cable starts from node 1 and is plugged into the NET0 socket of the number 1 PCIe3 pair, and the cable ends on node 0 and is plugged into the NET0 socket of the number 1 PCIe3 pair.
Row 2 is for the yellow CAT-6 cable identified by callout 6. The cable starts from node 1 and is plugged into the NET1 socket of the number 1 PCIe3 pair, and the cable ends on node 0 and is plugged into the NET1 socket of the number 1 PCIe3 pair.
The table describes the locations for the start and end of each SAS cable that connects Oracle Database Appliance server nodes to the storage expansion shelf. There is one row in the table for each of the four SAS cables shown in the right-hand image on this page.
Row 1 is for the dark blue SAS cable identified by callout 7. The cable starts from node 1 and is plugged into the SAS0 socket of the number 2 PCIe3 pair, and the cable ends on I/O module 1 of the storage expansion shelf and is plugged into port 0.
Row 2 is for the light blue SAS cable identified by callout 8. The cable starts from node 1 and is plugged into the SAS1 socket of the number 3 PCIe3 pair, and the cable ends on I/O module 0 of the storage expansion shelf and is plugged into port 0.
Row 3 is for the dark red SAS cable identified by callout 9. The cable starts from node 0 and is plugged into the SAS1 socket of the number 2 PCIe3 pair, and the cable ends on I/O module 1 of the storage expansion shelf and is plugged into port 1.
Row 4 is for the light red SAS cable identified by callout 10. The cable starts from node 0 and is plugged into the SAS0 socket of the number 3 PCIe3 pair, and the cable ends on I/O module 0 of the storage expansion shelf and is plugged into port 1.
The poster "Preparing to Deploy Oracle Database Appliance X3-2" consists of seven panels that describe basic hardware configuration and planning steps for Oracle Database Appliance, and one panel providing URL addresses for the documentation. There is also a a quick response (QR) code to link to documentation in the upper right corner of the poster. The following is a text description of each panel.
a) Ensure that the system hardware is set up and mounted properly as specified in Oracle Database Appliance Owner's Guide, which is available from the following URL:
http://www.oracle.com/pls/topic/lookup?ctx=dba21
b) Verify that your shipment contains the correct power cables for your location.
c) Verify that at least two Cat-6 cables are available to support the initial public network configuration. The public network cables are not included in the Oracle Database Appliance shipment
d) Obtain your hardware Support Identifier (SI) from your hardware vendor.
e) Add the hardware SI and new software licenses that you received with Oracle Database Appliance to your My Oracle Support profile. Each SI registration may take up to 24 hours.
Note:
You cannot obtain software or support from Oracle without registered hardware and software SIs.a) Collect the following network and cluster information from your network administrator:
Generic network information
Domain name (for example, example.com)
Domain name server addresses
(Optional) Network Time Protocol server addresses
Cluster network information
Single Client Access Name (SCAN) and two addresses (for example, hrsys-scan and 192.0.2.16, 192.0.2.17)
Netmask for the public network (for example, 255.255.252.0)
Gateway for the public network (for example, 192.0.2.1)
b) Collect the following cluster node information from your network administrator:
Node 0 network information
Public name and address (for example, hrsys0 and 192.0.2.18)
VIP name and address (for example, hrsys0-vip and 192.0.2.19)
Node 1 network information
Public name and address (for example, hrsys1 and 192.0.2.20)
VIP name and address (for example, hrsys1-vip and 192.0.2.21)
Note:
Public, VIP, and SCAN IP addresses must be on the same subnet.For virtualization, your network administrator must provide extra IP addresses for dom0, dom1, and virtual machines.
Configure Oracle Integrated Lights Out Manager (Oracle ILOM) for managing Oracle Database Appliance independently of the operating system.
Collect the following information for your Oracle ILOM network:
Oracle ILOM name and address for node 0 (for example, hrsysilom and 10.0.0.3)
Oracle ILOM name and address for node 1 (for example, hrsysilom and 10.0.0.4)
Netmask for management network (for example, 255.255.255.0)
Gateway for management network (for example, 10.0.0.1)
a) Plan your software installation choices as follows:
Configuration type: Custom
System name (for example, hrsys)
Region (for example, America)
Time zone (for example, America/Los_Angeles)
Deployment type (for example, Oracle Real Application Clusters)
Disk group redundancy: High (triple-mirrored) or Normal (double-mirrored)
Database backup (for example, External). Local appliance internal backups utilize 60% of available disk space for archive logs and backup, and external backups utilize 20% of available disk space for archive logs.
b) Prepare to enter information for the following fields:
Database Name (for example, hrdb)
DB Class (for example, Small)
Database Language (for example, English)
Database Block Size (for example, 8192)
Database Character Set (for example, AL32UTF8)
Database Territory (for example, America)
a) To configure Oracle Auto Service Request (Oracle ASR), be prepared to provide the following (Optional):
Proxy server name to use for your deployment
Proxy server port
Proxy username
Proxy password
Oracle online account username
Oracle online account password
b) Configure External Oracle ASR Manager (Optional)
Oracle ASR Manager IP/host name
Oracle ASR Manager port
Your My Oracle Support account user name and password
For more information about Oracle ASR see:
http://www.oracle.com/technetwork/systems/asr/overview/index.html
c) To change the default name and size of Oracle Cloud File System, be prepared to provide the following:
Name of file system (default name is /cloudfs)
Size of file system (default size is 50 GB)
Use one of the following two options to download the software:
A) (Recommended) Download Oracle Appliance Manager Configurator
Download the Configurator at the following URL:
Run the configurator, preferably on a computer that is on a network that is local to where you plan to install Oracle Database Appliance.
Enter and validate your configuration choices with the configurator. This creates a configuration file that you can use during actual deployment. You can also run Oracle Appliance Manger Configurator directly from Oracle Database Appliance during deployment.
B) Follow the instructions in My Oracle Support Note 888888.1
Go to My Oracle Support note 888888.1 using the following URL:
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=888888.1
Download the latest software (Oracle Database Appliance Bundle) to a local computer on the network.
Download the latest available Oracle Database Appliance patch bundle, which you must apply before or after deployment, and review the README files.
Note:
For information about the configuration options such as Deployment Type, Database Class, or any of the other options, refer to Oracle Appliance Manager Configurator online help.Review the most recent version of this poster in the Oracle Database Appliance online documentation library, which is available at the following URL:
http://www.oracle.com/pls/topic/lookup?ctx=dba21
Review the Oracle Database Appliance FAQs and online demos on Oracle Technology Network, which is available at the following URL:
Review the Oracle Database Appliance Information Center, which is contained in My Oracle Support Note 1417713.2 and available at the following URL:
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1417713.2
Review the latest information about Oracle software and hardware products at the following URL:
Oracle Database Appliance Setup is a poster consisting of eight panels showing basic configuration steps for Oracle Database Appliance. There is a quick response (QR) code to link to documentation located in the upper right corner of the poster. The following is a text description of each panel.
The panel shows an image of the back of an Oracle Database Appliance X3-2 system. The back of the appliance consists of two nodes on the top half, and a storage shelf on the bottom half. The upper node is node 1, and the lower node is node 0. There are seven callouts labeled 1 through 4, pointing to locations on the appliance.
Callout 1 consists of a total of 4 separate lines pointing to power plug inlets. Three of them are on the left side. They point to power cord inlet areas on the left side of the system: four inlets for the server power (two for each server), and one for the storage array. One is on the right side, and points to a power plug inlet on the storage array. The text associated with these callouts says "Power to the power supply unit (PSU)."
Callout 2 is located in the center above the two servers. It points to Ethernet ports on each node that are located on the lower left of each node. The text associated with the callout says "(Optional) Ethernet to network management for Oracle Integrated Lights Out Manager (Oracle ILOM)."
Callout 3 points to the Net0 and Net1 ports on each node. These ports are located on the center right of each node. They consist of two 10 gigabyte Ethernet ports, in a horizontal row arrangement. The text associated with the callout says "10 GbE network to Net0 and Net1 (bond0)."
Callout 4 points to ports that you can use to set up a direct user interface connection for node 0, the lower node. The callout points to two USB 2.0 ports on node 0, which is underneath node 1, and above the storage array. Connect a USB cable keyboard and a USB cable mouse to these ports. Callout 4 also points to an HD-15 video port. Connect a video monitor to that port. The text associated with the callout says "(Optional) On Node 0 only, connect keyboard and mouse to USB and video display to VIDEO."
Panel 2 shows a close-up picture of a node power button, which is located on the front panel of Oracle Database Appliance. Each node has a separate power button. The power button for node 1 is on the upper left corner of the Oracle Database Appliance X3-2 system front panel, and the power button for node 0 is on the center left edge of the Oracle Database Appliance system front panel.
After you plug in each node, each node requires time to start up.
Callout 5 points to a green light-emitting diode (LED) labeled SP. After connecting the power cords as shown in step 1, the green LED labeled SP blinks for a few minutes, then turns steadily on. Wait for the SP LED to stop blinking before you proceed further.
Callout 6 points to a round button that turns on the power. When the green LED is steady on, push the power button on each SC to power on the system. Only push the power buttons once. Do not repeatedly push the power button.
Callout 7 points to a green LED labeled OK. After you push the power buttons, the green LED labeled OK blinks for a few minutes, then turns steadily on. Wait for the OK LED to stop blinking before proceeding further.
To ensure that the SAS and interconnect is properly configured, run the validate command:
/opt/oracle/oak/bin/oakcli validate -c storagetopology
Configuring the network enables you to copy files to Oracle Database Appliance.
a) Log in to the console as root with the default password welcome1.
b) Consult with your network administrator to obtain the information you need to complete this step. Run the following command and complete the dialog as shown below, replacing the network values in the display with the values from your network.
[root@oak1]# /opt/oracle/oak/bin/oakcli configure firstnet
a) From a browser on an external client, log on to My Oracle Support. Identify the latest software version by reading the following note:
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=888888.1
b) To determine if your Oracle Appliance Manager software version is current, run the following command:
/opt/oracle/oak/bin/oakcli show version -detail
If your version is out of date, then update your base image as described in the following note:
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=888888.1
c) Download the Oracle Database Appliance end-user bundle zip file from the following URL:
https://updates.oracle.com/download/12978712.html
d) Use the command scp to copy the Oracle Database Appliance End-User Bundle to a location on node 0 (for example, to /tmp).
e) (Optional) Copy the configuration file created by the Oracle Appliance Manager configurator utility to a location on node 0 (for example, to /tmp).
Note:
Refer to My Oracle Support Note 1373617.1 for step-by-step instructions to complete end-user deployment:https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1373617.1
a) Use the command oakcli unpack –package to move the end-user bundle from its current location to the location required for deployment. For example, if you copied the package p12978712_21000Linux-x86-64.zip to the directory /tmp, then enter the following command:
[root@oak1]# /opt/oracle/oak/bin/oakcli unpack -package /tmp/p12978712_xxxxxx_Linux-x86-64.zip
The Configuration Type window enables you to select a Typical or a Custom configuration. Among other things, selecting Custom enables you to:
(Optional) Configure NTP servers (the default is Cluster Time Synchronization Service)
(Optional) Configure and set up Oracle ILOM
(Optional) Specify additional network interfaces (2 additional bonded 10 GbE interfaces, and 1 additional 10 GbE interface)
(Optional) Configure Oracle Auto Service Request
(Optional) Resize the Cloud File System partition (/cloudfs). The default is 50 Gb.
a) Type the command startx to start X11 window manager software.
b) Enter the following command:
[root@oak1]# /opt/oracle/oak/bin/oakcli deploy
Oracle Appliance Manager starts, and the Welcome window opens.
(Optional) If you saved a configuration file using the Oracle Appliance Manager Configurator, then click Browse to load the file.
c) Click Next.
The Configuration Type window opens. This window shows the text Select Configuration Type, and displays two options you can select:
Typical (Recommended)
Custom
Below the two options is a button with the title Load an existing configuration. The button is labeled Browse.
On the lower left hand corner of this window is a button labeled Help, which you can click for information about each window. On the lower right hand corner of this window are buttons labeled Back, Next, and Cancel. These buttons are displayed on each Oracle Appliance Manager window.
Select either the Typical or Custom installation type.
(Optional) If you have a configuration file (for example, myserver1.conf, as shown in the step 5 example), then click Browse to locate the file and import its contents into Oracle Appliance Manager.
d) Enter the requested information as the screens appear.
At the end of the Oracle Appliance Manager configuration interview, the Summary window is displayed. The Summary window displays a list of configuration values that you have entered during the configuration interview.
Below the Summary window is the a button with the title Save the generated configuration, and labeled Save. You can click this button to save the values you entered during the configuration interview in a configuration file. Below this button are the standard window buttons, and a button labeled Install.
Click Install to start deploying the Oracle software.
Oracle Database Appliance X3-2 Virtualized Platform Setup is a poster that shows shows basic configuration steps for Oracle Database Appliance installed with a virtual server environment, a quick response (QR) code to link to documentation in the upper right corner of the poster, and URL addresses for the documentation at the bottom of the poster. The text at the bottom of the poster reads:
For more information about Oracle Database Appliance, go to Oracle Technology Network:
For more information about deployment, go to:
http://www.oracle.com/pls/topic/lookup?ctx=dba21
You can also scan the Quick Response Code with your mobile device to read the documentation
The following is a text description of each panel.
The panel shows an image of the back of an Oracle Database Appliance X3-2 system. The back of the appliance consists of two nodes on the top half, and a storage shelf on the bottom half. The upper node is node 1, and the lower node is node 0. There are seven callouts labeled 1 through 4, pointing to locations on the appliance.
Callout 1 consists of a total of 4 separate lines pointing to power plug inlets. Three of them are on the left side. They point to power cord inlet areas on the left side of the system: four inlets for the server power (two for each server), and one for the storage array. One is on the right side, and points to a power plug inlet on the storage array. The text associated with these callouts says "Power to the power supply unit (PSU)."
Callout 2 is located in the center above the two servers. It points to Ethernet ports on each node that are located on the lower left of each node. The text associated with the callout says "(Optional) Ethernet to network management for Oracle Integrated Lights Out Manager (Oracle ILOM)."
Callout 3 points to the Net0 and Net1 ports on each node. These ports are located on the center right of each node. They consist of two 10 gigabyte Ethernet ports, in a horizontal row arrangement. The text associated with the callout says "10 GbE network to Net0 and Net1 (bond0)."
Callout 4 points to ports that you can use to set up a direct user interface connection for node 0, the lower node. The callout points to two USB 2.0 ports on node 0, which is underneath node 1, and above the storage array. Connect a USB cable keyboard and a USB cable mouse to these ports. Callout 4 also points to an HD-15 video port. Connect a video monitor to that port. The text associated with the callout says "(Optional) On Node 0 only, connect keyboard and mouse to USB and video display to VIDEO."
Panel 2 shows a close-up picture of a node power button, which is located on the front panel of Oracle Database Appliance. Each node has a separate power button. The power button for node 1 is on the upper left corner of the Oracle Database Appliance X3-2 system front panel, and the power button for node 0 is on the center left edge of the Oracle Database Appliance system front panel.
After you plug in each node, each node requires time to start up.
Callout 5 points to a green light-emitting diode (LED) labeled SP. After connecting the power cords as shown in step 1, the green LED labeled SP blinks for a few minutes, then turns steadily on. Wait for the SP LED to stop blinking before you proceed further.
Callout 6 points to a round button that turns on the power. When the green LED is steady on, push the power button on each SC to power on the system. Only push the power buttons once. Do not repeatedly push the power button.
Callout 7 points to a green LED labeled OK. After you push the power buttons, the green LED labeled OK blinks for a few minutes, then turns steadily on. Wait for the OK LED to stop blinking before proceeding further.
a) To ensure that the storage and interconnect are properly configured, run the validate command:
/opt/oracle/oak/bin/oakcli validate -c storagetopology
b) Check that Oracle Virtual Machine Image is installed:
Log in to dom0 as root with the password welcome1.
Confirm that you have Oracle Virtual Machine image for Oracle Database Appliance installed using the command xm list.
[root@oak1 ~]# xm list
If the resulting command does not include Domain-0 in the Name column, or if the command fails with any other error, then you need to install the Oracle Virtual Machine image.
Configuring the network enables you to use scp to copy files to Oracle Database Appliance.
a) Log in to dom0 as root with the password welcome1.
b) Configure the network using the command /opt/oracle/oak/bin/oakcli configure firstnet.
c) Select the Global option. When prompted, enter the domain name, DNS servers, host names, network interface, IP address for nodes, netmask, and gateway address.
a) Download the ODA_BASE template from My Oracle Support and copy the template to the directory /OVS on dom0.
b) Deploy ODA_BASE using the /opt/oracle/oak/bin/oakcli deploy oda_base command.
c) When the Location prompt appears, enter the full path and file name for the ODA_BASE template you downloaded and copied.
For example:
/OVS/templateBuild-2013-01-31.tar.gz
d) When the core licensing prompt appears, enter a value from 1 through 8, which corresponds to the number of cores you want to license.
e) (Optional) Change the memory allocation for ODA_BASE.
Note:
Download the template forODA_BASE from the following URL:
a) Use a VNC client to connect to dom1 using the hostname dom0 on port 5900.
b) In the VNC session on dom1, type the command startx to start X11 window manager software.
c) Open a terminal session and enter the following command:
/opt/oracle/oak/bin/oakcli deploy
Oracle Appliance Manager starts, and the Welcome window opens.
d) Click Next.
The Configuration Type window opens. This window shows the text Select Configuration Type, and displays two options you can select:
Typical
Custom
Note:
Select Custom to configure options that default in Typical configurations, such as:Normal disk redundancy
NTP servers
Oracle ILOM
Additional network interfaces
Oracle Auto Service Requests (ASR)
Size of the /cloudfs file system (default is 50 Gb)
Below the two options is a button with the title Load an existing configuration. The button is labeled Browse. If you have a configuration file (for example, myserver1.conf, as shown in the step 5 example), then click Browse to locate the file and import its contents into Oracle Appliance Manager.
On the lower left hand corner of this window is a button labeled Help, which you can click for information about each window. On the lower right hand corner of this window are buttons labeled Back, Next, and Cancel. These buttons are displayed on each Oracle Appliance Manager window.
At the end of the Oracle Appliance Manager configuration interview, the Summary window is displayed. The Summary window displays a list of configuration values that you have entered during the configuration interview.
Below the Summary window is the a button with the title Save the generated configuration, and labeled Save. You can click this button to save the values you entered during the configuration interview in a configuration file. Below this button are the standard window buttons, and a button labeled Install.
Click Install to start deploying the Oracle software. The deployment takes about one hour to finish.
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 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 Database Appliance Alernate Text Description for Oracle Database Appliance Setup, Release 2.5.5
E27168-05
Copyright © 2011, 2013 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 of The Open Group.
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.