Oracle® Exalytics In-Memory Machine for Linux

Release Notes

Exalytics X2-4, X3-4, and X4-4 Release 2 (2.0)

E62966-01

June 2015

Oracle Exalytics In-Memory Machine is an engineered solution that includes a memory-centric hardware platform, proven in-memory technology from Oracle TimesTen, and an optimized version of Oracle Business Intelligence Foundation Suite functionality.

These release notes describe known issues and workarounds for Oracle Exalytics In-Memory Machine and apply to:

- Oracle Exalytics X2-4, X3-4, and X4-4 Release 2 (2.0.0.0)

For information about setting up Oracle Exalytics In-Memory Machine and installing software on it, consult the following manuals:

- Oracle Exalytics In-Memory Machine Installation and Administration Guide for Linux

- Oracle Exalytics In-Memory Machine Owner's Guide Exalytics X2-4, X3-4 and X4-4

The manuals are available in the Oracle Exalytics Library at:

http://docs.oracle.com/cd/E62968_01/index.htm

The following list describes the sections of this document:

- Section 1, "Oracle Exalytics Machine X2-4, X3-4, and X4-4 Release Notes"

- Section 2, "Oracle Exalytics Release 2 Software Release Notes"

- Section 3, "Documentation Accessibility"

How to Use These Release Notes

These release notes are updated periodically as new information becomes available. To ensure that you are reading the latest version of the release notes, check the Oracle Exalytics Library at:

http://docs.oracle.com/cd/E62968_01/index.htm

Sometimes, there can be a delay before revised Release Notes are published on the Oracle Technology Network (OTN). To get access to Oracle Exalytics Release Notes items as soon as they are available, go to the Oracle Exalytics Release Notes wiki at:

https://wikis.oracle.com/display/oraclebidocumentation/Oracle+Exalytics+Release+Notes

1 Oracle Exalytics Machine X2-4, X3-4, and X4-4 Release Notes

This section contains the following topics:

- Section 1.1, "Latest Product Information"

1.1 Latest Product Information

For the latest information about Sun Fire X4470 M2 Servers, including the product notes, see the following link:

http://docs.oracle.com/cd/E20781_01/index.html

2 Oracle Exalytics Release 2 Software Release Notes

This section contains the following topics:

- Section 2.1, "Patch Requirements"

- Section 2.2, "Oracle Exalytics Issues and Workarounds Identified Since the Last Revision"

- Section 2.3, "Oracle Exalytics General Issues and Workarounds"

- Section 2.4, "Oracle Exalytics Installation Issues and Workarounds"

- Section 2.5, "Oracle Exalytics Post-Installation Issues and Workarounds"

- Section 2.6, "Oracle Exalytics Patching Issues and Workarounds"

- Section 2.7, "Oracle Exalytics Documentation Errata"

2.1 Patch Requirements

Oracle Exalytics includes various software components with differing release numbers. Do not patch individual software components on the Exalytics Machine unless instructed to do so by Oracle Support. Patches for the Exalytics Machine are announced periodically. For more information, see Chapter 2, "Upgrading to Oracle Exalytics Release 2 (2.0.0.0.el5) on Non-Virtual Deployments" and Chapter 3, "Upgrading to Oracle Exalytics Release 2 (2.2.0.0.0.ovs-3.2.9) on Virtual Deployments" in Oracle Exalytics In-Memory Machine Installation and Administration Guide for Linux.

2.2 Oracle Exalytics Issues and Workarounds Identified Since the Last Revision

The issues and workarounds related to Oracle Exalytics that have been identified or changed since the last revision of the Release Notes include:

This is the first revision of the release notes for Oracle Exalytics Release 2.

2.3 Oracle Exalytics General Issues and Workarounds

This section describes general issues and workarounds related to Oracle Exalytics. It includes the following topics:

- Section 2.3.1, "Manually Editing Properties for Full-Text Search"

- Section 2.3.2, "Default Address Configured for the eth0 Interface Varies"

- Section 2.3.3, "Guest Operating System Hangs with Soft Lockup: Error on Exalytics Virtual Machine"

- Section 2.3.4, "Slow Network Connectivity after Upgrading Oracle VM Server 3.0.3 to Oracle VM Server 3.2.4+"

- Section 2.3.5, "Flash Configuration May Fail on the Exalytics X3-4 or X4-4 Machine with New Flash Cards"

- Section 2.3.6, "Errors When Upgrading the OBIEE 11.1.1.6 Domain to the 11.1.1.7 Domain."

- Section 2.3.7, "Eth0 Network Might Fail When Starting an Exalytics Machine for the First Time After Installing Oracle Exalytics Release 2"

- Section 2.3.8, "Bluetooth Service Enabled on an Exalytics Machine"

- Section 2.3.9, "InfiniBand Connection Fails When an Exalytics Machine is Started for the First Time After Installing Oracle Exalytics Release 2"

- Section 2.3.10, "Exalytics Deployments Affected by Bash "Shellshock" Vulnerabilities- CVE-2014-7169"

- Section 2.3.11, "Exalytics Virtual Deployments Affected by Venom Vulnerability-CVE-2015-3456"

- Section 2.3.12, "ILOM (Release 3.1.2.24.d) Is Unable to Verify Status of Sun Flash Accelerator F80 Adapter Cards on an X2-4 or X3-4 Exalytics Machine"

- Section 2.3.13, "Slow Network Connection on Oracle VM Guest"

- Section 2.3.14, "Auto Service Request Not Supported When Running Oracle Virtual Server Image"

- Section 2.3.15, "Sockets Direct Protocol (SDP) Not Supported With InfiniBand When Configured on Oracle Exalytics Virtual Deployments"

- Section 2.3.16, "Non-Virtualized Exalytics Machine Fails to Respond When Sockets Direct Protocol (SDP) is Enabled With InfiniBand Connectivity"

- Section 2.3.17, "QLogic Cards Not Supported for Networking on Oracle Exalytics Virtual Deployments"

- Section 2.3.18, "VNC Client Unable to Connect to the VNC Server on an Exalytics Machine Installed on an Oracle Linux 6 Operating System"

- Section 2.3.19, "Ignore Error Messages in the Exalytics Startup and Shutdown Log"

2.3.1 Manually Editing Properties for Full-Text Search

Impacted Releases: 2.0

If you configure the Full-Text Search on the Exalytics Machine, then you must manually edit the BISearchConfig.properties file so that the following properties point to the proper external IP addresses:

- BIServerUrl

- BISearchServerUrl

- ECSF_DataServiceURL

- ECSF_RedirectServiceURL

- ECSF_SecurityServiceURL

For information on editing the file, see "Configuring Properties for Full-Text Catalog Search Manually" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

2.3.2 Default Address Configured for the eth0 Interface Varies

Impacted Releases: 2.0

When an Oracle Exalytics In-Memory Machine is delivered, the default IP address that is configured for the eth0 (physical NET0 port) interface of the machine might vary. It can be any IP address in the class C subnet 192.168.1.0.

To determine the eth0 IP address of an Exalytics Machine, connect to the Integrated Lights Out Manager (ILOM) of that machine through Secure Shell (SSH) using the default IP address 192.168.1.200. After logging in, run the following command to view the network configuration information:

show /SP/network

2.3.3 Guest Operating System Hangs with Soft Lockup: Error on Exalytics Virtual Machine

Impacted Releases: 2.0

When installing a guest operating system on a virtual Exalytics Machine you might see an error message such as the following:

date _and _time wtigervm1 kernel: BUG: soft lockup - CPU#5 stuck for 141s!
sadc:1066]
date_ and _time wtigervm1 kernel: Modules linked in: ovmapi(U) autofs4(U)
@ hidp(U) l2cap(U) bluetooth(U) rfkill(U) lockd(U) sunrpc(U) be2iscsi(U)
@ ib_iser(U) iscsi_tcp(U) bnx2i(U) cnic(U) uio(U) cxgb3i(U) libcxgbi(U)
@ cxgb3(U) mdio(U) libiscsi_tcp(U) libiscsi(U) scsi_transport_iscsi(U)
rdma_ucm(U) ib_sdp(U) rdma_cm(U) iw_cm(U) ib_addr(U) ib_ipoib(U) ib_cm(U)
ipv6(U) ib_uverbs(U) ib_umad(U) mlx4_vnic(U) mlx4_vnic_helper(U) mlx4_ib(U)
ib_sa(U) ib_mad(U) ib_core(U) mlx4_core(U) video(U) output(U) sbs(U) sbshc(U)
lp(U) serio_raw(U) parport_pc(U) parport(U) floppy(U) snd_seq_dummy(U)
snd_seq_oss(U) snd_seq_midi_event(U) snd_seq(U) snd_seq_device(U)
snd_pcm_oss(U) snd_mixer_oss(U) snd_pcm(U) snd_timer(U) snd(U) soundcore(U)
snd_page_alloc(U) pata_acpi(U) i2c_piix4(U) xen_netfront(U) pcspkr(U)
i2c_core(U) ata_piix(U) ata_generic(U) xen_blkfront(U) [last unloaded:
ipmi_msghandler
date_and_time wtigervm1 kernel: CPU 5:
date_and-time wtigervm1 kernel: Modules linked in: ovmapi(U) autofs4(U)
@ hidp(U) l2cap(U) bluetooth(U) rfkill(U) lockd(U) sunrpc(U) be2iscsi(U)
@ ib_iser(U) iscsi_tcp(U) bnx2i(U) cnic(U) uio(U) cxgb3i(U) libcxgbi(U)
@ cxgb3(U) mdio(U) libiscsi_tcp(U) libiscsi(U) scsi_transport_iscsi(U)
rdma_ucm(U) ib_sdp(U) rdma_cm(U) iw_cm(U) ib_addr(U) ib_ipoib(U) ib_cm(U)
ipv6(U) ib_uverbs(U) ib_umad(U) mlx4_vnic(U) mlx4_vnic_helper(U) mlx4_ib(U)
ib_sa(U) ib_mad(U) ib_core(U) mlx4_core(U) video(U) output(U) sbs(U) sbshc(U)
lp(U) serio_raw(U) parport_pc(U) parport(U) floppy(U) snd_seq_dummy(U)
snd_seq_oss(U) snd_seq_midi_event(U) snd_seq(U) snd_seq_device(U)
snd_pcm_oss(U) snd_mixer_oss(U) snd_pcm(U) snd_timer(U) snd(U) soundcore(U)
snd_page_alloc(U) pata_acpi(U) i2c_piix4(U) xen_netfront(U) pcspkr(U)
i2c_core(U) ata_piix(U) ata_generic(U) xen_blkfront(U) [last unloaded:
ipmi_msghandler]
date_and_time wtigervm1 kernel: Pid: 1066, comm: sadc Not tainted
2.6.32-200.21.2.el5uek #1 HVM domU
date_and_time wtigervm1 kernel: RIP: 0010:[<ffffffff810652cd>]
[<ffffffff810652cd>] run_timer_softirq+0x212/0x221

To work around this issue, you must update the console of the Oracle Virtual Machine for the Oracle Exalytics Base Image 2.0.1.1.0 for Exalytics Oracle VM x86-64, from version 1.3.1 to version 1.3.2.

To update the console of the Oracle Virtual Machine:

1. Navigate to My Oracle Support and download patch number 15954524.
The patch number contains the ovm-consoled-0.1-3.2.noarch.rpm package.

2. Copy the package on all the servers in the pool.

3. Navigate to the directory where the previous ovm-consoled package is installed.

4. Enter the following command to update the rpm file:
# rpm -Uvh ovm-consoled-0.1-3.2.noarch.rpm

5. Enter the following command to restart the ovm-consoled service:
# service ovm-consoled restart

Note:
To update all guest operating systems, you must restart the server.

6. Enter the following command to verify the upgrade:
# rpm -qi ovm-consoled

7. Confirm that the output is displayed as follows:

Name: ovm-consoled
Version: 0.1
Release: 3.2
Architecture: noarch
Install Date: (not installed)
Group: Applications/System
Size: 35030

2.3.4 Slow Network Connectivity after Upgrading Oracle VM Server 3.0.3 to Oracle VM Server 3.2.4+

Impacted Releases:2.0

After upgrading Oracle VM Server 3.0.3 to Oracle VM Server 3.2.4+, you may notice slow network connectivity when copying and transferring data.

To resolve the problem, configure the Intel ixgbe 10G Ethernet Kernel Driver for bridging.

To configure Intel ixgbe 10G Ethernet Kernel Driver for Bridging:

1. Connect to Oracle VM Server.

2. To configure the driver, enter the following command:
echo "options ixgbe LRO=0" > /etc/modprobe.d/ixgbe.conf

3. Save the file.

4. Restart Oracle VM Server using Oracle VM Manager.

2.3.5 Flash Configuration May Fail on the Exalytics X3-4 or X4-4 Machine with New Flash Cards

Impacted Releases: 2.0

When you configure Flash for the first time on an Exalytics Machine, Flash configuration may fail by displaying additional number of Flash cards.

To resolve the problem, rerun the command you were running previously.

For example, if you ran the command # ./opt/exalytics/bin/configure_flash --RAID10 and the configuration failed, rerun the same command again.

2.3.6 Errors When Upgrading the OBIEE 11.1.1.6 Domain to the 11.1.1.7 Domain

Impacted Releases: 2.0

When upgrading from the OBIEE 11.1.1.6 domain to the 11.1.1.7 domain, you may get error messages related to invalid XML child elements during the non-j2ee management update step.

To resolve the error, modify the OPMN.xml file as follows:

- For the LD_LIBRARY_PATH variable, add a forward slash after append="true"
Before the edit, the line looks like this: $ORACLE_HOME/lib:/u01/app/oracle/product/TimesTen/tt1122/lib" append="true">

After the edit, the line looks like this: $ORACLE_HOME/lib:/u01/app/oracle/product/TimesTen/tt1122/lib" append="true"/>

- For the TIMESTEN_DLL variable, remove the unnecessary </variable> tag at the end of the line
Before the edit, the line looks like: <variable id="TIMESTEN_DLL" value="/u01/app/oracle/product/TimesTen/tt1122/lib/libttclient.so"/></variable>

After the edit, the line looks like: <variable id="TIMESTEN_DLL" value="/u01/app/oracle/product/TimesTen/tt1122/lib/libttclient.so"/>

The opmn.xml file is in the following directory:

/u01/app/oracle/product/fmw/instances/instance1/config/OPMN

2.3.7 Eth0 Network Might Fail When Starting an Exalytics Machine for the First Time After Installing Oracle Exalytics Release 2

Impacted Releases: 2.0

When you start an Exalytics Machine for the first time after installing the Oracle Release 2, you may notice that the eth0 network fails to start.

To resolve the problem, configure the network by running the exalytics_configure_network.sh script, after you install Oracle Exalytics Release 2.

2.3.8 Bluetooth Service Enabled on an Exalytics Machine

Impacted Releases: 2.0

When you start an Exalytics Machine, you will notice that Bluetooth service is enabled.

For security reasons, perform the following actions to disable Bluetooth services on the Exalytics Machine:

1. Log in as the root user.

2. To query the status of Bluetooth service, enter the following command:
# chkconfig --list bluetooth

If Bluetooth is enabled, the output displayed is similar to the following:

bluetooth 0:off 1:off 2:on 3:on 4:on 5:on 6:off

3. To disable Bluetooth service, enter the following command:
# chkconfig bluetooth off

4. To check the status of Bluetooth service, enter the following command:
# chkconfig --list bluetooth

5. Confirm that the output displayed is similar to the following:
bluetooth 0:off 1:off 2:off 3:off 4:off 5:off 6:off

2.3.9 InfiniBand Connection Fails When an Exalytics Machine is Started for the First Time After Installing Oracle Exalytics Release 2

Impacted Releases:2.0

When you start an Exalytics Machine for the first time after installing the Oracle Exalytics Release 2, you may notice that the Exalytics Machine is unable to connect to InfiniBand. To resolve the problem, you must restart the Exalytics Machine again.

2.3.10 Exalytics Deployments Affected by Bash "Shellshock" Vulnerabilities- CVE-2014-7169

Impacted Releases: 2.0

All virtual and non-virtual Exalytics deployments affected by Bash Shellshock Vulnerabilities (CVE-2014-7169) may be remotely exploited without authentication.

To remedy the vulnerability, navigate to My Oracle Support and follow the instructions detailed in Note 1930588.1.

2.3.11 Exalytics Virtual Deployments Affected by Venom Vulnerability-CVE-2015-3456

Impacted Releases: 2.0

All Exalytics virtual deployments may be affected by the Venom Vulnerability (CVE-2015-3456).

To remedy the vulnerability, navigate to My Oracle Support and follow the instructions detailed in Note 2011585.1.

2.3.12 ILOM (Release 3.1.2.24.d) Is Unable to Verify Status of Sun Flash Accelerator F80 Adapter Cards on an X2-4 or X3-4 Exalytics Machine

Impacted Releases: 2.0

When using ILOM (Release 3.1.2.24.d), you may notice that ILOM is unable to verify status of the Sun Flash Accelerator F80 800GB adapter cards on an X2-4 or X3-4 Exalytics Machine.

Note that while ILOM does not recognize the cards under its PCIe inventory, the cards are accessible under the operating system. To work around the limitation, and to list and verify status of the cards, enter one of the following commands as a root user:

- # /opt/exalytics/bin/exalytics_CheckFlash.sh

- # ddoemcli

2.3.13 Slow Network Connection on Oracle VM Guest

Impacted Releases: 2.0

When connecting to a Network File System (NFS) through Oracle VM Server and Oracle VM Guest, you may notice a slower connection to the NFS when connecting through Oracle VM Guest than when connecting through Oracle VM Server. To confirm and resolve the problem, navigate to My Oracle Support and follow the instructions detailed in Note 1930365.1.

2.3.14 Auto Service Request Not Supported When Running Oracle Virtual Server Image

Impacted Releases: 2.0

Auto Service Request (ASR) events generated by Integrated Lights Out Manager (ILOM) are not supported when using Oracle Exalytics Base Images for Exalytics Oracle VM x86-64.

2.3.15 Sockets Direct Protocol (SDP) Not Supported With InfiniBand When Configured on Oracle Exalytics Virtual Deployments

Impacted Releases: 2.0

Sockets Direct Protocol (SDP) is not supported with InfiniBand that is configured on a Oracle Exalytics Virtual deployment.

2.3.16 Non-Virtualized Exalytics Machine Fails to Respond When Sockets Direct Protocol (SDP) is Enabled With InfiniBand Connectivity

Impacted Releases: 2.0

When you apply the Oracle Exalytics Release 2 on a non- virtualized Exalytics Machine, you might notice that the Exalytics Machine fails to respond when SDP is enabled with InfiniBand connectivity.

To resolve the problem, navigate to My Oracle Support and follow the instructions detailed in Note 1994907.1.

2.3.17 QLogic Cards Not Supported for Networking on Oracle Exalytics Virtual Deployments

Impacted Releases: 2.0

Please note that QLogic cards are not supported for networking on Oracle Exalytics virtual deployments.

2.3.18 VNC Client Unable to Connect to the VNC Server on an Exalytics Machine Installed on an Oracle Linux 6 Operating System

Impacted Releases: 2.0

When you try using the VNC client to access the VNC server with a non-virtualized Exalytics Machine that is installed on an Oracle Linux 6 operating system, you might notice that the VNC client is unable to connect to the VNC server.

To resolve the problem, log on as the root user and run the following commands to turn off iptables:

#chkconfig iptables off

#service iptables stop

2.3.19 Ignore Error Messages in the Exalytics Startup and Shutdown Log

Impacted Releases: 2.0

When you start and stop an Exalytics Machine, you might notice the following error messages displayed in the log:

During startup:

---------------------------
Bringing up interface eth0:
@ Determining IP information for eth0... failed; no link present.  Check cable?
@ [FAILED]
@ .
@ .
@ .

During shutdown:

--------------------------
@ Shutting down interface usb0:  [  OK  ]
@ .
@ Shutting down loopback interface:  [  OK  ]
@ .
@ Unloading OpenIB kernel modules:
@ Failed to unload rds_rdma
@ .
@ Failed to unload ib_ipoib
@ .
@ Failed to unload rdma_cm
@ .
@ Failed to unload ib_cm
@ .
@ Failed to unload iw_cm
@ .
@ Failed to unload ib_addr
@ .
@ Failed to unload ib_sa
@ .
@ Failed to unload ib_mad
@ .
@ Failed to unload ib_core
@ [FAILED]

You can ignore these messages.

2.4 Oracle Exalytics Installation Issues and Workarounds

This section describes the installation issues and workarounds related to Oracle Exalytics. It includes the following sections:

- Section 2.4.1, "Exalytics Domain Management Utility Script Times Out When Scaling Out a Domain on the Secondary Exalytics Machine"

2.4.1 Exalytics Domain Management Utility Script Times Out When Scaling Out a Domain on the Secondary Exalytics Machine

Impacted Releases: 2.0

When scaling out a primary domain on the secondary Exalytics Machine, you may notice that sometimes the script times out when starting a scaled out Managed Server on the secondary machine. Note that although the script times out, the domain is installed successfully.

To resolve this problem and to view the scaled out domain on the secondary Exalytics Machine, perform the following actions:

1. Confirm that the scaled out domain is successfully installed by performing the following actions:

1. Log on to Oracle Enterprise Manager.

2. Expand WebLogic Domain, then bifoundation_domain, then Admin Server, and then bi_cluster.

3. Under bi_cluster, confirm bi_server2 is up and running.

2. Register the scaled out domain on the secondary Exalytics Machine by entering the following command:
/opt/exalytics/bin/exalytics-domain-management.sh --action=register_existing_domain --input=<location and name of input file> --domain=<domain_name_on_the_secondary machine>

3. Verify that the scaled out domain is listed on the secondary Exalytics Machine by entering the following command on the secondary Exalytics Machine:
/opt/exalytics/bin/exalytics-domain-management.sh --action=list_domains --input=<location and name of input file>

4. Confirm that the scaled out domain is listed on the secondary Exalytics Machine.

2.5 Oracle Exalytics Post-Installation Issues and Workarounds

This section describes the post-installation issues and workarounds related to Oracle Exalytics. It includes the following sections:

- Section 2.5.1, "Delete Extraneous Directory After Installation"

2.5.1 Delete Extraneous Directory After Installation

Impacted Releases: 2.0

When you use the installation scripts (manual method) to install software on the Exalytics Machine, you see that the scripts create the following directory:

/home/oracle/aggregate_store/tt_aggr_store

The scripts create this directory in error, and you must delete it before instantiating the TimesTen database with a DSN called TT_AGGR_STORE.

You can leave intact the following directories, because they are referenced by the TimesTen DSN:

/home/oracle/aggregate_store/

/home/oracle/aggregate_store/logs

2.6 Oracle Exalytics Patching Issues and Workarounds

This section describes the patching issues and workarounds related to Oracle Exalytics Release 2 and includes the following section:

- Section 2.6.1, "Oracle VM Server 3.2.9 Supports Oracle VM Manager 3.2.9 and Later Versions (in the Oracle VM Manager 3.2.x Releases)"

2.6.1 Oracle VM Server 3.2.9 Supports Oracle VM Manager 3.2.9 and Later Versions (in the Oracle VM Manager 3.2.x Releases)

Impacted Releases:2.0

In Oracle Exalytics Release 2 for Oracle VM Linux x86-64, Oracle VM Server 3.2.9 supports Oracle VM Manager 3.2.9 and later versions (in the Oracle VM Manager 3.2.x releases).

Note:
You must install Oracle VM Manager 3.2.9 or later versions (in the Oracle VM Manager 3.2.x releases) outside the Exalytics Machine.

2.7 Oracle Exalytics Documentation Errata

This section describes errata in Oracle Exalytics documentation and help systems. It includes the following topics:

- Section 2.7.1, "Oracle Exalytics In-Memory Machine Installation and Administration Guide for Linux"

- Section 2.7.2, "Oracle Exalytics In-Memory Machine Owner's Guide Exalytics X2-4, X3-4 and X4-4"

2.7.1 Oracle Exalytics In-Memory Machine Installation and Administration Guide for Linux

This section describes documentation errata in Oracle Exalytics In-Memory Machine Installation and Administration Guide for Linux.

There are no known issues at this time.

2.7.2 Oracle Exalytics In-Memory Machine Owner's Guide Exalytics X2-4, X3-4 and X4-4

This section describes documentation errata in Oracle Exalytics In-Memory Machine Owner's Guide Exalytics X2-4, X3-4 and X4-4.

There are no know issues at this time.

3 Documentation Accessibility

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.

Access to Oracle Support

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 Exalytics In-Memory Machine Release Notes for Linux, Exalytics X2-4, X3-4, and X4-4 Release 2 (2.0)

E62966-01

Copyright © 2012, 2015 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.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2015, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

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.

License Restrictions Warranty/Consequential Damages Disclaimer

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.

Warranty Disclaimer

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.

Restricted Rights Notice

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 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.

Hazardous Applications Notice

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.

Third-Party Content, Products, and Services Disclaimer

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.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.