Skip to content

Archiving process data

Operation of archiving

Collected data can be archived in dedicated database tables, called offline tables, which have the same content as the original data tables. Storing the data offline is useful to reduce the size of the operational database, which can be extremely large at full operation.

Note: the offline tables are indicated with the prefix H_.

When data are archived, they are moved from the original tables to the offline tables. Specific scenarios are created in these tables for this purpose. After the data has been stored offline, the specific scenarios/periods are locked. When all the scenarios/periods of a process are locked, the process itself is locked and stored offline.

The offline storage of the data can be reversed, but this does not automatically unlock the original scenarios/periods.

Note: data stored offline can be used for reporting, but not for data entry or data processing.

Specifics for the HANA database

If you are using a HANA (Hana Data Tiering) database, all the partitions regarding the process scenario/period stored offline will be moved from the HOT area to WARM area to optimise the storage costs. When restoring data, all the partitions regarding the process scenario/period will be moved back to the HOT area.

If the "004203” function is active, the processes page shows the Hot/Warm partition alignment function. You can use this function to realign the partitions between the HOT and WARM areas, based on the status of offline storage of the scenarios/periods of the various processes the partitions refer to.

For example, this function is useful in the following cases:

  • to clone a workspace,
  • to update a workspace based on another workspace to which the user has access,
  • to realign partitions that are incorrectly aligned.