Use sp_companion to configure the primary companion for asymmetric configuration:
sp_companion "primary_server_name", configure, with_proxydb, login_name, password, cluster_login, cluster_password
Where:
primary_server_name is the name of the primary Adaptive Server as defined in the interfaces file entry and in sysservers.
with_proxydb indicates that proxy databases are created on the secondary companion for all databases other than system databases. Any subsequent databases that are added also create proxy databases.
login_name is the name of the user performing this cluster operation (must have the ha_role).
password is the password of the person performing this cluster operation
cluster_login is the name of the user logging into this cluster.
password is the password of the person logging into this cluster.
This example configures an Adaptive Server named PERSONNEL1 as a secondary companion (for more information about the syntax, see the Adaptive Server Reference Manual and your SGI documentation):
sp_companion "PERSONNEL1", configure, with_proxydb, null, sa, Odd2Think
Server 'MONEY1' is alive and cluster configured. Step: Access verified from Server:'MONEY1' to Server:'PERSONNEL1' Server 'PERSONNEL1' is alive and cluster configured. Step: Access verified from Server:'PERSONNEL1' to Server:'MONEY1' (1 row affected) (1 row affected) (1 row affected) (1 row affected) (1 row affected) (1 row affected) ..... Step: Companion servers configuration check succeeded Step: Server handshake succeeded Step: Master device accessible from companion Step: Added the servers 'MONEY1' and 'PERSONNEL1' for cluster config Step: Server configuration initialization succeeded Step: Synchronizing server logins from companion server Step: Synchronizing remoteserver from companion server Step: Synchronizing roles from companion server Step: Synchronizing server-wide privs from companion server Step: User information syncup succeeded Step: Server configured in normal companion mode
If user databases already exist while you are using sp_companion, you see messages similar to these:
Step: Created proxy database ‘pubs2’ Step: Proxy status for database has been set. Please Checkpoint the database 'pubs2' Step: Server configured in normal companion mode” Starting companion watch thread
See Chapter 3, “Asymmetric and Symmetric Setup,” for more information about asymmetric configuration.
