You must load the high availability services library for Sun Cluster.
First, verify that the high availability services library is available. Use isql to connect to any Adaptive Server:
sp_companion "MONEY1", show_cluster
You see:
The default cluster is: SC. The current cluster is set to default. Supported cluster systems for SunOS are: SC VCS
Set the high availability services library for SC3.0. For example, from PERSONNEL1, enter:
sp_companion "MONEY1", set_cluster, "SC"
The current cluster is set to SC.
Check the interaction of Adaptive Server with the underlying cluster system. From PERSONNEL1, enter:
sp_companion
Server 'PERSONNEL1' is alive and cluster configured. Server 'PERSONNEL1' is configured for HA services. Server 'PERSONNEL1' is currently in 'Single server' mode.
Perform these steps from only one of the servers in
the cluster. The high availability services library is populated
to another Adaptive Server in the cluster. If the high availability
services library has been loaded on another Adaptive Server, you
see the following when you issue sp_companion on server
MONEY1:
Server 'MONEY1' is alive and cluster configured. Server 'MONEY1' is configured for HA services. Server 'MONEY1' is currently in 'Single server' mode.
Since the two companion servers synchronize user information to remove any potential conflict, there should be no user login and password used for thorough probe on secondary companion server. If they do exist, both sp_companion configure and sp_companion do_advisory fail during the user information synchronization process,
To drop the user and login of user probe in the secondary companion server, use sp_dropuser and sp_droplogin.
