Monitoring and Diagnostic (MDA) tables

The installmontables script for installing Monitoring and Diagnostic tables (MDA) has been modified to now use the materialized parameter when defining the MDA proxy tables. This change results in improved performance for many queries using the MDA tables, making it no longer necessary to define a “loopback” remote server in your sysservers table in order to use the MDA tables.

Sybase recommends you reinstall the MDA tables using the installmontables script contained in this release.

Make these changes to use the MDA tables to monitor remote servers:

1. Update the installmontables script by changing all occurrences of “materialized” to “external procedure.”

2. Modify the at clause in the proxy table definitions in the installmontables script to add the name of the remote server followed by the string "..." before the MDA RPC name.

3. You can identify MDA RPC names by the “$” (dollar sign) preceding the name. The remote server name must be the same as the remote server name as it appears in the interfaces file on the server where the MDA tables are installed.

   For example, for the monState table definition, if your remote server name appearing in the interfaces file is SALESPROD, change:

   at "$monState"
   

   to:

   at "SALESPROD...$monState"
   

If the remote server has not already been registered with the server on which you are installing the MDA tables, use the sp_addserver stored procedure to do so.

When installing the MDA tables in order to reference a remote server as described above, be sure to use the version of the installmontables script that came with the version of the Adaptive Server Enterprise installed at the remote server.

Use of the materialized directive has changed the way some error messages from the MDA tables are sent to the client application. If all configuration parameters required by an MDA table used in a query are not enabled, then the client application receives an error message.