Before executing sp_companion do_advisory and sp_companion configure:
Disable the monitoring of the secondary Adaptive Server:
scswitch -n -M -j secondary-resource
Drop the user and login for monitor for the secondary Adaptive Server, where secondary_probe_ase is the login and user created in “Adding user and login for fault monitor”:
sp_dropuser secondary_probe_ase sp_droplogin secondary_probe_ase
After successfully executing sp_companion do_advisory and sp_companion configure for an asymmetric configuration (see the two sections below for detail), perform the following steps:
Add the user and login for monitor for secondary Adaptive 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 “Adding user and login for fault monitor”.
Enable monitoring of secondary Adaptive 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 the resources for only half the number of potential user logins necessary. Instead, configure both MONEY1 and PERSONNEL1 for 500 user logins.
sp_companion do_advisory checks the configuration options on both the primary and the secondary companion to make sure 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” for a complete description of the sp_companion do_advisory option.
