Product Features

Data Lifecycle Management (DLM) is designed to reduce the size and improve the performance of a Temenos Transact database by moving non-transactional, historical data to a separate Read-Only (RO) database. Temenos Transact Copy and Purge services maintain the movement of data from the LIVE database to RO database depending on the retention period definitions. The performance of the RO database is also optimized through the archiving of older historical data. DLM product provides features such as space reclamation, promoted column support, RO to ARC movement, Customer Data Protection, Retry Process, RO Delete Operation and Schema separation and this section explains these features.

DLM Implementation Methods

This section provides a brief overview about the two methods in which Data Life Cycle Management (DLM) can be implemented.

Space Reclaim

When large amount of data from the LIVE database are moved into DLM database, storage space occupied by the moved data will be freed in the LIVE database. This section explains you in detail the best practices to be followed for reclaiming the space freed in Oracle and SQL databases and various space reclamation methods.

Promoted Columns

A single value field (or even a specific value of a multi-valued field), which is a part of XMLRECORD, can be promoted as a computed column of the table and used in relational search conditions. Furthermore, a relational index can be created on the computed column to improve the query performance. This section provides details about the setup and script execution for various databases.

Moving Data from RO to ARC

Archiving of data from the Non-Volatile database (NVDB) read-only (RO) tables to archival (ARC) tables is possible by specifying the retention period (number of months). You can stop the data archival for some tables by excluding them from the archiving process. This section provides brief about the archival process methods, configuration of DLM RO database archival tables for various databases and data movement from RO to ARC database.

Customer Data Protection

Customer Data Protection (CDP) ensures that customer data is erased from all data storages on request. DLM supports data erasure in the RO database as part of CDP. This section provides the details about the applications or processes involved in the DLM CDP erasure process with sample screen captures.

Retry Process

Retry mechanism is introduced to reprocess the record(s), which failed already during DL.COPY.PROCESS and DL.PURGE.PROCESS. The failed records are captured in RO.ERROR.KEYLIST. This section provides details on how this process works.

Delete Operation

In Trickle feed mechanism, data from Temenos Transact LIVE database are moved to DLM without retention period. If a Temenos Transact record is deleted, its DLM counterpart must be deleted as well. However, you cannot delete records from DLM directly, since it is a RO database. To delete respective records in DLM, you need to capture the deleted IDs in DLM.DELETE.PROCESS.LIST file and execute the DLM.DELETE.PROCESS service. This section provides details about the records deletion process in DLM.

Schema Separation

Schema separation in transact system allows to store tables with respect to the company and/or to categories the Temenos Transact tables based on the functional nature. This will help the customers to have better control over the Temenos Transact tables from database level. This section provides details about the schema separation configuration and sample screen captures of the scripts with and without schema separation.