Since Adaptive Server supports both Solaris SC2.2 and SC3.0, you must load the high availability services library for SC3.0 since the high availability services library for SC2.2 is the default.
First, verify that the high availability services library is available. Use isql to connect to any Adaptive Server:
sp_companion "MONEY1", show_cluster
Returns message:
The default cluster is: SC-2.2. The current cluster is set to SC-3.0. Supported cluster systems for SunOS are: SC-2.2 VCS-1.3.0 SC-3.0
Set the high availability services library for SC3.0. For example, from PERSONEL1, enter:
sp_companion "MONEY1", set_cluster, "SC-3.0"
The current cluster is set to SC-3.0.
Check the interaction of Adaptive Server with the underlying cluster system. From PERSONEL1, enter:
sp_companion
Server 'PERSONEL1' is alive and cluster configured. Server 'PERSONEL1' is configured for HA services. Server 'PERSONEL1' is currently in 'Single server' mode.
Perform these steps from only one of the servers in
the cluster. The high availability services library is automatically
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, the user login and password used for thorough probe on secondary companion server should not exist. If they do, during the user information synchronization process, both sp_companion configure and sp_companion do_advisory fail.
To drop the user and login of user probe in the secondary companion server, use sp_droplogin and sp_dropuser.
