Sun Cluster 3.1 4/04 Release Notes Supplement
This page supplements the standard user documentation, including the Sun Cluster 3.1 4/04 Release Notes for Solaris OS 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 tables list the information contained in this page and provides the revision date for this information.
Sun Cluster 3.1 4/04 Release Notes Supplement Revision Record: 2006
| Revision Date | New Information |
|---|---|
| June 2006 | Use of the Sun Cluster PatchPro site to obtain patches is replaced by Sun Patch Manager and Sun Update Connection. See Change to Patch Management. |
| May 2006 | Upgrade Procedure Uses scsetup Which Does Not Yet Exist in Sun Cluster 3.0 (6349292) |
| Cluster Panics When Some Quorum Operations Are Attempted (6373967) | |
| January 2006 | Correction to procedures for mirroring the root disk. See CR 6341573. |
Sun Cluster 3.1 4/04 Release Notes Supplement Revision Record: 2005
| Revision Date | New Information |
|---|---|
| September 2005 | Support is added for VxVM 4.1 and VxFS 4.1. See SPARC: Support for VxVM 4.1 and VxFS 4.1 in Sun Cluster 3.1 9/04 Release Notes Supplement. |
| June 2005 | Added restriction on placement of SCI cards in hot swap PCI+ (hsPCI+) I/O assemblies. See Restriction on SCI Card Placement. |
| Bug ID 6252555, problems with quorum reservations and patch 113277–28 or later. See Bug ID 6252555. | |
| Support is added for VxVM 4.0 and VxFS 4.0. See SPARC: Support for VxVM 4.0 and VxFS 4.0. | |
| May 2005 | Added restriction on quorum devices when using storage-based data replication. See Storage-Based Data Replication and Quorum Devices. |
| March 2005 | Bug ID 6210418, Process accounting log files on global file systems cause the node to hang. See Bug ID 6210418 in Sun Cluster 3.1 9/04 Release Notes Supplement. |
| January 2005 | Bug ID 6196936, SCSI reset errors when using Cauldron-S and 3310 RAID arrays. See Bug ID 6196936. |
Sun Cluster 3.1 4/04 Release Notes Supplement Revision Record: 2004
| Revision Date | New Information |
|---|---|
| December 2004 | Sun Cluster supports 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. | |
| September 2004 | Restrictions apply to Sun Cluster installations on x86 based systems. See Bug ID 5066167. |
| July 2004 | Restrictions apply to the compilation of data services that are written in C++. See Compiling Data Services That Are Written in C++. |
| June 2004 | Information about support for the Sun StorEdge™ QFS file system added. See Support for the Sun StorEdge QFS File System. |
New Features
In addition to features documented in the Sun Cluster 3.1 4/04 Release Notes for Solaris OS, this release now includes support for the following features.
SPARC: Support for VxVM 4.0 and VxFS 4.0
A patch to Sun Cluster 3.1 software adds support on Sun Cluster 3.1 4/04 configurations and earlier for Veritas Volume Manager 4.0 and Veritas File System 4.0 software. Download and install the latest Sun Cluster 3.1 Core/Sys Admin patch from http://www.sunsolve.com. This support addition is associated with Bug ID 4978425.
Support for the Sun StorEdge QFS File System
Sun Cluster supports failover of a standalone Sun StorEdge QFS file system. For use with Sun Cluster, Sun StorEdge QFS release 4.1 is required.
For information about how to configure failover of a standalone Sun StorEdge QFS file system with Sun Cluster, see the following documentation:
- Sun StorEdge QFS and Sun StorEdge SAM-FS Release Notes, part number 817-4094-10
- Sun StorEdge QFS and Sun StorEdge SAM-FS Installation and Configuration Guide, part number 817-4092-10
- Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administration Guide, part number 817-4091-10
Support for Oracle 10g Real Application Clusters on the SPARC Platform
The Sun Cluster Support for Oracle Real Application Clusters data service supports Oracle 10g Real Application Clusters on the SPARC platform.
For information about how to configure Sun Cluster Support for Oracle Real Application Clusters, see Sun Cluster Data Service for Oracle Parallel Server/Real Application Clusters Guide for Solaris OS. Additional information that you require if you are using Oracle 10g Real Application Clusters is provided in the subsections that follow.
Required Sun Cluster Support for Oracle Real Application Clusters Patches
To use Oracle 10g Real Application Clusters with Sun Cluster Support for Oracle Real Application Clusters, install the appropriate HA-OPS/RAC patch for your versions of Sun Cluster and the Solaris Operating System. See the following table.
| Sun Cluster Version | Solaris Operating System Version | HA-OPS/RAC Patch Number |
|---|---|---|
| 3.1 | 9 | 115063-04 |
| 3.1 | 8 | 115062-04 |
| 3.0 | 9 | 114176-05 |
| 3.0 | 8 | 111857-09 |
Required Sun Cluster Patches
If you are using Sun Cluster 3.1, install the appropriate Core/Sys Admin patch for your version of the Solaris Operating System. See the following table.
| Solaris Operating System Version | Core/Sys Admin Patch Number |
|---|---|
| 9 | 113801-11 |
| 8 | 113800-11 |
Required Versions of Oracle 10g Real Application Clusters
To use Oracle 10g Real Application Clusters with Sun Cluster Support for Oracle Real Application Clusters, you must use the appropriate versions of Oracle 10g Real Application Clusters and the Oracle UDLM:
- Use Oracle 10g Real Application Clusters version 10.1.0.3 with the following Oracle patches:
- 3923542
- 3849723
- 3714210
- 3455036
Use Oracle UDLM version 3.3.4.8 with Oracle patch 3965383.
Installing Oracle 10g Cluster Ready Services (CRS) With Sun Cluster 3.0
During the installation of CRS, you are prompted in the Cluster Configuration screen for the private name or private IP address for each node. If you are using CRS with Sun Cluster 3.0, you must specify the private IP address that Sun Cluster assigns to the node. CRS uses this address to interconnect the nodes in the cluster.
Each node in the cluster has a different private address. To determine the private address of a node, determine the private address that is plumbed on interface lo0:1.
# ifconfig lo0:1
Installing CRS on a Subset of Sun Cluster Nodes
By default, the Oracle installer installs CRS on all nodes in a cluster. Instructions for installing CRS on a subset of Sun Cluster nodes are available at the Oracle MetaLink web site (http://metalink.oracle.com/). See Oracle MetaLink note 280589.1 How to install Oracle 10g CRS on a cluster where one or more nodes are not to be configured to run CRS.
Using the Cluster File System
You can store only these files that are associated with Oracle Real Application Clusters on the cluster file system:
- Oracle relational database management system (RDBMS) binary files
- Oracle configuration files (for example, init.ora, tnsnames.ora, listener.ora, and sqlnet.ora )
- Archived redo log files
- Alert files (for example, alert_sid.log)
- Trace files (*.trc)
- Oracle CRS binary files
- Oracle cluster registry (OCR) files
- Oracle CRS voting disk
Note You must not store data files, control files, online redo log files, or Oracle recovery files on the cluster file system.
If you are using the cluster file system with Sun Cluster 3.1, consider increasing the desired number of secondary nodes for device groups. By increasing the desired number of secondary nodes for device groups, you can improve the availability of your cluster. To increase the desired number of secondary nodes for device groups, change the numsecondaries property. For more information, see the section about multiported disk device groups in Sun Cluster Concepts Guide for Solaris OS.
Restrictions and Requirements
The following restrictions and requirements have been added or updated since the Sun Cluster 3.1 4/04 release.
Compiling Data Services That Are Written in C++
If you are using Sun Cluster 3.1 and are writing data services in C++, you must compile these data services in ANSI C++ standard mode.
Known Problems
In addition to known problems that are documented in Sun Cluster 3.1 4/04 Release Notes for Solaris OS, the following known problems affect the operation of the Sun Cluster 3.1 4/04 release.
Bug ID 5095543
Problem Summary: When using Sun StorEdge 6130 arrays in your cluster, you cannot connect both host ports of the same controller to the same switch.
Workaround: Connect only one controller host port to a given switch. See Figure 3–1 for an example of correct cabling.
Cabling Sun StorEdge 6130 Arrays
Bug ID 5066167
Problem Summary: When installing Sun Cluster Software on x86 based systems, you cannot use autodiscovery.
Workaround: When the installer asks “Do you want to use autodiscovery (yes/no) [yes]? “ answer no and specify the cluster transport yourself.
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 4/04 Release Notes for Solaris OS.
Software Installation Guide
The following subsections describe omissions or new information that will be added to the next publication of the Software Installation Guide.
CR 6341573
Problem Summary: In the chapters for Solstice DiskSuite/Solaris Volume Manager and VxVM, the procedure for mirroring the root disk instructs you to skip enabling the localonly property if the mirror is not connected to multiple nodes. This is incorrect.
Workaround: Always enable the localonly property of the mirror disk, even if the disk does not have more than one node directly attached to it.
# scconf -c -D name=rawdisk-groupname,localonly=true
Sign up or Log in to add a comment or watch this page.