Configuration Guide

10.3 HotFix 2
- 10.5 HotFix 2
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 3
- 10.3 HotFix 1
- 10.3

Back Next

Hard Delete Detection Table

The hard delete detection table is a repository table that you create to store metadata that the

MDM Hub

requires to detect hard deletes in source systems. The name of the hard delete detection table is C_REPOS_EXT_HARD_DEL_DETECT.

The following table describes the columns of the hard delete detection table:

Column Name	Datatype and Size in Bytes	Description
ROWID_TABLE	CHAR (14)	Contains values of the ROWID_OBJECT column of the staging table for which hard deleted records need to be detected. The ROWID_TABLE column cannot have a null value.
HDD_ENABLED	INTEGER	Enables or disables the MDM Hub to detect hard deletes for a staging table. The HDD_ENABLED column cannot have a null value. Use one of the following values: 0. Enables the MDM Hub to detect hard deletes. 1. Disables the MDM Hub to detect hard deletes. Default is 0.
HDD_TYPE	VARCHAR2 (14)	Indicates the type of hard delete for the staging table. Use one of the following values for the hard delete type: DIRECT. Performs the direct hard delete of the base object record. CONSENSUS. Performs the consensus based hard delete of the base object record.
DELETE_FLAG_ COLUMN_NAME	VARCHAR2 (30)	Name of the staging table column that contains the value of the delete flag for any hard-deleted records that the MDM Hub detects.
DELETE_FLAG_VAL_ ACTIVE	VARCHAR2 (14)	Value of the delete flag column for active records.
DELETE_FLAG_VAL_ INACTIVE	VARCHAR2 (14)	Value of the delete flag column for inactive records.
DELETE_FLAG_VAL_ PARTIAL	VARCHAR2 (14)	Value of the delete flag column for the partial delete in a consensus delete scenario.
HAS_END_DATE	INTEGER	Indicates whether the staging table has an end date column. The HAS_END_DATE column cannot have a null value. Use one of the following values: 0. Staging table does not have an end date column. 1. Staging table has an end date column. Default is 0.
END_DATE_COLUMN_NAME	VARCHAR2 (30)	Name of the end date column. The MDM Hub uses the column when HAS_END_DATE=1.
END_DATE_VAL	DATE	Value to use for the end date. If the implementation requires that you hard-code an end date value, then that value is stored in the END_DATE_VAL column in the MM/DD/YYYY format. Default is SYSDATE.
TRAN_HDD_ENABLED	INTEGER	Indicates whether the process to detect hard deletes is transactional. The TRAN_HDD_ENABLED column cannot have a null value. Use one of the following values: 0. The process to detect hard delete is not transactional. 1. The process to detect hard deletes is transactional and does not compare the full load against the previous landing and landing table. Default is 0.
HDD_LANDING_PKEY_COLUMNS	VARCHAR	Optional. If you use a function to concatenate the primary key from multiple source columns, and the inputs to the function include some source columns that do not contribute to the primary key, add the HDD_LANDING_PKEY_COLUMNS column to the table. In a comma-separated list, specify the source columns that contribute to the primary key. The hard delete detection process tracks changes on the specified source columns, instead of all the source columns that are inputs to the function.
EMPTY_LANDING_TABLE_CHECK_OFF	INTEGER	Optional. Indicates whether the process to detect hard delete checks for an empty landing table. Use one of the following values: 0. The process to detect hard delete checks for an empty landing table. 1. The process to detect hard deletes does not check for an empty landing table. Default is 0. Informatica recommends that you keep this value set to 0. A value of 1 means that the MDM Hub does not check for an empty landing table, which might cause all records associated with the source system of the landing table being marked for deletion.

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

Hard Delete Detection Table

Hard Delete Detection Table