Sun Cluster 3.1 8/05 Release Notes Supplement

This page supplements the standard user documentation, including the Sun Cluster 3.1 8/05 Release Notes for Solaris OSthat shipped with the Sun™ Cluster 3.1 8/05 product. These "online release notes" provide the most current information on the Sun Cluster 3.1 8/05 product. This page includes the following information.

• Revision Record
• New Features
• Restrictions and Requirements
• Known Problems
• Known Documentation Problems
• Resolved Issues

Top

Revision Record

The following tables list the information contained in this page and provides the revision date for this information.

NOTE For the list of changes made to this document after 2007, go to View page history (under the Info tab).

Sun Cluster 3.1 8/05 Release Notes Supplement Revision Record 2007

Sun Cluster 3.1 8/05 Release Notes Supplement Revision Record 2006

Sun Cluster 3.1 8/05 Release Notes Supplement Revision Record 2005

Top

New Features

In addition to features documented in the Sun Cluster 3.1 8/05 Release Notes for Solaris OS, this release now includes support for the following features.

Top

Support for Solaris 10 5/08 OS

Sun Cluster 3.1 8/05 software supports the Solaris 10 5/08 OS.

Support for Solaris 10 8/07 OS

Sun Cluster 3.1 8/05 software supports the Solaris 10 8/07 OS.

Top

Required Patches

Patches are required to run Sun Cluster 3.1 8/05 on certain operating system configurations. See to the following table to determine if your operating system configuration requires a patch.

Top

Support for Oracle 10g R2 on the x64 Platform With the Solaris 10 OS

Sun Cluster HA for Oracle supports version 10g R2 of Oracle with the Solaris 10 OS on the x64 platform.

If you are using Sun Cluster HA for Oracle with Oracle 10g R1 on SPARC and x86 platforms, an attempt by the init(1M) command to start the Oracle cssddaemon might cause unnecessary error messages to be displayed. These error messages are displayed if the Oracle binary files are installed on a highly available local file system or on the cluster file system. The messages are displayed repeatedly until the file system where the Oracle binary files are installed is mounted.

These error messages are as follows:

These messages are displayed if the following events occur:

• A node is running in noncluster mode. In this situation, file systems that Sun Cluster controls are never mounted.
• A node is booting. In this situation, the messages are displayed repeatedly until Sun Cluster mounts the file system where the Oracle binary files are installed.
• Oracle is started on or fails over to a node where the Oracle installation was notoriginally run. In such a configuration, the Oracle binary files are installed on a highly available local file system. In this situation, the messages are displayed on the console of the node where the Oracle installation was run.

To prevent these error messages, remove the entry for the Oracle cssd daemon from the /etc/inittab file on the node where the Oracle software is installed. To remove this entry, remove the following line from the /etc/inittab file:

Sun Cluster HA for Oracle does not require the Oracle cssd daemon. Therefore, removal of this entry does not affect the operation of Oracle 10g R1 with Sun Cluster HA for Oracle. If your Oracle installation changes so that the Oracle cssd daemon is required, restore the entry for this daemon to the /etc/inittab file.

Caution If you are using Real Application Clusters, do not remove the entry for the cssd daemon from the /etc/inittab file.

These error messages stated above are not displayed when you use Sun Cluster HA for Oracle with Oracle 10g R2.
The Start method of the HA Oracle fault monitor also copies an Oracle client library, libclntsh.sofrom the Oracle installation to the local file system. This library is dynamically linked to the HA Oracle fault monitor process.
Top

Support for Oracle 10g R2 Real Application Clusters on the x64 Platform

Sun Cluster Support for Oracle Real Application Clusters supports Oracle 10g R2 Real Application Clusters on the x64 platform with version 10 of the Solaris OS. For information about Sun Cluster Support for Oracle Real Application Clusters, see Sun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OS.

If you are using Sun Cluster Support for Oracle Real Application Clusters with Oracle 10g R2 Real Application Clusters on the x64 platform, the following patches are required:

• Sun Cluster patch 120498-02
• Solaris patch 119964-05
• Solaris patch 120538-04
• Solaris patch 120810-01
• Solaris patch 120808-01
• Solaris patch 118844-21 (minimum requirement, the current revision is 30)

If you are using a storage area network (SAN) to provide access to shared storage and I/O multipathing is enabled, the following Solaris patches are also required:

• 119375-13
• 119716-10

Without these patches, a node can lose access to all shared storage if a physical link that provides access to storage is disconnected or fails.

Top

RETRACTED: Support for Apache on the x64 Platform

Support for Sun Cluster HA for Apache data service on the x64 platform was reported here in error. This data service is supported only on the SPARC platform in the 3.1 8/05 release. However, the 3.2 release does support HA-Apache on both the x64 and SPARC platforms.

Top

Support for Sun Multipathing Software on Solaris 10 x86 Based Configurations

The procedure How to Install Sun Multipathing Software in Sun Cluster Software Installation Guide for Solaris OSis now also valid for x86 based configurations on the Solaris 10 operating system (OS). Contact your Sun sales representative for details.

Sun Traffic Manager is not supported on x86 based configurations that run the Solaris 9 OS. However, it is still supported on SPARC based configurations that run the Solaris 8 or Solaris 9 OS.

Top

Support for InfiniBand Adapters on the Cluster Interconnect

The following requirements and guidelines apply to Sun Cluster configurations that use InfiniBand adapters:

• A two-node cluster must use InfiniBand switches. You cannot directly connect the InfiniBand adapters to each other.
• A single Sun InfiniBand switch, which has nine ports, can support up to nine nodes in a cluster.
• Jumbo frames are not supported on a cluster that uses InfiniBand adapters.
• VLANs are not supported on a cluster that uses InfiniBand adapters.
• If only one InfiniBand adapter is installed on a cluster node, each of its two ports must be connected to a different InfiniBand switch.
• If two InfiniBand adapters are installed in a cluster node, leave the second port on each adapter unused. For example, connect port 1 on HCA 1 to switch 1 and connect port 1 on HCA 2 to switch 2.

Top

Support for the Sun StorEdge QFS Shared File System With Solaris Volume Manager for Sun Cluster

Sun Cluster Support for Oracle Real Application Clusters supports the use of the Sun StorEdge™ QFS shared file system with Solaris Volume Manager for Sun Cluster on the Solaris 10 OS. For more information, seeSun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OS.

Note Sun StorEdge QFS shared file system with Solaris Volume Manager for Sun Cluster is supported only on the SPARC platform.

Additional information that you require if you are using this configuration is provided in the subsections that follow.
Top

Required Solaris OS Patches

To use Sun Cluster Support for Oracle Real Application Clusters with the Sun StorEdge QFS shared file system and Solaris Volume Manager for Sun Cluster, install these patches in the following order:

1. 120809-01
2. 120807-01
3. 118822-21
4. 120537-04

   Note Ensure that you install the stated revision or a higher revision of each patch in the preceding list.

Top

Storage Management Requirements for Oracle Files

Storage Management Requirements for Oracle Files in Sun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OSstates that you can use the Sun StorEdge QFS shared file system only with hardware redundant array of independent disks (RAID) support. Ignore this statement.

Top

Using Sun StorEdge QFS Shared File System

How to Use Sun StorEdge QFS Shared File System in Sun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OS states that you must use the Sun StorEdge QFS shared file system with hardware RAID support. Ignore this statement.

You might use Solaris Volume Manager metadevices as devices for the shared file systems. In this situation, ensure that the metaset and its metadevices are created and available on all nodes before configuring the shared file systems.

For optimum performance, use Solaris Volume Manager for Sun Cluster to mirror the logical unit numbers (LUNs) of your disk arrays. If you require striping, configure the striping with the file systems.

Mirroring the LUNs of your disk arrays involves the following operations:

• Creating RAID0 metadevices
• Using the RAID0 metadevices or Solaris Volume Manager soft partitions of such metadevices as Sun StorEdge QFS devices

Top

Installing Sun Cluster Support for Oracle Real Application Clusters Packages

In Step 5 of the procedure How to Install Sun Cluster Support for Oracle Real Application Clusters Packages in Sun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OS, run the command for users of Solaris Volume Manager for Sun Cluster:

N is the version number of the Solaris OS that you are using. For example, if you are using the Solaris 10 OS, N is 10.

Top

Installing Oracle Real Application Clusters Software

For instructions, see Installing Oracle Real Application Clusters Software in Sun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OS.

If you are installing the Oracle binary files and Oracle configuration files on a shared file system, specify the absolute paths to the file system when the Oracle installation tool requests this information. Do not use a symbolic link whose target is the shared file system. Examples of shared file systems are the Sun StorEdge QFS shared file system and the cluster file system.

Top

Removing Sun Cluster Support for Oracle Real Application Clusters From a Cluster

Before You Begin: If you are using Sun StorEdge QFS shared file systems on Solaris Volume Manager metadevices, remove these items in the following order:

1. The resource groups that contain resources for the Sun StorEdge QFS metadata servers of these files systems
2. The Sun StorEdge QFS shared file systems

In Step 5 of the procedure How to Remove Sun Cluster Support for Oracle Real Application Clusters From a Cluster in Sun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OS, run the command for users of Solaris Volume Manager for Sun Cluster:

Top

Removing Sun Cluster Support for Oracle Real Application Clusters From Selected Nodes

Before You Begin: If you are using Sun StorEdge QFS shared file systems on Solaris Volume Manager metadevices, remove these items in the following order:

1. Each affected node from the node list of the resource groups that contain resources for the Sun StorEdge QFS metadata servers of these files systems

For instructions for removing a node from a resource group's node list, see Removing a Node From a Resource Group in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

1. The configuration of the Sun StorEdge QFS shared file systems from each affected node

In Step 4 of the procedure How to Remove Sun Cluster Support for Oracle Real Application Clusters From Selected Nodes in Sun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OS, run the command for users of Solaris Volume Manager for Sun Cluster:

Top

Support for Oracle 10g R1 and 10g R2 Real Application Clusters on the SPARC Platform

Sun Cluster Support for Oracle Real Application Clusters supports Oracle 10g R1 and 10g R2 Real Application Clusters on the SPARC platform with versions 8, 9, and 10 of the Solaris OS.

If you are using Oracle 10.1.0.4 through Oracle 10g R2 Real Application Clusters with Sun Cluster Support for Oracle Real Application Clusters, you must disable the Oracle Global Services Daemon (GSD).

Note Disabling the Oracle GSD does not enable Oracle 10g R1 or Oracle 10g R2 to coexist with Oracle 9.2.

How to Disable the Oracle GSD

Perform this task on each node of the cluster.

1. Stop the Oracle GSD.

   # crs-home/bin/crs_stop ora.nodename.gsd

   crs-home

   The home directory for Oracle Cluster Ready Services (CRS)

1. Prevent the Oracle GSD from being started if the node is rebooted.

   # crs-home/bin/crs_unregister ora.nodename.gsd

   crs-home

   The home directory for Oracle CRS

Top

Support for Oracle 10g on the x64 Platform With the Solaris 10 OS

Sun Cluster HA for Oracle supports version 10g of Oracle with the Solaris 10 OS on the x64 platform. For more information, see Sun Cluster Data Service for Oracle Guide for Solaris OS.

If you are using Sun Cluster HA for Oracle with version 10g of Oracle on the x64 platform, you must install the Oracle application files on a highly available local file system. Do not install these files on the cluster file system.

Top

Support for SAP Version 6.40

Sun Cluster HA for SAP supports version 6.40 of SAP. For more information, see Sun Cluster Data Service for SAP Guide for Solaris OS.

Steps in this guide that apply specifically to SAP 6.10 and SAP 6.20 also apply to SAP 6.40 and SAP 7.0.

When planning Sun Cluster HA for SAP installation and configuration or performing the following procedures, consult http://service.sap.com/ha for information about updates to SAP profiles.

• How to Install an SAP Scalable Application Server
• How to Enable Failover SAP Instances to Run in a Cluster

When performing How to Enable Failover SAP Instances to Run in a Cluster, add the following Step 9 to this procedure:

9. As user sapsidadm, add the following entry for enq in the DEFAULT.PFL profile file under the /sapmnt/SAPSID/profile directory.

Top

Support for MaxDB Version 7.5

Sun Cluster HA for MaxDB supports version 7.5 of MaxDB. For more information, see Sun Cluster Data Service for MaxDB Guide for Solaris OS.

Note From version 7.5 of this product, the product name SAP DB has become MaxDB by MySQL (MaxDB).

If you are using MaxDB 7.5, the UNIX user identity of the OS user who administers the MaxDB database must be sdb. Otherwise, the MaxDB fault monitor cannot probe the MaxDB database.
You are required to specify this user identity when you perform the tasks that are explained in the following sections:

• How to Install and Configure MaxDB in Sun Cluster Data Service for MaxDB Guide for Solaris OS
• How to Verify MaxDB Installation and Configuration on Each Node in Sun Cluster Data Service for MaxDB Guide for Solaris OS
• How to Register and Configure a MaxDB Resource in Sun Cluster Data Service for MaxDB Guide for Solaris OS
• How to Verify the Operation of the MaxDB Fault Monitor in Sun Cluster Data Service for MaxDB Guide for Solaris OS

Top

Support for MaxDB Version 7.6

All procedures that are currently documented for MaxDB Version 7.5 are also valid for MaxDB Version 7.6.

Top

Support for SAP Version 7.0 and NW2004 SR1

Sun Cluster HA for SAP supports version 7.0 of SAP and NW2004 SR1. For more information, see Sun Cluster Data Service for SAP Guide for Solaris OS

If you are using SAP 7.0 or NW2004 SR1 the following alternative configuration tasks are required in the following sections:

• How to Install an SAP Scalable Application Server
• How to Enable Failover SAP Instances to Run in a Cluster
• If you have installed SAP 7.0 or NW2004 SR1 using the logical host then skip all those steps that ask you to change the `references to physical host' to become `references to logical hosts' in the Sun Cluster Data Service for SAP Guide for Solaris OS. These updates to file names and file contents with such references are not required because, when you install SAP 7.0 or NW2004 SR1 using the logical host, the SAP installer creates files and file contents using the logical hostname. Thus the updates are already taken care of.

  Note In SAP 7.0 and NW2004 SR1, when a SAP instance is started, sapstartsrv process is started by default. The sapstartsrvprocess is not under the control of Sun Cluster HA for SAP Web Application Server. So, when a SAP instance is stopped or failed over by Sun Cluster HA for SAP Web Application Server, the sapstartsrv process is not stopped. It is highly recommended that the startsap script is modified, so that the sapstartsrvprocess is not started when a SAP instance is started by Sun Cluster HA for SAP Web Application Server. In addition, rename the /etc/rc3.d/S90sapinit file to /etc/rc3.d/xxS90sapinit on all the Sun Cluster nodes.

Install and Enable SAP 7.0 or NW2004 SR1 Application Server

If you are using SAP 7.0 or NW2004 SR1 and performed the SAP installation using the logical host, perform the following steps instead of step 8 in "How to Install and Enable a SAP Scalable Application Server."

1. Become the user sapsidadm.
2. In the home directory of sapsidadm user create a startup and stop script that calls the startsap script and stopsap scripts with proper arguments for the instance.

   #echo "/usr/sap/SID/SYS/exe/run/startsap instance-name logical-host" 
   > $SAPSID_HOME/startsap_instance-number

   #chmod 755 $SAPSID_HOME/startsap_instance-number

   #echo "/usr/sap/SID/SYS/exe/run/stopsap instance-name logical-host" 
   > $SAPSID_HOME/stopsap_instance-number

   #chmod 755 $SAPSID_HOME/stopsap_instance-number

3. Proceed to step 11 of "How to Install and Enable a SAP Scalable Application Server."

Enable Failover SAP Instances to Run in a Cluster

1. If you are using SAP 7.0 or NW2004 SR1 and you performed the SAP installation using the logical host, perform the following steps instead of step 5 of "How to Enable SAP Instances to Run in a Cluster."

   #echo "/usr/sap/SID/SYS/exe/run/startsap instance-name logical-host" 
   > $SAPSID_HOME/startsap_instance-number

   #chmod 755 $SAPSID_HOME/startsap_instance-number

   #echo "/usr/sap/SID/SYS/exe/run/stopsap instance-name logical-host" 
   > $SAPSID_HOME/stopsap_instance-number

   #chmod 755 $SAPSID_HOME/stopsap_instance-number

2. Proceed to step 7 of "How to Enable SAP Instances to Run in a Cluster."

Top

Additional Configuration Procedures for SAP liveCache Beginning with Version 7.5

Beginning with SAP liveCache 7.5, the following additional configuration tasks are required:

• Configuring the SAP liveCache administrator user
• Confirming that the SAP liveCache administrator user can run the lcinit command

For more information, see Sun Cluster Data Service for SAP liveCache Guide for Solaris OS

How to Configure the SAP liveCache Administrator User

Beginning with SAP liveCache 7.5, configure the SAP liveCache administrator user immediately after you perform the step to install SAP liveCache in How to Install and Configure SAP liveCache.

1. Ensure that the SAP liveCache administrator user is in the sdba user group.

The format of the SAP liveCache administrator user's user ID is lc-nameadm.

If you are creating the SAP liveCache administrator user manually, add the following entry to the /etc/group file:

For more information about the /etc/group file, see the group(4) man page.

1. If the SCM and SAP liveCache are installed on different machines, ensure that the SAP liveCache administrator user's user ID is identical and belongs to the sdba group on each machine.

To meet these requirements, ensure that the entry for the SAP liveCache administrator user in the /etc/group file on each machine is identical. The required format of this entry is given in Step 1.

How to Confirm That the SAP liveCache Administrator User Can Run the lcinit Command

Beginning with SAP liveCache 7.5, confirm that the SAP liveCache administrator user can run lcinit immediately after you perform the task How to Verify the SAP liveCache Installation and Configuration.

1. Become the SAP liveCache administrator user.

   # su - lc-nameadm

   lc-name

   Lowercase name of SAP liveCache database instance

2. Run the lcinit command.

$ lcinit

Top

Support for Oracle 10g on the x86 Platform

Sun Cluster HA for Oracle supports version 10g of Oracle with the Solaris 9 OS on the x86 platform. For more information, see Sun Cluster Data Service for Oracle Guide for Solaris OS.

Top

Restrictions and Requirements

Top

Network Appliance Network-Attached Storage Devices Requires SUNWzlib Package to Run on Sun Cluster

The Network Appliance NAS device requires the SUNWzlib package to run on Sun Cluster. If you installed the End User Solaris Software Group on your cluster, you must add the SUNWzlib package using the pkgadd command.

Top

You Can Now Configure e1000g Cards as Cluster Interconnect Using Back-to-Back Cabling

Previously, you could not use switches for private interconnects in the following hardware configurations, even if the Sun Cluster configuration included two nodes:

• Sun Fire T2000 onboard Ethernet ports
• Sun Netra T2000 onboard Ethernet ports
• Sun PCI-Express Dual Gigabit Ethernet UTP Adapter, (X)7280A-2

Now, if you have installed Solaris Operating System 10 Kernel Update patch 118833-30 or later versions of this patch, you can use switches for private interconnects in the preceding two-node hardware configurations.

Top

Fixed Problems

There are no fixed problems at this time.

Top

Features Nearing End of Life

Top

Standalone SAP J2EE Component

The standalone or add-in SAP J2EE engine component of the Sun Cluster data service for SAP Web Application Server might not be included in a future release. However, the corresponding functionality will be provided as an integrated component of the Sun Cluster data service for SAP Web Application Server also known as HA agent for SAP Enqueue Server (part number CLAIS-XAI-9999).

Top

Known Problems

In addition to known problems that are documented in Sun Cluster 3.1 8/05 Release Notes for Solaris OS, the following known problems affect the operation of the Sun Cluster 3.1 8/05 release.

Top

Auto Discovery During Installation for Sun Cluster/Transport Does Not Work for igb Interfaces on Solaris OS x64 Platforms (6821699)

Problem Summary: During a Sun Cluster installation, auto discovery for Sun Cluster/transport does not work for igb interfaces on Solaris OS x64 platforms.

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

Top

The reconf.pl  Script Fails on a Sun SPARC Enterprise T5440 Server Running Sun Cluster Software in an LDOM Configuration (6749189)

Problem Summary: If you have a Sun SPARC Enterprise T5440 Server that runs Sun Cluster software in an LDOM configuration, do not run the reconf.pl script. This script can change device paths and device instances, and can damage or destroy your Sun Cluster configuration. Recovery is extremely difficult, if not impossible.

Workaround: Do not run the reconf.pl script with this configuration.
Top

Required Steps If Solaris Secure by Default Option Is Enabled Need Documentation (6558275)

Problem Summary: During the installation of the Solaris 10 11/06 or Solaris 10 8/07 OS, if you choose not to enable network services for remote clients, a restricted network profile is used that disables external access for certain network services. The restricted services include the following services that affect cluster functionality:

• The RPC communication service, which is required for cluster communication
• The Sun Java Web Console service, which is required to use the Sun Cluster Manager GUI

Workaround: The following steps restore Solaris functionality that is used by the Sun Cluster framework but which is prevented if a restricted network profile is used.

1. Perform the following commands to restore external access to RPC communication.

# svccfg
svc:> select network/rpc/bind
svc:/network/rpc/bind> setprop config/local_only=false
svc:/network/rpc/bind> quit
# svcadm refresh network/rpc/bind:default
# svcprop network/rpc/bind:default | grep local_only

The output of the last command should show that the local_only property is now set to false.

2. (Optional) Perform the following commands to restore external access to Sun Java Web Console.

# svccfg
svc:> select system/webconsole
svc:/system/webconsole> setprop options/tcp_listen=true
svc:/system/webconsole> quit
# /usr/sbin/smcwebserver restart
# netstat -a | grep 6789

The output of the last command should return an entry for 6789, which is the port number that is used to connect to Sun Java Web Console.

SAP Central Instance Problem Due to Setting rdisp/myname Parameter in DEFAULT.PFL (6444036)

Problem Summary: Setting the parameter rdisp/myname in the DEFAULT.PFL is causing problems in RFC communication. The parameter rdisp/myname in DEFAULT.PFL is set by the system automatically and is used for unique identification of the system.

Workaround: When enabling failover SAP instances to run in a cluster, do not set the parameter rdisp/myname in the DEFAULT.PFL file as described in step 9 of the section How to Enable Failover SAP Instances to Run in a Cluster

Top

BEA WebLogic Server Managed Server Fails to Come Online (6410526)

Problem Summary: The BEA WebLogic Server Managed Server cannot come online unless the Admin Server is running.

Workaround: When you start the BEA WebLogic Server Managed Server resource in the Managed Server Independence (MSI) mode, ensure that the logical host or shared address resource used by the BEA WebLogic Server Admin Server resource is online.

Top

The Sybase Resource Goes Into the STOP_FAILED State After Probe Timeout Preventing Failover of the Resource Group (6407329)

Problem Summary: The Sybase ASE fault monitor is unable to failover the resource group to another node and also stop the Sybase resource after the probe times out and a core dump occurs.

Workaround: Clear the STOP_FAILED error flag on the Sybase resource and bring the resource group offline. Then bring the resource group online on the next available primary node.

Top

Cluster Panics When Some Quorum Operations Are Attempted (6373967)

Problem Summary: In a cluster of three or more nodes, when running version 4.4.9 of the SAN foundation software, the cluster might panic when adding or removing a quorum device.

Workaround: Quorum devices are optional in clusters of this size. Do not perform quorum operations when running this software.
Top

Java ES 4 Installer Fails to Install on Solaris 10 End User Cluster (6363536)

Problem Summary: In the Sun Java Enterprise System 2005Q4 distribution, Sun Cluster software has a dependency on Sun Java Web Console. The Solaris 10 version of Java ES no longer installs Sun Java Web Console. Instead, Sun Java Web Console is expected to be installed as part of the Solaris 10 OS.

Sun Java Web Console is only available in the Developer software group of Solaris 10 software and higher. If you install the End User software group of the Solaris 10 OS, Sun Java Web Console is not installed. Therefore, the Java ES installer will not install Sun Cluster software because this required software is missing.

Workaround: After you install the Solaris 10 End User software group but before you start the Java ES installer, use the pkgadd command to install the following Sun Java Web Console software and its dependency packages from the Solaris 10 media:

After all packages are installed, start the Java ES installer and proceed with Sun Cluster software installation.

Top

Solaris Operating System 10 Patch 118822--18 and Later Can Negatively Impact Cluster Stability When Run on SPARC Platform with PxFS (6335093)

Problem Summary: The Solaris Operating System 10 patch 118822--18 and later can cause node and cluster panics when run on a SPARC with PxFS. The workaround for this bug is to disable segkpmon all nodes of the cluster. This workaround can cause severe performance degradation when compared to an existing Solaris 10 installation. There is no performance degradation when compared to a Solaris 9 installation. The performance degradation is directly proportional to the number of CPUs on each node. Nodes with moderate numbers of CPUs (less than 20) will not be affected significantly. This problem does not affect x86/x64 systems on Solaris 8, Solaris 9, and Solaris 10 and SPARC Solaris 8 and Solaris 9 installations. This problem also does not affect clusters running UFS, QFS, and VxFS.

Workaround: Disable segkpm. On each node, add the following entry to the /etc/system file.

Top

IPv6 Scalable Service Support is Not Enabled by Default (6332656)

Problem Summary: IPv6 plumbing on the interconnects, which is required for forwarding of IPv6 scalable service packets, will no longer be enabled by default. The IPv6 interfaces, as seen when using the ifconfig command, will no longer be plumbed on the interconnect adapters by default.

Workaround: Manually enable IPv6 scalable service support.

How to Manually Enable IPv6 Scalable Service Support

Before You Begin

Ensure that you have prepared all cluster nodes to run IPv6 services. These tasks include proper configuration of network interfaces, server/client application software, name services, and routing infrastructure. Failure to do so might result in unexpected failures of network applications. For more information, see your Solaris system-administration documentation for IPv6 services.

1. On each node, add the following entry to the /etc/system file.

   set cl_comm:ifk_disable_v6=0

2. On each node, enable IPv6 plumbing on the interconnect adapters.

   # /usr/cluster/lib/sc/config_ipv6

The config_ipv6 utility brings up an IPv6 interface on all cluster interconnect adapters that have a link-local address. The utility enables proper forwarding of IPv6 scalable service packets over the interconnects.

Alternately, you can reboot each cluster node to activate the configuration change.

Top

Cluster Problems When Using the ipge3 Port as Interconnect (6328986, 6331252, 6352333)

Problem Summary: Various problems occur when using the ipge3 port for the cluster interconnect. These issues include the following:

• The cluster interconnect goes down intermittently (CR 6328986).
• Network devices based on the Intel Ophir chip are unreliable in a back-to-back configuration (CR 6331252).
• The rsh/telnet/rlogin process hangs when connecting over the cluster interconnect (CR 6352333).

Workaround: To avoid these problems, perform the following steps:

1. Set the /etc/system variable for ipge as follows:

   set ipge:ipge_taskq_disable=1

2. Use an Ethernet switch with your cluster interconnect cables for all ipge onboard interfaces. Direct-connect onboard interfaces are not supported by Sun Cluster software at this time.

Top

x86: scinstall Should Add/Delete /etc/cluster/nodeid File in filelist.ramdisk During Install/Uninstall (6299971)

Problem Summary: On Solaris 10 x86 based configurations, the x86 new boot architecture fails to boot a Sun Cluster node into cluster mode.

Workaround: Perform the following steps on each cluster node:

1. Add the following entry to the /boot/solaris/filelist.ramdisk file.

   etc/cluster/nodeid

2. Activate the change and perform a reconfiguration reboot.

   # bootadm update-archive# reboot ---- -r

Top

Localization Packages For Sun Java Web Console Do Not Exist in the Sun Cluster Standalone Distribution (6299614)

Problem Summary: In the standalone distribution of Sun Cluster 3.1 8/05 software, the Sun Java Web Console packages on the Sun Cluster 2 of 2 CD-ROM do not include localization packages. The lack of packages prevents SunPlex Manager from displaying the correct localized version after Sun Cluster software is upgraded to the Sun Cluster 3.1 8/05 release.

Workaround: During upgrade to the Sun Cluster 3.1 8/05 release, upgrade Sun Java Web Console packages from the Sun Java Enterprise System (Java ES) distribution instead of from the Sun Cluster distribution. When following the Sun Cluster procedures for upgrading dependency software, substitute the following instructions to install or upgrade Sun Java Web Console.

How to Upgrade Sun Java Web Console Localization Packages

1. Remove any Sun Java Web Console localization packages that are installed on the node.

   # pkgrm SUNWcmctg SUNWdmctg SUNWemctg SUNWfmctg SUNWhmctg SUNWkmctg SUNWjmctg# pkgrm SUNWcmcon SUNWdmcon SUNWemcon SUNWfmcon SUNWhmcon SUNWkmcon SUNWjmcon

2. Insert the Java ES 2 of 2 CD-ROM in the CD-ROM drive of the node.
3. Install the base Sun Java Web Console package by using the setup utility.

   # Product/sunwebconsole/setup

4. Change to a directory that does not reside on the CD-ROM and eject the CD-ROM.

   # cd /# eject cdrom

5. Insert the Java ES 1 of 2 CD-ROM in the CD-ROM drive of the node.
6. Change to the directory that contains the Sun Java Web Console localization packages for the language that you want.

   # cd Product/shared_components/Packages/locale/lang/

Each language package is located in the Product/shared_components/Packages/locale/lang/ directory where lang is the locale name of a particular language. For example, the locale name for Japanese is ja.

1. Install the packages manually from the lang/ directory.

   # pkgadd -d . localization-packages

2. Change to a directory that does not reside on the CD-ROM and eject the CD-ROM.
3. Continue the Sun Cluster 3.1 8/05 software upgrade procedures.

See Upgrading Sun Cluster Software in Sun Cluster Software Installation Guide.

Top

Use of the Console as ttya on a V440 Causes Unresponsiveness of WebLogic Server (6182519)

Problem Summary: In a Sun Cluster 3.1 environment, when using the console as a ttya on a V440 server, WebLogic Server can become extremely slow and unresponsive.

Workaround: Avoiding this problem involves steps specific to the WebLogic Server and its configuration files. These steps are kept in a single location to ensure that they are kept up to date as work to fix the problem progresses. To see these workaround steps, go to [http://wikis.sun.com/pages/createpage.action?spaceKey=SunCluster&title=www.sunsolve.sun.com&linkCreation=true&fromPageId=5308995] and search on change request 6182519.

Top

Configure T2000 Internal Disk Mirroring Prior to Solaris OS Installation Only (5103374)

Because of a bug in the Solaris software, procedures in the cluster user documentation will lead to a need to reinstall the operating system. Do not follow these procedures. Instead, to configure internal disk mirroring in T2000 servers, follow the special instructions in theSun Fire T2000 Server Product Notes. However, when that procedure instructs you to install the Solaris OS, do not do so. Instead, return to the cluster installation guide and follow those instructions for Solaris OS installation.

Top

Must Configure Runtime Linking Environment on SAP Unicode Systems (4996643)

Problem Summary: On SAP unicode systems, cleanpic binary needs User_env parameter for LD_LIBRARY_PATH

• sap_ci and sap_as start methods' dump core unable to start SAP unicode systems.

Workaround: To avoid this problems, if you are using a SAP Unicode system, you must perform the following steps before you perform Step 6 of How to Register and Configure Sun Cluster HA for SAP with Central Instanceas the Solaris root user configure the runtime linking environment to include the SAP exe and load library directories as follows:

1. Configure the runtime linking environment for 32 bit applications:

   # crle -u -l /sapmnt/SAPSID/exe

2. Verify that this modification has been applied for 32 bit applications:

   # crle

3. Configure the runtime linking environment for 64 bit applications:

   # crle -64 -u -l /sapmnt/SAPSID/exe

4. Verify that this modification has been applied for 64 bit applications.

   # crle -64

You need only perform these steps once. If you have not performed these steps, you will not be able to:

• Enable the failover resource group that includes the SAP central instance as described in How to Register and Configure Sun Cluster HA for SAP with Central Instance
• Enable the failover resource group that includes the SAP application server resource group, step 6 of How to Register and Configure Sun Cluster HA for SAP as a Failover Data Service
• Enable the scalable resource group that includes the SAP application server resource, as described in [How to Register and Configure Sun Cluster HA for SAP as a Scalable Data Service]

Top

Known Documentation Problems

This section discusses documentation errors you might encounter and steps to correct these problems. This information is in addition to known documentation problems that are documented in the Sun Cluster 3.1 8/05 Release Notes for Solaris OS.

Top

Release Notes

The following subsections describe omissions or errors discovered in the Sun Cluster 3.1 8/05 Release Notes for Solaris OS.

Top

Changes to Patch Management

Sun Cluster Core-Patch Requirements

The information in the section PatchPro in Sun Cluster 3.1 8/05 Release Notes for Solaris OShas changed. The PatchPro patch management technology is now available as Patch Manager 2.0 for Solaris 8 and Solaris 9 and Sun Update Connection 1.0 for Solaris 10 OS.

• Sun Patch Manager 2.0 is available for free download from SunSolve at http://wwws.sun.com/software/download/products/40c8c2ad.html. Documentation for Sun Patch Manager is available at http://docs.sun.com/app/docs/coll/1152.1.
• Sun Update Connection is available as patch ID 121118-05 (SPARC) or 121119-05 (x86) or as a download from SunSolve. See http://www.sun.com/service/sunupdate/gettingstarted.html
  for details. Documentation for Sun Update Connection is available at http://docs.sun.com/app/docs/coll/1320.2.

  Note Sun Update Connection requires the Developer software group for the initial release of the Solaris 10 OS (May 2005). To install Sun Update Connection on a system that is installed with the End User software group for this release, you must first manually install the following Solaris software packages: # pkgadd -G -d . SUNWj3dev As of the Solaris 10 1/06 release, Sun Update Connection is supported on a system that is installed with the End User software group.

Additional information about all patch management options for the Solaris 10 OS is available at http://www.sun.com/service/sunupdate/. Additional information for using the Sun patch management tools is provided in the Solaris Administration Guide: Basic Administration at http://docs.sun.com/. Refer to the version of this manual that is published for the Solaris OS release that you have installed.

If some patches must be applied when the node is in noncluster mode, you can apply them in a rolling fashion, one node at a time, unless a patch's instructions require that you shut down the entire cluster. Follow procedures in How to Apply a Rebooting Patch (Node) in Sun Cluster System Administration Guide for Solaris OSto prepare the node and boot it into noncluster mode. For ease of installation, consider applying all patches at once to a node in noncluster mode.

New Interconnect Driver Patches

When using an interconnect network driver that was not supported or available at the time of the Sun Cluster 3.1 8/05 release (e.g. nxge), System Administrators would need to apply Sun Cluster patches with one of the above methods immediately following the JES software installation in order for the adpater to be listed during the private interconnect selection portion of 'scinstall'. Also, of note, is that the 'scinstall' patching feature method of installing patches will not work in this case, since the patches are applied after the private interconnect selection portion of 'scinstall'. Another workaround for this issue would be to use the 'Other' selection when prompted by 'scinstall' for the private interconnect names, and type in the driver instances by hand (e.g. nxge0).

Top

Incorrect Claim That VxVM 4.0 Is Supported on Solaris 10 OS (CR 6315895)

In the Supported Products section, the matrix for volume manages and for file systems each lists VxVM 4.0 and VxFS 4.0 as supported on the Solaris 10 OS versions of Sun Cluster 3.1 8/05 software. However, only version 4.1 of VxVM and VxFS is supported on Solaris 10 OS. The following are the correct support matrices:

• Volume managers
  • On Solaris 8 - Solstice DiskSuite™ 4.2.1 and (SPARC only) Veritas Volume Manager 3.5, 4.0, and 4.1. Also, Veritas Volume Manager components delivered as part of Veritas Storage Foundation 4.0 and 4.1.
  • On Solaris 9- Solaris Volume Manager and (SPARC only) Veritas Volume Manager 3.5, 4.0, and 4.1. Also, Veritas Volume Manager components delivered as part of Veritas Storage Foundation 4.0 and 4.1.
  • On Solaris 10- Solaris Volume Manager and (SPARC only) Veritas Volume Manager 4.1. Also, Veritas Volume Manager components delivered as part of Veritas Storage Foundation 4.1.
  • File systems
    • On Solaris 8- Solaris UFS, (SPARC only) Sun StorEdge QFS, and (SPARC only) Veritas File System 3.5, 4.0, and 4.1. Also, Veritas File System components delivered as part of Veritas Storage Foundation 4.0 and 4.1.
    • On Solaris 9- Solaris UFS, (SPARC only) Sun StorEdge QFS, and (SPARC only) Veritas File System 3.5, 4.0, and 4.1. Also, Veritas File System components delivered as part of Veritas Storage Foundation 4.0 and 4.1.
    • On Solaris 10- Solaris UFS, (SPARC only) Sun StorEdge QFS, and (SPARC only) Veritas File System 4.1. Also, Veritas File System components delivered as part of Veritas Storage Foundation 4.1.

Top

Sun Cluster Concepts Guide for Solaris OS

The following subsection describes omissions or errors that were discovered in the Sun Cluster Concepts Guide for Solaris OS.

Top

Ambiguous Statement That Sun Cluster for SPARC Supports a Maximum of 16 Nodes (CR 6322262)

In the section Sun Cluster Topologies for SPARC in Sun Cluster Concepts Guide for Solaris OS, the following ambiguous statement appears:

A Sun Cluster environment that is composed of SPARC based systems supports a maximum of sixteen nodes in a cluster, regardless of the storage configurations that you implement.

The preceding statement is changed as follows:

A Sun Cluster environment that is composed of SPARC based systems supports a maximum of sixteen nodes in a cluster. All SPARC based topologies support up to eight nodes in a cluster. Selected SPARC based topologies support up to sixteen nodes in a cluster. Contact your Sun sales representative for more information.

Top

Software Installation Guide

The following subsections describe omissions or new information that will be added to the next publication of the Software Installation Guide.

Top

Upgrade Procedure Uses scsetup Which Does Not Yet Exist in Sun Cluster 3.0 (6349292)

The procedure to prepare a cluster for upgrade uses the scsetuputility to take resource groups offline and disable resources. However, if you are upgrading from a Sun Cluster 3.0 version, the scsetup utility is not yet available. To perform these tasks, use the following commands instead:

1. Take each resource group offline.

   # scswitch -F -g resource-group

   -F	Switches a resource group offline

1. From any node, list all enabled resources in the cluster.

   # scrgadm -pv | grep "Res enabled"(resource-group:resource) Res enabled: True

2. Identify those resources that depend on other resources.

You must disable dependent resources first before you disable the resources that they depend on.

1. Disable each enabled resource in the cluster.

   # scswitch -n -j resource

   -n

   Disables

See the scswitch(1M) man page for more information.

1. Verify that all resources are disabled.

   # scrgadm -pv | grep "Res enabled"(resource-group:resource) Res enabled: False

2. Move each resource group to the unmanaged state.

   # scswitch -u -g resource-group

   -u	Moves the specified resource group to the unmanaged state

Top

Incorrect Release Date for the First Update of the Solaris 10 OS

In Appendix, Upgrading Sun Cluster Software From Solaris 8 to Solaris 9 Software, upgrade guidelines and procedures refer to the first update release of the Solaris 10 OS as Solaris 10 10/05. The date of this release is incorrect. The correct release date is 1/06.

Therefore, to upgrade a Sun Cluster configuration to the Solaris 10 OS, the Solaris 10 1/06 release is the minimum version that Sun Cluster 3.1 8/05 software supports.

Top

Clarification of the Restriction Concerning Solaris 10 Non-Global Zones

The section Solaris OS Restrictions in the chapter Planning the Sun Cluster Configuration contains the following statement:

This restriction applies specifically to the installation location of Sun Cluster framework software and Sun Cluster data-service software. It does not restrict the creation of non-global zones on a cluster node. In addition, applications can be installed in a non-global zone on a cluster node and configured to be highly available and managed by Sun Cluster software. For more information, see Sun Cluster HA for Solaris Containers in Sun Cluster 3.1 8/05 Release Notes for Solaris OS.
Top

Package Dependency Change from 1.0 to 1.1 Causes Installation Problems (6316676)

The procedures to upgrade dependency software (nonrolling upgrade and rolling upgrade) are correct only for common agent container version 1.0, which was distributed in the initial standalone release of Sun Cluster 3.1 8/05 software. The Sun Java Enterprise System 2005Q4 distribution contains common agent container version 1.1, which now has a package order dependency.

To install common agent container 1.1 software from the Java ES 2005Q4 distribution, specify the package names explicitly and in the following order, to satisfy the new package dependencies:

Top

Sun Cluster System Administration Guide for Solaris OS

The following subsection describes an error that was discovered in the Sun Cluster System Administration Guide for Solaris OS.

The instructions in Chapter 8 for restoring an encapsulated root file sytem for VERITAS Volume Manager are incorrect. Replace Step #14 with the following step:

14. Run the scvxinstall command to encapsulate the disk and reboot.

Top

Sun Cluster Data Service for Solaris Containers Guide

The following sections in Sun Cluster Data Service for Solaris Containers Guide are incorrect:

• How to Install and Configure a Zone in Sun Cluster Data Service for Solaris Containers Guide

Replace this incorrect section with How to Install a Zone and Perform the Initial Internal Zone Configuration

• Patching the Global Zone and Local Zones in Sun Cluster Data Service for Solaris Containers Guide

Replace this incorrect section with How to Patch to the Global Zone and Local Zones.

How to Install a Zone and Perform the Initial Internal Zone Configuration

Perform this task on each node that is to host the zone.

Note For complete information about installing a zone, see System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

Before You Begin

Determine the following requirements for the deployment of the zone with Sun Cluster:

• The number of Solaris Zone instances that are to be deployed.
• The cluster file system that is to be used by each Solaris Zone instance.

Ensure that the zone is configured.

If the zone that you are installing is to run in a failover configuration, configure the zone's zone path to specify a highly available local file system. The file system must be managed by the SUNW.HAStoragePlus resource that you created in How to Enable a Zone to Run in a Failover Configuration in Sun Cluster Data Service for Solaris Containers Guide.

For detailed information about configuring a zone before installation of the zone, see the following documentation:

• Chapter 17, Non-Global Zone Configuration (Overview), in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones
• Chapter 18, Planning and Configuring Non-Global Zones (Tasks), in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones

1. If the zone is to run in a failover configuration, ensure that the zone's zone path can be created on the zone's disk storage.

If the zone is to run in a multiple-masters configuration, omit this step.

1. 1. On the node where you are installing the zone, bring online the resource group that contains the resource for the zone's disk storage.

      # scswitch -z -g solaris-zone-resource-group -h node

   2. If the zone's zone path exists on the zone's disk storage, remove the zone path.

The zone's zone path exists on the zone's disk storage if you have already installed the zone on another node.

1. Install the zone.

   # zoneadm -z zone install

For more detailed information about installing a zone, see How to Install a Configured Zone in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

1. Perform the initial internal zone configuration.
   1. Log in to the zone's console.

      # zlogin -C zone

You are prompted to configure the zone.

1. 1. Follow the prompts to configure the zone.
   2. Disconnect from the zone`s console.

Use the escape sequence that you defined for the zone. If you did not define an escape sequence, use the default escape sequence as follows:

How to Patch to the Global Zone and Local Zones

This task is required only if you are applying a patch to the global zone and to local zones. If you are applying a patch to only the global zone, follow the instructions in Chapter 8, Patching Sun Cluster Software and Firmware, in Sun Cluster System Administration Guide for Solaris OS.

This task applies to both nonrebooting patches and rebooting patches.

Perform this task on all nodes in the cluster.

1. Ensure that the node that you are patching can access the zone paths of all zones that are configured on the node.

Some zones might be configured to run in a failover configuration. In this situation, bring online on the node that you are patching the resource group that contains the resources for the zones' disk storage.

1. Apply the patch to the node.

For detailed instructions, see Chapter 8, Patching Sun Cluster Software and Firmware, in Sun Cluster System Administration Guide for Solaris OS in Sun Cluster System Administration Guide for Solaris OS.

Top

Sun Cluster Data Service for Oracle Guide for Solaris OS

The following information is missing from the topic Sun Cluster Data Service for Oracle Guide for Solaris OS in the Sun Cluster Data Service for Oracle Guide for Solaris OS.

Top

Obtaining Core Files for Troubleshooting

To facilitate troubleshooting of unexplained DBMS timeouts, you can enable the fault monitor to create a core file when a probe timeout occurs. The contents of the core file relate to the fault monitor process. The fault monitor creates the core file in the / directory. To enable the fault monitor to create a core file, use the coreadm command to enable set-id core dumps. For more information, see the coreadm(1M) man page.

Top

Sun Cluster Data Service for SAP Guide for Solaris OS

The following information is missing from Sun Cluster Data Service for SAP Guide for Solaris OS:

After modifying your SAP system's database to refer to a logical host, if you are using SAP DB or MaxDB as your database, create a .XUSER.62 file in the home directory of the sapsysadm user that refers to the logical host of the database. Create this .XUSER.62 file using the dbmcli or xuser tools. Test this change using R3trans -d. This step is necessary so the SAP instance can find the database state while starting up.

Top

Adding New Entries to SAP Profiles (6342832)

When following the procedure How to Enable Failover SAP Instances to Run in a Cluster in Sun Cluster Data Service for SAP Guide for Solaris OS, add the following eighth step to the procedure.

8. Become user sapsidadm. Add the following lines to the DEFAULT.PFL file located under the /sapmnt/SAPSID/profile directory:

The following information is missing from Sun Cluster Data Service for SAP Guide for Solaris OS, Sun Cluster Data Service for SAP Guide for Solaris OS, and [How to Enable Failover SAP Instances to Run in a Cluster] sections in Sun Cluster Data Service for SAP Guide for Solaris OS.

For information about updates to SAP profile, see the SAP documentation at http://service.sap.com/ha.

Top

Sun Cluster Data Service for SAP DB Guide for Solaris OS

The following information is missing from the Sun Cluster Data Service for MaxDB Guide for Solaris OS:

When following the procedure How to Install and Configure MaxDB in Sun Cluster Data Service for MaxDB Guide for Solaris OS, add the following fifth step to the procedure:

5. Copy the /etc/opt/sdb directory and its contents from the node on which you installed SAP DB to all nodes where resources for SAP DB and SAP xserver will run.

Ensure that the ownership of this directory and its contents is the same on all nodes:

Top

Sun Cluster Data Service for SAP liveCache Guide for Solaris OS

The following information is missing from the Sun Cluster Data Service SAP liveCache Guide for Solaris OS:

When following the procedure How to Install and Configure SAP liveCache, add the following fifth and sixth steps to the procedure:

5. Copy the /etc/opt/sdb directory and it contents from the node on which you installed SAP liveCache, to all the nodes where resources for SAP liveCache will run. Ensure that the ownership of these files is the same on all nodes as it is on the node on which you installed SAP liveCache.

6. Create a link from the /sapdb/LCA/db/wrk directory to the /sapdb/data/wrk directory as follows:

Top

Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS

Information is missing from the Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS on the following topics:

• How to Install and Configure the Scalable SAP Web Application Server and the SAP J2EE Engine
• How to Modify the Installation for a Scalable SAP Web Application Server Component
• How to Create a Dependency on the Web Application Server Database

Top

How to Install and Configure the Scalable SAP Web Application Server and the SAP J2EE Engine

When performing the procedure How to Install and Configure the SAP Web Application Server and the SAP J2EE Engine in Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS check ??http://service.sap.com/ha??and corresponding SAP notes for information about any changes that you must make to the SAP configuration for it to work with a logical host.

Step 2 of How to Install and Configure the SAP Web Application Server and the SAP J2EE Engine in Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS is missing information for the J2EE user.

2. If you are using the SAP J2EE engine, install J2EE as an addon or a standalone, following these instructions:

2a. If you are configuring J2EE as a failover data service install the SAP J2EE engine software on the same node as which you installed the SAP Web Application Server software.

2b. If you are configuring J2EE as a scalable data service, install the same J2EE instance using the same instance name on each node where you want the corresponding scalable resource to run.

Top

How to Modify the Installation for a Scalable SAP Web Application Server Component

Steps 2 and 5 of procedure "How to Modify the Installation for a Scalable SAP Web Application Server Component" in Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS are missing information specific to the use of a scalable J2EE instance and a scalable ABAP Web Application Server instance.

2. If you are on an ABAP-only system, copy the dialog instance from the node where it was installed to the local file system on the other nodes.

Note If you are using the J2EE engine, you have installed the J2EE instance on each node. For more information, see Step 2 of How to Install and Configure the Scalable SAP Web Application Server and the SAP J2EE Engine .

5. Update the script $HOME/loghost as follows:
Here are examples depending on the type of instance you are using:

The returned string must match the corresponding profiles for the instance. A scalable resource group does not contain a logical host.
Top

How to Create a Dependency on the Web Application Server Database

When following Step 2 of the procedure How to Register and Configure an SAP Enqueue Server Resource in Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS, add a dependency to the Web Application Server database:

2. Create an SAP enqueue server resource in the SAP central services resource group.

When following Step 2 of the procedure How to Register and Configure an SAP Message Server Resource in Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS, add a dependency to the Web Application Server database:

2. Create an SAP message server resource in the SAP central services resource group.

Top

Support for SAP Version 7.0 for Sun Cluster HA for SAP Web Application Server (6461002)

When running sapinst installer to install SAP 7.0 or NW2004 SR1, use the SAPINST_USE_HOSTNAMEparameter to install SAP using the logical host. Once the installation is completed using the logical host, ignore all steps that ask for updates related to the logical hosts. Also, before you register resources of type SUNW.sapwebas or SUNW.sapscs, you must create a wrapper script in the home directory of the sapsidadm user that calls the startsap and stopsap scripts with the proper arguments for the instance:

1. Become user sapsidadm

2. In the home directory of sapsidadm, create a wrapper script that invokes the appropriate startsap and stopsap script generated by the SAP installer with necessary parameters.

When creating a resource of type SUNW.sapwebas, specify the appropriate wrapper scripts for the webas_startup_script and webas_shutdown_script extension properties. Similarly, while creating the resource type SUW.sapscs, specify the appropriate wrapper script for the scs_startup_script and scs_shutdown_script extension properties.

After completing the installation of SAP 7.0 or NW2004 SR1, add the following to the LD_LIBRARY_PATH to the end of the .profile filename in the home directory of user sapsidadm:

Ensure that the $HOME/.profile is sourced by the startsap and stopsap scripts.

The following information is missing in the post-installation procedures of SAP 7.0 or NW2004 SR1:

In SAP 7.0 and NW2004 SR1, when a SAP instance is started, sapstartsrv process is started by default. The sapstartsrvprocess is not under the control of Sun Cluster HA for SAP Web Application Server. So, when a SAP instance is stopped or failed over by Sun Cluster HA for SAP Web Application Server, the sapstartsrv process is not stopped.

It is highly recommended that the startsap script is modified, so that the sapstartsrvprocess is not started when a SAP instance is started by Sun Cluster HA for SAP Web Application Server. In addition, rename the /etc/rc3.d/S90sapinit file to /etc/rc3.d/xxS90sapinit on all the Sun Cluster nodes.

Top

Sun Cluster Data Service for Sybase ASE Guide for Solaris OS

The following information is missing from the topic Sun Cluster Data Service for Sybase ASE Guide for Solaris OS in the Sun Cluster Data Service for Sybase ASE Guide for Solaris OS.

Top

Obtaining Core Files for Troubleshooting

To facilitate troubleshooting of unexplained DBMS timeouts, you can enable the fault monitor to create a core file when a probe timeout occurs. The contents of the core file relate to the fault monitor process. The fault monitor creates the core file in the / directory. To enable the fault monitor to create a core file, use the coreadm command to enable set-id core dumps. For more information, see the coreadm(1M) man page.

Resolved Issues

Private Network Interfaces Using the nxge Driver Can Cause a Solaris OS Panic (6525548 and 6726165)

Problem Summary: Private network interfaces that use the nxge(7D)driver can cause a panic in the Solaris OS (6525548 and 6726165). A cluster node might panic if the network adapter meets the following criteria:

1. Your private network adapter uses the nxge driver.
2. A change in network adapter state follows a change in cluster configuration.

A stack trace of the panic might look like this stack trace (6525548):

A demangled stack trace of the panic might look like this stack trace (6525548):

A stack trace of the panic might look like this stack trace (6726165):

A demangled stack trace might look like this stack trace (6726165):

To determine whether you are using the nxge driver, type one of the following commands:

• If you are using Sun Cluster 3.2, on a cluster node, type clinterconnect status.
• If you are using Sun Cluster 3.1, on a cluster node, type scstat -W, as shown in the following example.

Note You can also use the modinfo or the ifconfig command to determine if the nxge driver is used on a node. For example, you can type modinfo -c | grep nxge.

Examples of a change in adapter state that follows a change in cluster configuration are:

• The cluster switches over and the private adapter fails.
• The private adapter is disabled.

Solution: For SPARC, apply Patch 138048-03 or later to resolve both the Solaris OS panic and the Sun Cluster software issue. For x86, apply Patch 138049-03 or later.

Workaround: You can perform the following workaround until you apply the appropriate patch:

1. On each node that uses an nxge private adapter, add the following entry to the /etc/system file.

   set nxge:nxge_rx_threshold_hi=0

2. Reboot.

Top

Required Minimum Solaris Kernel Patch for UltraSPARC T2 and UltraSPARC T2 Plus Servers

Problem Summary: The Sun Cluster software requires Solaris kernel Patch 137111-01 or later to avoid  a node panic on all UltraSPARC T2 and UltraSPARC T2 Plus-based servers. Without this patch, a panic can occur when a node in the cluster attempts to mount a Global File System (pxfs).

A stack trace of the panic is similar to the following:

 A demangled stack trace of the panic is similar to the following:

Solution: Apply Patch 137111-01 to eliminate the cause of the Solaris kernel panic. 

 Top