NPDL26 — transformed at source.
The Non-Production Data Loader applies deterministic, referentially consistent transformation to production data inside the production boundary, and delivers only the transformed dataset to the target environment. Real names map to real names. Foreign keys still resolve. Nothing leaves in the clear.
Five stages, one direction: production to target.
NPDL26 uses Oracle GoldenGate to capture production data and transactions, applies the NPDL transformation engine inside the production zone, writes a transformed file inside the production environment, transfers that file to the target — whether non-production, cloud, or affiliate — and applies it to the target with automatic cleanup at the end of the run.
GoldenGate captures production data and transactions.
Change is captured at the source database using Oracle GoldenGate. No production access from outside the production zone is required for a downstream refresh.
NPDL transformation engine.
Deterministic transformation is applied inside the production zone. The same input value always maps to the same output value, so joins hold, distributions hold, and foreign keys still resolve in the transformed dataset.
Securely write the transformed file in the production environment.
The transformed file is materialised inside the production environment. Nothing has left the production boundary in the clear.
Secure transfer to non-production, cloud, or affiliate targets.
Only the transformed file leaves the production zone, over a secured transfer, to the intended target environment.
Apply to the target environment. Clean up automatically.
The transformed file is applied to the target and cleanup runs at the end of the pass. There is no lingering intermediate copy of the transformed data outside the target.
NPDL26 is applied at source, inside the production boundary. Non-production environments never see the untransformed data. This is a design decision, not a configuration option.
What NPDL26 gives your non-production teams.
- Deterministic mapping — the same input always produces the same output, so downstream analytics and tests remain stable across refreshes.
- Referential integrity preserved — primary-to-foreign key relationships continue to resolve in the transformed dataset.
- No egress in the clear — only the transformed file crosses the production boundary.
- Native platform coverage — Oracle Database, Microsoft SQL Server, and IBM DB2, with wider reach via Oracle GoldenGate.
- Automatic cleanup — intermediate artefacts are removed at end-of-run.
- Reversible under RDT26 — when a specifically identified record needs lawful re-identification, RDT26 provides the governed path.