Table of Contents


  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Configuring the Audit Trail for a Staging Table

Configuring the Audit Trail for a Staging Table

Informatica MDM Hub
allows you to configure an audit trail that retains the history of the data in the RAW table based on the number of Loads and timestamps.
This audit trail is useful, for example, when using HDD (Hard Delete Detection). By default, audit trails are not enabled, and the RAW table is empty. If enabled, then records are kept in the RAW table for either the configured number of stage job executions or the specified retention period.
The Audit Trail has very different functionality from—and is not to be confused with—the Audit Manager tool.
To configure the audit trail for a staging table:
  1. Start the Schema Manager.
  2. Acquire a write lock.
  3. If you have not already done so, add a mapping for the staging table.
  4. Select the staging table that you want to configure.
  5. At the bottom of the properties panel, click
    Preserve an audit trail in the raw table
    to enable the raw data audit trail.
    The Schema Manager prompts you to select the retention period for the audit table.
  6. Selecting one of the following options for audit retention period:
    Number of batch loads for which to retain data.
    Time Period
    Period of time for which to retain data.
  7. Click
    to save your changes.
Once configured, the audit trail keeps data for the retention period that you specified. For example, suppose you configured the audit trail for two loads (Stage job executions). In this case, the audit trail will retain data for the two most recent loads to the staging table. If there were ten records in each load in the landing table, then the total number of records in the RAW table would be 20.
If the Stage job is run multiple times, then the data in the RAW table will be retained for the most recent two sets based on the ROWID_JOB. Data for older ROWID_JOBs will be deleted. For example, suppose the value of the ROWID_JOB for the first Stage job is 1, for the second Stage job is 2, and so on. When you run the Stage job a third time, then the records in which ROWID_JOB=1 will be discarded.
Using the Clear History button in the Batch Viewer after the first run of the process:If the audit trail is enabled for a staging table and you choose the Clear History button in the Batch Viewer while the associated stage job is selected, the records in the RAW and REJ tables will be cleared the next time the stage job is run.


We’d like to hear from you!