Sun Cluster Data Services 3.1 10/03 Release Notes Supplement
This page supplements the standard user documentation, including the Sun Cluster 3.1 Data Service 5/03 Release Notes that shipped with the Sun™ Cluster 3.1 product. These “online release notes” provide the most current information on the Sun Cluster 3.1 product. This page includes the following information.
- Revision Record
- New Features
- Restrictions and Requirements
- Known Problems
- Known Documentation Problems
Revision Record
The following table lists the information contained in this page and provides the revision date for this information.
Sun Cluster Data Services 3.1 10/03 Release Notes Supplement Revision Record: 2003/2004
| Revision Date | New Information |
|---|---|
| December 2004 | Sun Clustersupports the use of ASM with Oracle 10g Real Application Clusters on the SPARC platform. For more information, see IPv6 Support and Restrictions for Public Networks. |
| November 2004 | The Sun Cluster Support for Oracle Real Application Clusters data service supports Oracle 10g Real Application Clusters on the SPARC platform. For more information, see Support for Oracle 10g Real Application Clusters on the SPARC Platform. |
| Cabling restrictions apply when including Sun StorEdge 6130 arrays in a Sun Cluster environment. See Bug ID 5095543 for more information. | |
| May 2004 | The Sun Cluster HA for Oracle data service in Sun Cluster Data Services 3.1 10/03 now supports Oracle 10g. See Support for Oracle 10g. |
| February 2004 | Bug ID 4818874, lack of support for Sun StorEdge 3310 JBOD array in a split-bus configuration, has been fixed. See BugId 4818874 for details. |
| Conceptual material and example configurations for using storage-based data replication in a campus cluster. Refer to Chapter 7, Campus Clustering With Sun Cluster Software, in Sun Cluster 3.0-3.1 Hardware Administration Manual for Solaris OS. | |
| December 2003 | Problem of using NIS for naming services in a cluster that runs Sun Cluster HA for SAP liveCache. See Sun Cluster HA for liveCache nsswitch.conf requirements for passwd make NIS unusable (4904975). |
| November 2003 | Procedure and examples to upgrade data services that cannot be upgraded by using the scinstall utility. See Some Data Services Cannot be Upgraded by Using the scinstall Utility. |
| Support for WebLogic Server 8.x. See WebLogic Server Version 8.x. |
New Features
In addition to features documented in the Sun Cluster 3.1 Data Service 5/03 Release Notes, this release now includes support for the following features.
Support for Oracle 10g
The Sun Cluster HA for Oracle data service in Sun Cluster Data Services 3.1 10/03 now supports Oracle 10g.
If you are using Sun Cluster HA for Oracle with Oracle 10g, an attempt by the init(1M) command to start the Oracle cssd daemon 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:
INIT: Command is respawning too rapidly. Check for possible errors.
id: h1 "/etc/init.d/init.cssd run >/dev/null 2>&1 >/dev/null"
Waiting for filesystem containing $CRSCTL.
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 not originally 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:
h1:23:respawn:/etc/init.d/init.cssd run >/dev/null 2>&1 > </dev/null
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 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. |
WebLogic Server Version 8.x
System administration instructions for Sun Cluster for WebLogic Server apply also to WebLogic Server version 8.x. For documentation on Sun Cluster for WebLogic Server, see the Sun Cluster Data Service for WebLogic Server Guide for Solaris OS.
Restrictions and Requirements
The following restrictions and requirements have been added or updated since the Sun Cluster 3.1 Data Services 10/03 release.
There are no known restrictions and requirements at this time.
Known Problems
In addition to known problems that are documented in the Sun Cluster 3.1 Data Service 5/03 Release Notes, the following known problems affect the operation of the Sun Cluster 3.1 Data Services 10/03 release.
Some Data Services Cannot be Upgraded by Using the scinstall Utility
The data services for the following applications cannot be upgraded by using the scinstall utility:
- Apache Tomcat
- DHCP
- mySQL
- Oracle E-Business Suite
- Samba
- SWIFTAlliance Access
- WebLogic Server
- WebSphere MQ
- WebSphere MQ Integrator
If you plan to upgrade a data service for an application in the preceding list, replace Step 5 in the procedure Upgrading to Sun Cluster 3.1 10/03 Software (Rolling) in Sun Cluster 3.1 10/03 Software Installation Guide with the steps that follow. Perform these steps for each node where the data service is installed.
How to Upgrade Data Services That Cannot be Upgraded by Using scinstall
- Remove the software package for the data service that you are upgrading.
# pkgrm pkg-inst
_pkg-inst_ specifies the software package name for the data service that you are upgrading as listed in the following table.Application Data Service Software Package Apache Tomcat SUNWsctomcat DHCP SUNWscdhc mySQL SUNWscmys Oracle E-Business Suite SUNWscebs Samba SUNWscsmb SWIFTAlliance Access SUNWscsaa WebLogic Server (English locale) SUNWscwls WebLogic Server (French locale) SUNWfscwls WebLogic Server (Japanese locale) SUNWjscwls WebSphere MQ SUNWscmqs WebSphere MQ Integrator SUNWscmqi - Install the software package for the version of the data service to which you are upgrading.
To install the software package, follow the instructions in the Sun Cluster documentation for the data service that you are upgrading. This documentation is available in the Sun Cluster 3.1 10/03 Data Services Collection at http://docs.sun.com/db/coll/573.11.
Sun Cluster HA for liveCache nsswitch.conf requirements for passwd make NIS unusable (4904975)
The requirements for the nssswitch.conf file in Preparing the Nodes and Disks do not apply to the entry for the passwd database.
The entry in the /etc/nsswitch.conf file for the passwd database should be as follows:
passwd: files nis [TRYAGAIN=0]
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 documented in the Sun Cluster 3.1 Data Service 5/03 Release Notes.
There are no known problems at this time.