Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.5 HotFix 2
  • All Products

Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Glossary

Configuration Guide

Configuration Guide

Back Next

Hard Delete Detection Table

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.
0 COMMENTS
We’d like to hear from you!