Data Pump Dump File Version Compatibility for Downward Migration
0 reputation · 16 Sept 2022, 04:32 UTC
Data Pump export files record the source database release in the dump file header and import checks compatibility before loading metadata.
The goal is downward migration from a newer Oracle release to an older target while preserving schema objects and data fidelity. The VERSION parameter can be used at export time to request a target release level, but it is unclear which object types are silently omitted versus preserved, and whether feature loss is deterministic across 12.2, 19c, 21c and 23ai.
An alternative is a two-step export through an intermediate database that matches the target feature set. The decision boundary between a single export with VERSION downgrade and an intermediate export remains unresolved.
What metadata categories are guaranteed to survive a VERSION downgrade to a specific release? When does an intermediate export retain more information than VERSION stripping? Is the compatibility behavior consistent across major releases for objects introduced after 19c?
