This test monitors the tables in the eG database and turns the spotlight on the following:

• Large sized tables in terms of the volume of data they store;
• Tables with too many rows of data;
• Tables that are badly structured - i.e., tables without index or tables without primary key

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

• In the PORT text box, specify the port at which the specified HOST listens.

• Specify the port at which the JMX listens for requests from remote hosts in the JMX REMOTE PORT text box. In the <EG_MANAGER_INSTALL_DIR>\manager directory (on Windows; on Unix, this will be the /opt/egurkha/manager directory) of the eG manager, you will find a management.properties file. Set the port defined against the com.sun.management.jmxremote.port parameter of the file as the JMX REMOTE PORT.

• By default, JMX requires no authentication or security. Therefore, the USER, PASSWORD, and CONFIRM PASSWORD parameters are set to none by default.

• The JNDINAME is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have resgistered the JMX connector in the RMI registery using a different lookup name, then you can change this default value to reflect the same in the JNDINAME text box.

• Specify the maximum size limit (in KB) that a table should exceed in order to be counted as a high volume table in the MAXIMUM TABLE SIZE text box.

• Specify the minimum size limit (in KB) that a table should fall below in order to be counted as a low volume table in the MINIMUM TABLE SIZE text box.

• This test reports all tables with more number of rows than the row limit specified in the MAXIMUM ROW SIZE text box as Tables with many rows.

• This test reports all tables with more number of rows than the row limit specified in the MINIMUM ROW SIZE text box as Tables with few rows.

• To make diagnosis more efficient and accurate, the eG system embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability

  • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the Update button will register the changes made.

When changing the configuration for specific servers, a "*" beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a "$" or contain a series of "*". A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.