Page tree

Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

To access the Aging configuration page by using the Administration tab, click Data Warehouse then click Aging configuration. It allows you to set some important parameters that affect both the efficiency and the disk space needed by the data warehouse. For each table that stores BMC TrueSight Capacity Optimization metrics, you can set how long the data should be kept and whether to partition the table into smaller chunks if needed.

This page displays a summary of the aging and partitioning configuration for each data table, including:

and buttons to edit, delete or synchronize the configuration.

The Add configuration button on top of the table allows you to define a new aging configuration.

Example of the Aging configuration page

Clicking on the name of a table will display the detail page for that configuration, where you can delete it or edit its settings.

Example of detail page for the SYS_CONF_STAGE table


The Aging parameter defines the number of days that the specific metric value will be kept in the data table, using its timestamp as starting date. It is important to properly tune this parameter, as it can strongly influence the space occupied in each tablespace and the availability of the data for analysis purposes.

For example, let's consider the table SYS_DATA_DETAIL. It holds the system metrics collected at the maximum detail available, given that the duration of the samples is greater or equal to 5 minutes. According to your needs, you can decide to reduce or increase the aging parameter value for this table:

  • A small value will save space because the detailed data will be deleted after a short period of time, but will prevent you from performing detailed analyses
  • A high value will let you perform detailed analyses over more data, but the tradeoff will be a high space consumption and slower performances

The Aging parameter also regulates the data retention period of BMC TrueSight Capacity Optimization. As data is automatically aggregated at different time levels, when the highest level data (usually, WKLD_DATA_MDCH and SYS_DATA_MDCH) becomes old (i.e. its aging period expires) it is deleted and all information about that period of time is lost.

Moreover, the Aging parameter directly affects the maximum age of the data that can be imported in BMC TrueSight Capacity Optimization, i.e. the latency. The latency is specific to the entity and is automatically set equal to the Aging parameter values of the SYS_DATA_DETAIL and WKLD_DATA_DETAIL tables.

Additional information

The latency setting limits the maximum age of data imported by an ETL task: if it is older than the aging policies of the SYS_DATA_DETAIL and WKLD_DATA_DETAIL tables it will be discarded by the warehousing engine and thus become useless.

For example, if the latency is set to six months, the warehousing process only takes into account the data present in a stage table whose timestamp is not older than six months. If the data loaded by an ETL task refers to metrics collected before this date, they will ben ignored by the warehousing engine and will not be reported.

These settings are necessary because the warehousing process has to deal with a great volume of summarizations; establishing limits prevents the process from becoming unmanageable.

Partition period

Another very important parameter that can be set in the Aging Configuration page is the partition period, which allows you to improve the performances of the BMC TrueSight Capacity Optimization DWH by using table partitioning. The partition period is expressed in days and defines the time span of each chunk in which the tables will be partitioned.

To tune this parameter you must consider the specific needs of your BMC TrueSight Capacity Optimization deployment, because this setting speeds up the execution of SQL instructions by limiting it to one partition at a time. Partitions allow smaller indices to query, update and drop table rows. This feature is totally transparent to BMC TrueSight Capacity Optimization users, and a good tuning of the parameter for each table can lead to major speed-ups.

For example, if you want to have a data retention period of three months but your users frequently perform analyses that are based on data from the last two weeks, you could set the partition period to 15 days. This way, most of the queries will be executed only on the last partition, which is much smaller than the whole table.

Adding a new aging configuration

The Add aging configuration form has the following fields:



Table name

Name of the database table for which you want to set an aging configuration

Column name

Name of the database column that contains the data timestamp


How many days should pass before the data is considered old and removed

Partitioned table

Check if you want to partition this table. Selecting this option has the following effect:

  • Enables the Partition period, Partition pattern, Forward, and Tablespace name options.
  • Disables the Additional conditions option.

Partition period

A drop-down menu that lets you select the time span for the partition chunk, e.g. year, semester, month, etc.

Partition pattern

A drop-down menu that lets you select the pattern for the name that will be assigned to every chunk of the table


How many days in advance the partition should be created

Tablespace name

The name of the tablespace to which the table belongs

Additional conditions

Additional filtering conditions for data deletion that can be used only with unpartitioned tables. For example, in the case of stage tables aging, you can express the additional condition and status>0 to avoid deletion of data not yet processed by the warehousing engine.

Adding a new aging configuration