|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Cluster 3.3 3/13 Release Notes Oracle Solaris Cluster 3.3 3/13|
This section contains the following information about Oracle Solaris Cluster compatibility issues with other products. Contact your Oracle support representative to learn whether a fix becomes available.
See also the following information:
Additional Oracle Solaris Cluster framework compatibility issues are documented in Chapter 1, Planning the Oracle Solaris Cluster Configuration, in Oracle Solaris Cluster Software Installation Guide.
Additional Oracle Solaris Cluster upgrade compatibility issues are documented in Upgrade Requirements and Software Support Guidelines in Oracle Solaris Cluster Upgrade Guide.
For other known problems or restrictions, see Known Issues and Bugs.
Problem Summary: If your Oracle Solaris Cluster HA for Oracle Database or Support for Oracle RAC configuration requires using Oracle ASM with Solaris Volume Manager mirrored logical volumes, you might experience failures of the SUNW.ScalDeviceGroup probe. These failures result in a loss of availability of any service that is dependent on the SUNW.ScalDeviceGroup resource.
Workaround: You can mitigate the failures by increasing the IOTimeout property setting for the SUNW.ScalDeviceGroup resource type. See Article 603825.1 at My Oracle Support for additional information.
Problem Summary: Because of an issue with ACFS resources going offline unexpectedly, the combination of Oracle 12.1 and ACFS with Oracle Solaris Cluster 3.3 3/13 is not currently supported. This issue does not affect Oracle 188.8.131.52 ACFS support.
Workaround: Contact your Oracle support representative to learn whether a fix or workaround is available.
Problem Summary: Clusters with Tavor IB Host Channel Adapters (HCAs) panic when attempting to use Reliable Datagram Sockets (RDS) v3 drivers. RDSv3 is not supported on Tavor IB because of hardware limitations. Use the following command to determine if Tavor IB is installed:
# /usr/sbin/prtconf -v | grep tavor
Workaround: Configure applications on the cluster to use either RDS version 1 or the IP-over-IB protocol. In order to run RDSv3, the Hermon IB HCAs must be installed on the cluster.
Problem Summary: During upgrade from Oracle Solaris 9 to Oracle Solaris version 10 8/11 or 10 1/13, the /etc/hostname.adp file is overwritten. This causes networking resources to fail to come online, because the IPMP group configuration was removed during the file overwrite.
Workaround: Perform the following steps for each node you upgrade:
Before you upgrade the Oracle Solaris OS, save the contents of the /etc/hostname.adp file.
After the upgrade but before you reboot the system, copy the saved contents of the pre-upgrade hostname.adp files to the current hostname.adp files.
After you reboot the system, if there was IPMP group information available in the /etc/hostname.adp files, verify that IPMP groups are created correctly. Use either the cluster command or ifconfig commands.
The Enhanced Storage module of Solaris Management Console (Solaris Volume Manager) is not compatible with Oracle Solaris Cluster software. Use the command-line interface or Oracle Solaris Cluster utilities to configure Solaris Volume Manager software.