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

Hub Delete Jobs

Hub Delete Jobs

The Hub Delete job removes specified data—up to and including an entire source system—from Informatica MDM Hub based on your XREF table input to the CMXDM.HUB_DELETE_BATCH stored procedure.
The XREF input table must contain either the primary key (ROWID_XREF) or the source system key (PKEY_SRC_OBJECT and ROWID_SYSTEM) of the cross-reference records to be deleted. If the XREF table contains both, the primary key and the source system key, then only the primary key is used to identify the records to be deleted. The Hub Delete job is faster when you use ROWID_XREF to identify the records to be deleted.
If you are deleting all records from a specific source system and cascade delete is enabled, then you must specify the XREFs of the specific source system as input to the cmxdm.hub_delete_batch stored procedure. All the parent records that belong to the specific source system are deleted but in the case of the child records that are cascaded to, XREFs and base objects that do not belong to the specified source system are also deleted.
After a Batch Delete job completes, temporary tables must be removed by using the following command:
cmxut.drop_table_in_list(OUT_TMP_TABLE_LIST,OUT_ERROR_MESSAGE,RC);
The Hub Delete batch job will not delete the data if there are records queued for an Automerge job.
Do not run a Hub Delete job when there are automerge records in the match table. Run the Hub Delete job after the automerge matches are processed.

0 COMMENTS

We’d like to hear from you!