eG Database Partitions Test

Database partitioning feature if enabled on the eG database lets the eG manager automatically create separate partitions on the database for every single day. This helps the manager to automatically store the data pertaining to a particular day into the partition created for that day. During cleanup process, the partitions for the selected days are dropped i.e., the data stored in that partition is deleted without multiple data seeks on the database. This enables the cleanup process to be more faster and efficient.

In some environments where a large number of measurements were collected and stored in the eG database on which database partitioning feature is enabled, database cleanup took a long time. Sometimes, administrators may have upgraded the eG manager or the eG backend database from a version that did not support the database partitioning feature. In such cases, the tests/diagnosis tables that existed prior to the upgrade will not be partitioned after upgrade. Hence, administrators found it difficult to identify those tables on which partitions have not been created. To aid administrators in this regard, eG Enterprise offers the eG Database Partitions test.

This test monitors the eG backend database and reports if the database partitioning feature is supported on the database. If this database partitioning feature is supported, this test additionally reports the count of tables that were partitioned and were not partitioned. Further, the detailed diagnostics lists the tables that were partitioned and were not partitioned.


The database partitioning feature is presently available only when the following databases are used as the eG backend database:

  • Microsoft SQL Server Enterprise Edition

  • Databases hosted on Microsoft Azure Cloud

  • Microsoft SQL 2016 and above (both Web and Standard Editions)

  • Oracle Database 12c Enterprise Edition

Target of the test : The eG Manager

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for the eG manager being monitored

Configurable parameters for the test



Test period

How often should the test be executed .


The host for which the test is to be configured.


The port number at which the specified host listens.

JMX Remote Port

Here, specify the port at which the JMX listens for requests from remote hosts. 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 file. Set the port defined against the parameter of the file as the JMX Remote Port.

JMX User, JMX Password, and Confirm Password

By default, JMX requires no authentication or security. Therefore, the JMX User, JMX 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 registered the JMX connector in the RMI registry using a different lookup name, then you can change this default value to reflect the same.


This test uses a JMX Provider to access the MBean attributes of the eG manager and collect metrics. Specify the package name of this JMX Provider here. By default, this is set to com.sun.jmx.remote.protocol.


Specify the duration (in seconds) for which this test should wait for a response from the eG manager. If there is no response from the eG manager beyond the configured duration, the test will timeout. By default, this is set to 240 seconds.

DD Frequency

Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise 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. 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 normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Is database partitioning supported?

Indicates whether/not database partitioning feature is supported.


The values that this measure reports and the numeric values that correspond to them have been discussed in the table below:

Measure Value Numeric Value
Yes 1
No 0


By default, this measure reports the Measure Values listed in the table above to indicate whether/not database partitioning feature is supported. The graph of this measure however, represents the same using the corresponding numeric equivalents only.

Partitioned tables

Indicates the number of tables that were partitioned.



The detailed diagnosis of this measure lists the name of the tables that were partitioned and the date until which the partition has been created.

Non-partitioned tables

Indicates the number of tables on which partitions have not been created.


The tables that were existing on the database may not be partitioned if the eG backend database / eG manager is upgraded from a lower version (that does not support database partitioning feature). However, the tables created on the database after the upgrade will be partitioned if the database supports database partitioning feature.

The detailed diagnosis of this measure lists the name of the tables on which partitions have not been created.

Partition configuration missing tables

Indicates the number of partitioned tables for which the date until which the partition has been created is missing.


By default, the date until which partitions were created for each table that is partitioned is maintained in the [PARTITIONED_TABLES] section of the eg_dbase.ini file available in the <eG_INSTALL_DIR/manager/config> folder. If this date is unavailable for one/more tables, then, the counter of this measure will be incremented. Also, if this date has not been specified, then, even though the table has been partitioned, the data will be stored at random locations in the eG database. Hence, the cleanup process will require more data seeks to the database may take too long to complete.

The detailed diagnosis of this measure lists the name of the tables for which the date until which the partition has been created is missing.