Oracle Solaris Cluster 3.3 Release Notes Supplement

This document provides information to supplement the Oracle Solaris Cluster 3.3 Release Notes.

Resolved Issues

The following issues are resolved for the Oracle Solaris Cluster 3.3  release.  

Oracle's SPARC T3-4 Fails During Reboot (6993321)

Problem Summary: During a reboot, Oracle's SPARC T3-4 server with four processors fails to connect to the Oracle Solaris Cluster framework. For more detailed information, see 6986241. Error messages similar to the following appear:

Sep 20 15:18:53 svc.startd [8]: svc:/system/pools:default: Method or service exit timed out. Killing contract 29.

Sep 20 15:18:53 svc.startd [8]: svc:/system/pools:default: Method "/lib/svc/method/svc-pools start" failed due to signal KILL. ...

Sep 20 15:20:55 solta svc.startd [8]: system/pools:default failed: transitioned to maintenance (see 'svcs -xv' for details) ...

Sep 20 15:22:12 solta INITGCHB: Given up waiting for rgmd. ...

Sep 20 15:23:12 solta Cluster.GCHB_resd: GCHB system error: scha_cluster_open failed with 18

Sep 20 15:23:12 solta : No such process

Workaround: Apply Patch 144039-02, which is available on My Oracle Support. This issue is fixed in Oracle Solaris 10 8/11.

SAP Web Application Server Primary Instance Not Able to Come Online on the Same Node After Killing the Dispatcher (7018400)

Problem Summary: If you killed the dispatcher of a dialogue instance that was running with SAP kernel 7.11, the SAP Web Application Server agent was unable to restart the dialogue instance on the same node. After two retries, it failed over, and the start succeeded on the other node. The root cause was that, with SAP Kernel 7.11, the cleanipc command required setting LD_LIBRARY_PATH before executing cleanipc.

Problem Fixed: The following minimum patch version corrects this problem.

SPARC: 146091-04
x86: 146092-04

Known Issues and Bugs

The following known issues and bugs affect the operation of the Oracle Solaris Cluster 3.3 release.

Autodiscovery Does Not Work for the ixgbe Driver for Niantic Card (7089677)

Problem Summary: During an Oracle Solaris Cluster installation, auto discovery for the ixgbe driver for the Niantic X1109A-Z network interface card does not work. This product is also called the Sun Dual 10GbE SFP+ PCIe 2.0 Low Profile Adapter with Intel 82599 10GbE Controller.

Workaround: When you run the scinstall utility and you are prompted for the interconnect adapters, select Other and type the name of the ixgbe interface.

Documentation Issues

This section discusses errors or omissions for documentation in the 3.3 release of Oracle Solaris Cluster and Oracle Solaris Cluster Geographic Edition software.

Data Service for SAP Web Application Server Guide

This section discusses errors, omissions, and additions to the Oracle Solaris Cluster Data Service for SAP Web Application Server Guide.

Documentation Changes to Support SAP kernel 7.11

Perform the following tasks to support SAP kernel 7.11 in an Oracle Solaris Cluster configuration:

  1. Apply the Oracle Solaris Cluster patch for your platform.

    2. SPARC: 146091-05
    x86: 146092-05

  2. Amend the start and stop scripts of the dialogue instances with a kill command for potential remaining processes. 

    For example, assume the following component names:

    1. Your logical host is bulge1.
    2. The instance is D04.
    3. The SID is NUT.
    4. The start script is startsap_04.
    5. The stopsap script is stopsap_04.

    3. The following is an example for the startsap_04 start script

    

#!/usr/bin/ksh
/usr/bin/kill    -9 `/usr/ucb/ps -auxww | 
grep NUT |grep -v  startsap_04| grep  D04|grep 

  -v grep|awk '{print $2'}` >/dev/null  2>&1
/usr/sap/NUT/SYS/exe/run/startsap_di1 r3 D04 bulge1

    The following is an example for the stopsap_04 stop script. 

    #!/usr/bin/ksh

/usr/sap/NUT/SYS/exe/run/stopsap_di1 r3 D04 bulge1
 /usr/bin/kill    -9 `/usr/ucb/ps -auxww | grep NUT 
|grep -v  stopsap_04| grep D04|grep    
-v grep|awk '{print $2'}` >/dev/null  2>&1
exit 0

    NOTE: When the patch 146091-05 (SPARC) or 146092-05 (x86) is applied, it is no longer necessary to source the .profile file of the sidadmuse in the startsap and stopsap scripts. These patches introduce the use of su- instead.

  3. Amend similar kill statements to the start-up and shutdown scripts of the message server resource.  
  4. Modify the start scripts to run the sapstartsrv process outside of the message servers and the dialogue instance sapstart command. 

    The following is an example of a modified start script for the message server. 



 #!/usr/bin/ksh
/usr/bin/kill     -9 `/usr/ucb/ps -auxww | grep NUT |grep -v 
startsap_01| grep   ASCS01|grep   -v grep|awk '{print $2'}` >/dev/null  2>&1
/usr/sap/FIT/SYS/exe/run/sapstartsrv 
pf=/usr/sap/FIT/SYS/profile/NUT_ASCS01_bulge1 -D
/sapmnt/FIT/exe/uc/sun_64/startsap_msg_server r3 ASCS01 bulge1

Use similar statements for the start script for the dialogue instance.

Back to Release Notes Supplement home