5 Release Notes for Oracle Solaris on Exalogic

This chapter lists known issues in Oracle Solaris on Exalogic.

It contains the following sections:

5.1 Oracle Solaris 11.1 Release Notes

The release notes document for Oracle Solaris 11.1 is available at:


5.2 Oracle Solaris 11 Express Release Notes

The release notes document for Oracle Solaris 11 Express is available at:


5.3 Install Package for Oracle Universal Installer

If you are running the Oracle Universal Installer (OUI) on Oracle Solaris, then you must install the SUNWxwplt package.

5.4 General Issues and Workarounds

This section describes the following issues and workarounds:

5.4.1 Running Oracle Coherence on Oracle Solaris 11 Express

Keep the following points in mind when running Oracle Coherence on Oracle Solaris 11 Express:

  • Use Oracle Sun JDK 1.6.0_23 for Oracle Coherence.

  • Do not configure Oracle Coherence to loop back traffic on localhost ( To loop back traffic, you must configure Oracle Coherence to use an IP that is bound to the machine.

  • Enable -Djava.net.preferIPv4Stack=true in the start-up property. The underlying JDK/Solaris interaction will result in the following message:

    java.io.IOException: Message too long

  • Oracle Coherence on Oracle Exalogic dynamically adjusts buffering to the MTU of the interface. To use dynamic buffering, you must run the following parameters:

    ndd -set /dev/ip ip_reass_queue_bytes 16777216
    ndd -set /dev/tcp tcp_max_buf 8388608
    ndd -set /dev/udp udp_max_buf 8388608 

5.4.2 Extracting Contents of Repositories and Boot Media

To extract the contents of repositories and boot media, complete the following steps:

  1. Use an SSH client, such as PuTTY, to log in to the first compute node (also referred to as master node located in Unit 1 of your Exalogic machine rack) using the NET0 IP address. The default NET0 IP address for this compute node is Log in as root.

  2. After login, run the following command on the command line:

    # mkdir -p /share/images
  3. Edit the /etc/fstab file to add the following entry: /share/images nfs rw,bg,hard,nointr,rsize=131072,wsize=131072,tcp,vers=3
  4. Save the file and exit.

  5. Run the following command to mount the directory:

    # mount –a
  6. Run the following command:

    # cd /share/images
  7. Extract the contents of the repository by running the following command:

    tar -pxzvf el_x2-2_baseimage_solaris_1.
  8. Run the following command:

    cd el_x2-2_baseimage_solaris_1.
  9. Extract the contents of the boot media by running the following commands:

    tar -pxzvf exa-family_1.

5.4.3 Multicasting in Multi-Homed Environments for Oracle Solaris

Exalogic compute nodes are multi-homed. They have multiple network interfaces, each in a different LAN segment.

Upon IP configuration, these interfaces initiate a static route to their respective subnets. For all other networks, a default route is used. Multicasting also follows the system-wide routing table. By default, multicast packets are sent over the default route because it is a class D network.

If you want to enforce multicasting over a specific interface or network, you must add a route manually.

To multicast over the bond0 (IPoIB) interface, run the following command as a root user on the command line:

route -p add -net netmask dev bond0

Where bond0 is the name of the IPMP group for the default IPoIB interface.