|
Measures reported by EgDBPartitionTest
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 EgDBPartitionTest.
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.
Note:
The database partitioning feature is presently available only when the following databases are used as the eG backend database:
Outputs of the test: One set of results for the eG manager being monitored.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Status |
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 |
Note:
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.
|
| PartitionedTables |
Indicates the number of tables that were partitioned. |
Number |
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.
|
| NonPartitionedTests |
Indicates the number of tables on which partitions have not been created. |
Number |
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.
|
| PartitionMissedTests |
Indicates the number of partitioned tables for which the date until which the partition has been created is missing. |
Number |
The detailed diagnosis of this measure lists the name of the tables on which partitions have not been created.
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 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.
|
|