Purge DPH tables during tenant clone
Learn more about why and when you must purge your DPH tables if you request a tenant data clone.
If you're using Reltio Data Pipeline Hub (DPH) and request a tenant data clone, you must purge your DPH tables before or immediately after the clone completes.
Important: Reltio does not have access to customer-maintained DPH tables. You are responsible for purging these tables as part of your tenant clone process.
What is it?
DPH tables store stateful pipeline execution data for your tenant. These tables are not reset or purged automatically during a tenant clone process.
Who is it for?
This guidance is for technical teams who manage DPH-enabled tenants and participate in cloning or environment provisioning workflows.
Why would I use it?
If old DPH data is left in place during a clone, it can interfere with the cloned environment and cause:
- Duplicate processing of pipeline jobs
- Outdated results or stale outputs
- Pipeline execution errors due to inconsistent state
When and where would I use it?
You should purge DPH tables in either of the following situations:
- Before the tenant clone begins, to ensure a clean export
- Immediately after cloning completes, and before activating any pipelines in the new environment
How does it support business goals?
Purging DPH tables ensures a clean transition between environments and helps you:
- Maintain data processing integrity
- Avoid operational risks from inherited pipeline state
- Support safe testing, onboarding, or environment replication