Administration Runtime Issues and Bugs

HA Oracle Instances Will Not Start If SCI Interconnect Disabled (4823212)

Oracle instances will not start if an SCI cluster interconnect on one cluster node is disabled using the scconf -c -A command.

HA Oracle Stop Method Times Out (4644289)

If you are running Solaris 9, include the following entries in the /etc/nsswitch.conf configuration files on each node that can be the primary for oracle_server or oracle_listener resource so that the data service starts and stops correctly during a network failure:

passwd: files
groups: files
publickey: files
project:  files

The Sun Cluster HA for Oracle data service uses the super user command, su(1M), to start and stop the database. The network service might become unavailable when a cluster node's public network fails. Adding the above entries ensures that the su command does not refer to the NIS/NIS+ name services.

SAP liveCache Stop Method Times Out (4836272)

If you are running Solaris 9, include one of the following entries for the publickey database in the /etc/nsswitch.conf configuration files on each node that can be the primary for liveCache resources so that the data service starts and stops correctly during a network failure:

publickey: 
publickey:  files
publickey:  files [NOTFOUND=return] nis 
publickey:  files [NOTFOUND=return] nisplus

The Sun Cluster HA for SAP liveCache data service uses the dbmcli command to start and stop the liveCache. The network service might become unavailable when a cluster node's public network fails. Adding one of the above entries, in addition to updates documented in Sun Cluster 3.1 Data Service for SAP liveCache Guide ensures that the su command and the dbmcli command do not refer to the NIS/NIS+ name services.

HA Oracle Listener Probe Timeouts (4900140)

On a heavily loaded system, the Oracle listener probe might time out. To prevent the Oracle listener probe from timing out, increase the value of the Thorough_probe_interval extension property. The time-out value of the Oracle listener probe depends on the value of the Thorough_probe_interval extension property. You cannot set the time-out value of the Oracle listener probe independently.

HA-Siebel Does Not Automatically Restart Failed Siebel Components (4722288)

Sun Cluster HA-Siebel agent does not monitor individual Siebel components. If the failure of a Siebel component is detected, only a warning message is logged in syslog.

To work around this, restart the Siebel server resource group in which components are offline using the command scswitch -R -h node -g resource_group.

xserver_svc_start Reports xserver Unavailable During Start-up (4738554)

The message “SAP xserver is not available” is printed during the start up of SAP xserver due to the fact that xserver is not considered to be available until it is fully up and running.

Ignore this message during the startup of the SAP xserver.

xserver Resource Cannot be Configured as a Failover Resource (4836248)

Do not configure the xserver resource as a failover resource. The Sun Cluster HA for SAP liveCache data service does not failover properly when xserver is configured as a failover resource.

To Utilize Monitor_Uri_List, Type_version Must Be Set to 4 (4924147)

To utilize the Monitor_Uri_List extension property of Sun Cluster HA for Apache and Sun Cluster HA for Sun ONE Web Server, you must set the Type_version property to 4.

You can also upgrade the Type_version property of a resource to 4 at any time. For information on how to upgrade a resource type, see “Upgrading a Resource Type” in Sun Cluster 3.1 Data Service Planning and Administration Guide.

The su Command Resets the Project Identifier (4868654)

Some data services run the su command to set the user identifier (ID) to a specific user. For the Solaris 9 operating environment, the su command resets the project identifier to default. This behavior overrides the setting of the project identifier by the RG_project_name system property or the Resource_project_name system property.

To ensure that the appropriate project name is used at all times, set the project name in the environment file of the user. One method to set the project name in the user's environment file is to add the following line to the .cshrc file of the user:

/usr/bin/newtask -p project-name -c $$

project-name is the project name that is to be used.