Before doing sp_companion do_advisory and sp_companion configure:
Disable the monitoring of secondary ASE server: scswitch -n -M -j secondary-resource
Drop the user and login for monitor for secondary ASE server: sp_droplogin secondary_probe_ase sp_dropuser secondary_probe_ase
where secondary_probe_ase is the login and user created in the previous section “Adding user and login for monitoring”.
After successfully executing commands sp_companion do_advisory and sp_companion configure for asymmetric configuration (see the two sections below for detail), do the following steps:
Add the user and login for monitor for secondary ASE server:
sp_addlogin secondary_probe_ase, secondary_probe_passwd sp_adduser secondary_probe_ase
where secondary_probe_ase is the login and user created in the previous section “Adding user and login for monitoring”.
Enable monitoring of secondary ASE server: scswitch -e -M -j secondary-resource
You must configure the secondary companion with sufficient resources to perform the work of both servers during failover. The secondary companion may have attributes that will prevent a successful cluster operation. For example, if both the primary and secondary companions are configured for 250 user logins, during failover, the secondary companion has only the resources for half the number of potential user logins necessary. Instead, both MONEY1 and PERSONEL1 should be configured for 500 user logins (requires 250 users on each).
The sp_companion do_advisory option checks the configuration options on both companions to verify that a cluster operation (such as configuring an Adaptive Server as a secondary companion) will be successful. sp_companion do_advisory advises you of any configuration options that should be changed.
See Chapter 6, “Running do_advisory,” in for a complete description of the sp_companion do_advisory option.
