The syntax for sp_companion do_advisory is:
sp_companion server_name, do_advisory [, all | help | group_attribute_name | base_attribute_name ]
where:
server_name is the name of the remote Adaptive Server.
all indicates that you want information about both the group and the base attributes.
help prints the sp_companion do_advisory syntax and a list of the group and base attributes
group_attribute_name is the name of the group attribute upon which you want sp_companion to report.
base_attribute_name is the name of the base attribute upon which you want sp_companion do_advisory to report.
sp_companion do_advisory output includes:
Attribute name – The name of the attribute that sp_companion do_advisory is investigating.
Attribute type – The type of attribute. For example, the type might be CIS, disk i/o, General Config (these are the configuration parameters set in the server_name.cfg file).
Local value – The value of the attribute on the companion from which you entered sp_companion do_advisory command.
Remote value – The value of the attribute on the remote companion.
Advisory – After accessing the attributes on the two companions, sp_companion do_advisory prints its findings in the Advisory column. The values in this column are:
0 – The attributes will not affect the cluster operation.
1 – The attributes are not configured for the best configuration, but they will not prevent a cluster operation.
2 – The attributes need to be altered before proceeding with the cluster operation.
For example, the following checks the attributes between Adaptive Servers MONEY1 and PERSONEL1:
sp_companion "MONEY1", do_advisory, ‘all’ go
Attribute Name Attrib Type Local Value Remote Value Advisory -------------- ----------- ----------- ----------- ------ cis connect time CIS 1 0 2 cis rpc handling CIS 1 0 2 max cis remote se CIS 10 25 2 (1 row affected) (return status = 0)
In this example, the attributes cis connect, cis rpc handling, and max cis remote servers all have a value of 2 under the Advisory column, which indicates that these attributes will prevent a successful companion configuration between MONEY1 and PERSONEL1. Note that the Local Values for these three attributes are different from the Remote Values. The companions must be re configured to have the same or compatible values.
