Diagnostics database archiving guide
statistical information correctly. . These updated values from the meta table are used by the archiving mechanism to clean up the disk space.
However, calling VACUUM FULL operation is not suggested from the product binaries as it takes exclusive locks on the tables.Therefore, it is often observed that in a heavily accessed system, the disk size eventually grows as archiving is not able to fetch the updated data related to pages and rows in the absence of VACUUM FULL operation.
Configurable parameters of DBConfig.xml
The DBConfig.xml is configuration file for databases used by SysFaultMgmt. This file contains the parameters for configurations of both LOGDB and evweb DB. These configurations together will decide when the archival activity should be triggered. The administrator can modify this file but should not modify any of the XML tags. The administrator should modify only the values of the tags as and when required.
Note: the page size for all databases mentioned here is 8 kB.
|
|
|
|
| Xml Field Names | Max Values | Min Values |
| Default Values | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1. |
|
|
| MaxNumPagesAllowed(LOGDB) |
| 400 |
| 10 |
|
| 140 |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2. |
|
|
| DBRecordLifeTime (LOGDB) | 10 |
| 1 |
|
| 10 |
| ||
|
|
|
|
|
|
|
|
|
|
|
|
| |
3. |
|
|
| ArchedRecordLifetime (LOGARCHDB) | 365 |
| 30 |
|
| 365 |
| ||
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
| ||
4. |
|
|
| ArchDBSize (LOGARCHDB) | 400 |
| 10 |
| 340 |
| |||
|
|
|
|
|
|
|
|
|
|
|
| ||
5. |
|
|
| MaxNumPagesAllowed (evweb DB) | 400 |
| 10 |
|
| 100 |
| ||
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
| ||
6. |
|
|
| DBRecordLifeTime (evweb DB) |
| 10 |
| 1 |
| 10 |
| ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 7. |
|
|
| ArchedRecordLifetime (evweb_history) | 365 |
| 30 |
|
| 365 |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The
1.MaxNumPagesAllowed (LOGDB) - Argument is NUMBER OF PAGES: It indicates the maximum number of pages that the current database can hold.
2.DBRecordLifeTime (LOGDB) - Argument is NUMBER OF DAYS: As the max threshold time is 7 days, 10 days would be sufficient for this parameter. If any of the conditions hit, then the records will be moved to Archive DB.
3.ArchedRecordLifetime (LOGARCHDB) - Argument is NUMBER OF DAYS: It includes number of days, which is spent in CURRENT DB also. It will be desirable to have records of one year.
4.ArchDBSize (LOGARCHDB) - Argument is NUMBER OF PAGES: A value of 340 would be sufficient for this parameter.
Following are the Archival parameters for evweb & evweb_history:
5.MaxNumPagesAllowed (evweb DB) - Argument is NUMBER OF PAGES: It indicates the maximum number of pages that the current database size can grow before history management can move the events to history
7