Table of Contents

Search

  1. Abstract
  2. Supported Versions
  3. Writing Custom Scripts to Run Batch Jobs

Writing Custom Scripts to Execute Batch Jobs

Writing Custom Scripts to Execute Batch Jobs

Cascade Delete

Cascade Delete

The Hub Delete job performs a
cascade delete
if you set the parameter IN_ALLOW_CASCADE_DELETE=1 for a base object in the stored procedure. With cascade delete, when records in the parent object are deleted, Hub Delete also removes the affected records in the child base object. Hub Delete checks each child base object table for related data that should be deleted given the removal of the parent base object record.
If a many-to-many parent child relationship exists between records, some parents may lose their child records during a cascde delete. Consider a scenario where two parent records share the same child record, and you delete one of the parent records. The associated child record is cascade deleted and the other parent record is left without its child record.
For the prior example, the Hub Delete job may potentially delete XREF records from other source systems. To ensure that Hub Delete does not delete XREF records from other systems, do not use cascade delete. IN_ALLOW_CASCADE_DELETE forces Hub Delete to delete the child base objects and cross-references (regardless of system) when the parent base object is being deleted.
  • If you do not set the IN_ALLOW_CASCADE_DELETE=1, Informatica MDM Hub generates an error message if there are child base objects referencing the deleted base objects record; Hub Delete fails, and Informatica MDM Hub performs a rollback operation for the associated data.
  • IN_CASCADE_CHILD_SYSTEM_XREF=1 is not supported.

0 COMMENTS

We’d like to hear from you!