To configure the primary companion asymmetrically, issue this command from the secondary companion:
sp_companion “primary_server_name", configure, NULL, login_name, password
primary_server_name is the name of the primary Adaptive Server as defined in the interfaces file entry and in sysservers.
login_name is the name of the user performing this cluster operation (this person must have the ha_role).
password is the password of the person performing this cluster operation.
You must execute the above command only from
the secondary companion.
This example configures an Adaptive Server named MONEY1 as a primary companion. Issue the following command from the secondary server PERSONNEL1:
sp_companion "MONEY1", configure, NULL, sa, Odd2Think
Server 'PERSONNEL1' is alive and cluster configured. Step: Access verified from Server:'PERSONNEL1' to Server:'MONEY1' Server 'MONEY1' is alive and cluster configured. Step: Access verified from Server:'MONEY1' to Server:'PERSONNEL1' (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 'PERSONNEL1' and 'MONEY1' 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 are created during the sp_companion configuration, 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
