5.14 Database usage

The page shows data usage and retention configuration related information and it can be used to estimate the required Oracle tablespace size for PVSR. The page is divided into four parts:

·       Database usage: the table shows the current database usage of the different types of data stored in the database

o   Raw data: measured values

o   Hourly averages: PVSR calculates hourly averages specified by the “retain raw data” parameter configured for each measurement, except when it is configured to periodically create new storage tables (see the Measurement result storage options section for more details). This cell shows the database space used by these hourly averages

o   Audit trail entries: data shown on the Audit trail page

o   Alarms: alarm violations

o   Reports: calculated report values

o   Others: any other table used by PVSR

·       Data purge options: the configured data retentions in the CONFIG_INI.pm file

o   Hourly averages: DELETE_DAILY_DATA_AFTER

o   Alarms: VIOLATION_DELETE_AFTER

o   Reports: REPORT_DELETE_AFTER

o   Audit trail entries: AUDIT_TRAIL_DELETE_AFTER

o   New data table interval: CREATE_PP_TABLE_AFTER

o   Drop data table: DROP_DATA_AFTER

·       Measurement data storage configuration: this table tries to give an estimation about the required size based on the current measurement retention configuration. For each measurement interval – data retention setting pair the table shows a separate row including the number of measurements and the required tablespace size. It is important to mention that if the measurement is irregular (it does not have a fix collection cycle) then PVSR cannot know how often measurement values will arrive into the system. In this case it uses the “expect data in” parameter to do the estimation

·       The last part of the page shows a chart depicting the database usage in the future based on the current configuration