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 Sun Java Enterprise System 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.
In the Sun Cluster Software Installation Guide for Solaris OS, the procedure How to Install Sun Cluster Software Packages in Sun Cluster Software Installation Guide for Solaris OS incorrectly documents the location of the installer program on the base CD-ROM. The procedure documents the installer program as being at the CD-ROM mount point directory level. Instead, the installer program is located in the Solaris_sparc/Product/sun_cluster/ directory of the SPARC CD-ROM and in the Solaris_x86/Product/sun_cluster/ directory of the x86 CD-ROM.
The procedure How to Install Cluster Control Panel Software on an Administrative Console in Sun Cluster Software Installation Guide for Solaris OS contains the following unnecessary steps and one inaccuracy:
You do not need to use the pkgadd command to install the Cluster Control Panel package SUNWccon or to install the documentation packages. You can pick these packages from the list provided by the installer program. Ignore Step 12 and Step 14 of the procedure.
You do need to use the pkgadd command to install the man page package, SUNWscman. The installer program does not include that package in the list of software packages that it can install. Ignore Step 9 of the procedure.
The section Public Networks in Sun Cluster Software Installation Guide for Solaris OS states, “Sun Cluster software supports IPv4 and IPv6 addresses on the public network, both for failover and scalable data services.” This statement is not correct for Sun Cluster software for Solaris 8. Sun Cluster software for Solaris 8 supports a failover data service to run on an IPv6 address, but does not support a scalable data service to run on an IPv6 address. Sun Cluster software for Solaris 8 continues to support IPv4 addresses for both failover and scalable data services.
The procedure How to Finish a Nonrolling Upgrade to Sun Cluster 3.1 9/04 Software in Sun Cluster Software Installation Guide for Solaris OS incorrectly instructs you to edit the /opt/SUNWsclc/livecache/bin/lccluster file if you upgraded the Sun Cluster HA for SAP liveCache data service from the Sun Cluster 3.0 version to the 3.1 version. Do not perform the instruction to edit the /opt/SUNWsclc/livecache/bin/lccluster file. This file is only a template that is installed with the data service and should not be edited in that location. Instead, perform the following steps:
After upgrade to the Sun Cluster 3.1 version of Sun Cluster HA for SAP liveCache, go to a node that will host the liveCache resource.
Copy the new /opt/SUNWsclc/livecache/bin/lccluster file to the /sapdb/LC_NAME/db/sap/ directory, overwriting the lccluster file that already exists from the previous configuration of the data service.
Configure this /sapdb/LC_NAME/db/sap/lccluster file as documented in Step 3 of How to Register and Configure Sun Cluster HA for SAP liveCache in Sun Cluster Data Service for SAP liveCache Guide for Solaris OS.
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.
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.
Correct:
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.
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 rerouted 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.
Instructions for upgrading Sun Cluster HA for DHCP are omitted from Sun Cluster Data Service for DHCP Guide for Solaris OS.
As a result of bug fixes, the configuration for IPMP based clusters has changed. If you are running Sun Cluster HA for DHCP on an IPMP-based cluster, you have to disable, delete and reregister the DHCP resource.
Save the Sun Cluster DHCP resource definitions.
# scrgadm -pvv -j resource > file1 |
Disable the Sun Cluster DHCP resource.
# scswitch -n -j resource |
Remove the Sun Cluster DHCP resource.
# scrgadm -r -j resource |
Configure and register the Sun Cluster DHCP resource.
Save the Sun Cluster DHCP resource definitions.
# scrgadm -pvv -j resource > file2 |
Compare the updated definitions to the definitions that you saved before you updated the resource.
Comparing these definitions enables you to determine if any existing extension properties have changed, for example, time-out values.
# diff file1 file2 |
Amend any resource properties that were reset.
# scrgadm -c -j resource -x|y resource |
Bring online the Sun Cluster DHCP resource.
# scswitch -e -j resource |
Instructions for upgrading Sun Cluster HA for Oracle E-Business Suite are omitted from Sun Cluster Data Service for Oracle E-Business Suite Guide for Solaris OS.
Support for Oracle E-Business Suite v11.5.9 is introduced in Sun Cluster 3.1 9/04. Oracle E-Business Suite v11.5.9 introduces the hostname within some path names. If you are upgrading to Oracle E-Business Suite v11.5.9, you must upgrade Sun Cluster HA for Oracle E-Business Suite for use with Oracle E-Business Suite v11.5.9.
Upgrading Sun Cluster HA for Oracle E-Business Suite involves the following tasks:
Removing and reregistering resources for the following server components of Oracle E-Business Suite:
Concurrent Manager Server
Forms Server
Reports Server
Removing and reregistering resources for the following listener components of Oracle E-Business Suite:
Oracle Listener
Concurrent Manager Listener
Bringing online resources for Sun Cluster Oracle E-Business Suite
Perform this task for each server resource that you must remove and reregister, namely:
Concurrent Manager Server resource
Forms Server resource
Reports Server resource
Save the definition of the Oracle E-Business Suite sever resource.
# scrgadm -pvv -j resource > file1 |
Disable the Oracle E-Business Suite sever resource.
# scswitch -n -j resource |
Remove the Oracle E-Business Suite sever resource.
# scrgadm -r -j resource |
Configure and register the Oracle E-Business Suite server resource.
Go to the directory that contains the configuration file and the registration file for the resource.
# cd /opt/SUNWscebs/prefixutil |
Edit the configuration file for the resource.
vi prefix_config |
Run the registration file for the resource.
# ./prefix_register |
prefix denotes the server to which the file applies, as follows:
cmg denotes the Concurrent Manager Server.
frm denotes the Forms Server.
rep denotes the Reports Server .
Compare the updated definitions to the definitions that you saved before you updated the resource.
Comparing these definitions enables you to determine if any existing extension properties have changed, for example, time-out values.
# scrgadm -pvv -j resource > file2 # diff file1 file2 |
Amend any resource properties that were reset.
# scrgadm -c -j <resource>-x | y <resource> |
This task removes and reregisters all the listener resources that you must remove and reregister, namely:
Oracle Listener resource
Concurrent Manager Listener resource
These resources are instances of the SUNW.oracle_listener resource type. For information about this resource type, see Sun Cluster Data Service for Oracle Guide for Solaris OS.
Disable and remove the Sun Cluster Oracle E-Business Suite listener resources.
# scswitch -n -j resource # scrgadm -r -j resource |
Create a resource for the Oracle E-Business Suite Oracle Listener.
In the following example, the copy_env script is used to copy the PROD.env file to PROD_ha.env and to format the PROD_ha.env file. The PROD_ha.env is specified for the User_env extension property of the Oracle Listener resource.
# grep PROD.DBS_ORA816= /var/tmp/config.txt PROD.DBS_ORA816=/global/mnt10/d02/oracle/proddb/8.1.7 # # cd /opt/SUNWscebs/cmg/util # # ./copy_env /global/mnt10/d02/oracle/proddb/8.1.7 PROD # # scrgadm -a -j Oracle-E-Business-Suite-ORALSR-resource \ -t SUNW.oracle_listener \ -g Oracle-E-Business-Suite-failover-resource-group\ -x Listener_name=PROD\ -x ORACLE_HOME=/global/mnt10/d02/oracle/proddb/8.1.7 \ -x User_env=/global/mnt10/d02/oracle/proddb/8.1.7/PROD_ha.env # # scswitch -e -j Oracle-E-Business-Suite-ORALSR-resource |
Create a resource for the Oracle E-Business Suite Concurrent Manager Listener.
In the following example, the copy_env script is used to copy the PROD.env file to PROD_ha.env and to format the PROD_ha.env file. The PROD_ha.env is specified for the User_env extension property of the Concurrent Manager Listener resource.
# grep PROD.CON_ORA806= /var/tmp/config.txt PROD.CON_ORA806=/global/mnt10/d01/oracle/prodora/8.0.6 # # cd /opt/SUNWscebs/cmg/util # # ./copy_env /global/mnt10/d01/oracle/prodora/8.0.6 PROD # # scrgadm -a -j Oracle-E-Business-Suite-CMGLSR-resource \ -t SUNW.oracle_listener \ -x Listener_name=APPS_PROD\ -x ORACLE_HOME=/global/mnt10/d01/oracle/prodora/8.0.6 \ -x User_env=/global/mnt10/d01/oracle/prodora/8.0.6/PROD_ha.env # # scswitch -e -j Oracle-E-Business-Suite-CMGLSR-resource |
For each resource that you are bringing online, type the following command.
# scswitch -e -j <resource> |
Instructions for upgrading Sun Cluster HA for Samba are omitted from Sun Cluster Data Service for Samba Guide for Solaris OS.
As a result of bug fixes, the configuration of Sun Cluster HA for Samba has changed. If you are running Sun Cluster HA for Samba, you must remove and reregister the resources for the following components of Sun Cluster HA for Samba.
Samba component
Winbind component
Perform this task for each Samba resource that you must remove and reregister.
Save the resource definitions.
# scrgadm -pvv -j resource > file1 |
Disable the resource.
# scswitch -n -j resource |
Remove the resource.
# scrgadm -r -j resource |
Configure and register the resource.
Go to the directory that contains the configuration file and the registration file for the resource.
# cd /opt/SUNWscsmb/prefixutil |
Edit the configuration file for the resource.
vi prefix_config |
Run the registration file for the resource.
# ./prefix_register |
prefix denotes the component to which the file applies, as follows:
samba denotes the Samba component.
winbind denotes the Winbind component.
Save the resource definitions.
# scrgadm -pvv -j resource > file2 |
Compare the updated definitions to the definitions that you saved before you updated the resource.
Comparing these definitions enables you to determine if any existing extension properties have changed, for example, time-out values.
# diff file1 file2 |
Amend any resource properties that were reset.
# scrgadm -c -j resource -x|y resource |
Bring online the resource.
# scswitch -e -j resource |
Instructions for upgrading Sun Cluster HA for WebSphere MQ are omitted from Sun Cluster Data Service for WebSphere MQ Guide for Solaris OS.
Additional configuration parameters for Sun Cluster HA for WebSphere MQ are introduced in Sun Cluster 3.1 9/04, as explained in the subsections that follow. If you need to modify the default value of a parameter, or set a value for a parameter without a default, you must upgrade Sun Cluster HA for WebSphere MQ.
The following parameters for configuring the MQ user are introduced in Sun Cluster 3.1 9/04. Default values are defined for theses parameters.
Specifies that unused shared memory segments that mqm creates are to be deleted.
Specifies that user ID mqm is to be used to issue mq commands.
XAResourceManager processing enables WebSphere MQ to manage global units of work with any combination of the following databases:
DB2
Oracle
Sybase
The following parameters for configuring XAResourceManager processing are introduced in Sun Cluster 3.1 9/04. Null values are defined for these parameters.
Specifies the DB2 instance name for XAResourceManager.
Specifies the Oracle home directory for XAResourceManager.
Specifies the Oracle SID for XaResourceManager.
You might deploy a WebSphere MQ queue manager's qmgr files and log files on a global file system. In this situation, rename the strmqm program and the endmqm program to prevent the queue manager from being manually started on another node. If you rename these programs, the Sun Cluster framework manage the startup of WebSphere MQ queue manager. For more information, see Sun Cluster Data Service for WebSphere MQ Guide for Solaris OS.
The following parameters for enabling Sun Cluster to manage the startup of WebSphere MQ queue manager are introduced in Sun Cluster 3.1 9/04. Null values are defined for these parameters.
Specifies the full path name and filename of the renamed strmqm program.
Specifies the full path name and filename of the renamed endmqm program.
If you need to modify the default value of a parameter, or set a value for a parameter without a default, you must remove and reregister the Sun Cluster HA for WebSphere MQ resource for which you are changing the parameter.
Only the USERID=mqm applies to the resources for all components, namely:
Queue Manager component
Channel Initiator component
Command Server component
Listener component
Trigger Monitor component
The remaining parameters that are introduced in Sun Cluster 3.1 9/04 apply only to the resource for the Queue Manager component.
Perform this task for each WebSphere MQ resource that you are modifying.
Perform this task only if you are setting or modifying parameters that are introduced in Sun Cluster 3.1 9/04.
Save the resource definitions.
# scrgadm -pvv -j resource > file1 |
Disable the resource.
# scswitch -n -j resource |
Remove the resource.
# scrgadm -r -j resource |
Configure and register the resource.
Go to the directory that contains the configuration file and the registration file for the resource.
# cd /opt/SUNWscmqs/prefixutil |
Edit the configuration file for the resource.
vi prefix_config |
Run the registration file for the resource.
# ./prefix_register |
prefix denotes the component to which the file applies, as follows:
mgr denotes the Queue Manager component.
chi denotes the Channel Initiator component.
csv denotes the Command Server component.
lsr denotes the Listener component.
trm denotes the Trigger Monitor component.
Only the mgr_config file contains all the parameters that are introduced in Sun Cluster 3.1 9/04. The remaining files contain only the USERID=mqm parameter.
Save the resource definitions.
# scrgadm -pvv -j resource > file2 |
Compare the updated definitions to the definitions that you saved before you updated the resource.
Comparing these definitions enables you to determine if any existing extension properties have changed, for example, time-out values.
# diff file1 file2 |
Amend any resource properties that were reset.
# scrgadm -c -j resource -x|y resource |
Bring online the resource.
# scswitch -e -j resource |
Instructions for upgrading Sun Cluster HA for WebSphere MQ Integrator are omitted from Sun Cluster Data Service for WebSphere MQ Integrator Guide for Solaris OS.
Additional configuration parameters for Sun Cluster HA for WebSphere MQ Integrator are introduced in Sun Cluster 3.1 9/04. If you need to set a value for a parameter, you must upgrade Sun Cluster HA for WebSphere MQ Integrator.
You might deploy a WebSphere MQ queue manager's qmgr files and log files on a global file system. In this situation, rename the strmqm program and the endmqm program to prevent the queue manager from being manually started on another node. If you rename these programs, the Sun Cluster framework manage the startup of WebSphere MQ queue manager. For more information, see Sun Cluster Data Service for WebSphere MQ Guide for Solaris OS.
The following parameters for enabling Sun Cluster to manage the startup of WebSphere MQ queue manager are introduced in Sun Cluster 3.1 9/04. Null values are defined for these parameters.
Specifies the full path name and filename of the renamed strmqm program.
Specifies the full path name and filename of the renamed endmqm program.
If you need to set a value for a parameter , you must remove and reregister the Sun Cluster HA for WebSphere MQ Integrator resource for which you are changing the parameter.
The parameters that are introduced in Sun Cluster 3.1 9/04 apply to the resources for all components, namely:
Broker component
User Name Server component
Perform this task for each WebSphere MQ Integrator resource that you are modifying.
Perform this task only if you are setting or modifying parameters that are introduced in Sun Cluster 3.1 9/04.
Save the resource definitions.
# scrgadm -pvv -j resource > file1 |
Disable the resource.
# scswitch -n -j resource |
Remove the resource.
# scrgadm -r -j resource |
Configure and register the resource.
Go to the directory that contains the configuration file and the registration file for the resource.
# cd /opt/SUNWscmqi/prefixutil |
Edit the configuration file for the resource.
vi prefix_config |
Run the registration file for the resource.
# ./prefix_register |
prefix denotes the component to which the file applies, as follows:
sib denotes the Broker component.
siu denotes the User Name Server component.
Save the resource definitions.
# scrgadm -pvv -j resource > file2 |
Compare the updated definitions to the definitions that you saved before you updated the resource.
Comparing these definitions enables you to determine if any existing extension properties have changed, for example, time-out values.
# diff file1 file2 |
Amend any resource properties that were reset.
# scrgadm -c -j resource -x|y resource |
Bring online the resource.
# scswitch -e -j resource |
This section discusses errors and omissions from the Sun Cluster man pages.
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 9/04 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 |
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.