This section discusses known errors or omissions for documentation, online help, or man pages and steps to correct these problems.
All occurrences of "Sun One" in the names and descriptions of the data services for the JES applications should be read as "Sun Java System." Example: "Sun Cluster Data Service for Sun One Application Server" should read "Sun Cluster Data Service for Sun Java System Application Server."
This section discusses errors and omissions from the Sun Cluster Software Installation Guide for Solaris OS.
The procedure “How to Configure Sun Cluster Software on All Nodes (scinstall)” does not include instructions to install the Sun Cluster software packages that support the RSMAPI and SCI-PCI adapters. The installer utility does not automatically install these packages.
Follow these steps to install these additional packages from the Sun Cluster 3.1 CD-ROM. Install these packages before you install Sun Cluster framework software.
Determine which packages you must install.
The following table lists the Sun Cluster 3.1 packages that each feature requires and the order in which you must install each group of packages.
Additional Sun Cluster 3.1 Packages to Install
SUNWsci SUNWscid SUNWscidx
Use the following command to install the additional packages.
Replace arch with sparc or x86 and replace ver with 8 (for Solaris 8) or 9 (for Solaris 9).
# cd /cdrom/suncluster_3_1Packages # pkgadd -d . packages
This section discusses errors and omissions in SunPlex Manager online help.
In the online help file that is titled “Sun Cluster HA for Oracle,” in the section titled “Before Starting,” a note is incorrect.
If no entries exist for shmsys and semsys in /etc/system, default values for these variables are automatically inserted in/etc/system. The system must then be rebooted. Check Oracle installation documentation to verify that these values are correct for your database.
If no entries exist for the shmsys and semsys variables in the /etc/system file when you install the Oracle data service, you can open /etc/system and insert default values for these variables. You must then reboot the system. Check Oracle installation documentation to verify that the values that you insert are correct for your database.
In the table under "Sun Cluster RBAC Rights Profiles," the authorizations solaris.cluster.appinstall and solaris.cluster.install should be listed under the Cluster Management profile rather than the Cluster Operation profile.
In the table under “Sun Cluster RBAC Rights Profiles,” under the profile Sun Cluster Commands, sccheck(1M) should also be included in the list of commands.
This section discusses errors and omissions from the Sun Cluster Concepts Guide for Solaris OS.
In chapter 3, the section on “Using the Cluster Interconnect for Data Service Traffic“ should read as follows:
A cluster must have multiple network connections between nodes, forming the cluster interconnect. The clustering software uses multiple interconnects both for high availability and to improve performance. For both internal and external traffic (for example, file system data or scalable services data), messages are striped across all available interconnects.
The cluster interconnect is also available to applications, for highly available communication between nodes. For example, a distributed application might have components running on different nodes that need to communicate. By using the cluster interconnect rather than the public transport, these connections can withstand the failure of an individual link.
To use the cluster interconnect for communication between nodes, an application must use the private hostnames configured when the cluster was installed. For example, if the private hostname for node 1 is clusternode1-priv, use that name to communicate over the cluster interconnect to node 1. TCP sockets opened using this name are routed over the cluster interconnect and can be transparently re-routed in the event of network failure. Application communication between any two nodes is striped over all interconnects. The traffic for a given TCP connection flows on one interconnect at any point. Different TCP connections are striped across all interconnects. Additionally, UDP traffic is always striped across all interconnects.
Note that because the private hostnames can be configured during installation, the cluster interconnect can use any name chosen at that time. The actual name can be obtained from scha_cluster_get(3HA) with thescha_privatelink_hostname_node argument.
This section discusses errors and omissions from the Sun Cluster System Administration Guide for Solaris OS.
Simple root disk groups are not supported as disk types with VERITAS Volume Manager on Sun Cluster software. As a result, if you perform the procedure “How to Restore a Non-Encapsulated root (/) File System (VERITAS Volume Manager)” in the Sun Cluster System Administration Guide for Solaris OS, you should ignore Step 9, which asks you to determine if the root disk group (rootdg) is on a single slice on the root disk. You would complete Step 1 through Step 8, skip Step 9, and proceed with Step 10 to the end of the procedure.
When increasing or decreasing the number of node attachments to a quorum device, the quorum vote count is not automatically recalculated. You can re-establish the correct quorum vote if you remove all quorum devices and then add them back into the configuration.
This section discusses errors and omissions from the Data Service Guides.
In the Sun Cluster Data Service for Sun Java System Application Server Guide for Solaris OS, the example given for the asadmin command is incorrect and should be ignored. Step 15 of the procedure “How to Install and Configure the Sun Java System Application Server” should read as follows:
Change the location of the accesslog parameter to reflect the directory that you created in Step 11. To change this parameter, use the asadmin utility. See Sun Java System Application Server 7 Administration Guide for instructions.
This section discusses errors and omissions from the Sun Cluster man pages.
Thescconf_transp_adap_sci(1M) man page states that SCI transport adapters can be used with the rsm transport type. This support statement is incorrect. SCI transport adapters do not support the rsm transport type. SCI transport adapters support the dlpi transport type only.
The following sentence clarifies the name of an SCI–PCI adapter. This information is not currently included in thescconf_transp_adap_sci(1M) man page.
Use the name sciN to specify an SCI adapter.
The following paragraph clarifies behavior of the scgdevs command. This information is not currently included in thescgdevs(1M) man page.
scgdevs(1M) called from the local node will perform its work on remote nodes asynchronously. Therefore, command completion on the local node does not necessarily mean it has completed its work cluster wide.
In this release, the current API_version has been incremented to 3 from its previous value of 2. If you are developing a new Sun Cluster agent and wish to prevent your new resource type from being registered on an earlier version of Sun Cluster software, declare API_version=3 in your agent's RTR file. For more information, seert_properties(5).
To display Sun Cluster 3.0 data service man pages, install the latest patches for the Sun Cluster 3.0 data services that you installed on Sun Cluster 3.1 software. See Patches and Required Firmware Levels for more information.
After you have applied the patch, access the Sun Cluster 3.0 data service man pages by issuing the man -M command with the full man page path as the argument. The following example opens the Apache man page.
% man -M /opt/SUNWscapc/man SUNW.apache
Consider modifying your MANPATH to enable access to Sun Cluster 3.0 data service man pages without specifying the full path. The following example describes command input for adding the Apache man page path to your MANPATH and displaying the Apache man page.
% MANPATH=/opt/SUNWscapc/man:$MANPATH; export MANPATH % man SUNW.apache
The tunability of the Restart_if_Parent_Terminated extension property is any time, and not as incorrectly stated in theSUNW.sapdb(5) man page.
There is an error in the See Also section of this man page. Instead of referencing the Sun Cluster 3.1 Data Services Installation and Configuration Guide, you should reference the Sun Cluster Data Service for WebLogic Server Guide for Solaris OS.