Examples Using DataPump VERSION Parameter And Its Relationship To Database COMPATIBLE Parameter
(Doc ID 864582.1)
Last updated on SEPTEMBER 14, 2024
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterGen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Purpose
This article shows by example how setting of data pump VERSION parameter and database COMPATIBLE parameter affect the data pump export and import.
Scope
This article is intended to help users better understand how setting VERSION parameter be used.
Detailed examples with different settings of VERSION and COMPATIBLE are given that demonstrate how these parameters can affect data pump export/import.
For a detailed discussion of data pump compatibility see
<Note 553337.1> Export/Import DataPump Parameter VERSION - Compatibility of Data Pump Between Different Oracle Versions
Here are basic definitions of the VERSION parameter for both export and import.
Export
Specifies the version of database objects to be exported. The VERSION parameter simply allows you to identify the version of the objects being exported.
It also defines the dumpfile compatibility.
- VERSION={COMPATIBLE | LATEST | version_string}
- COMPATIBLE : This is the default value. The version of the metadata corresponds to the database compatibility level. Database compatibility must be set to 9.2 or higher.
- LATEST : The version of the metadata corresponds to the database version.
- version_string : A specific database version (for example, 11.1.0). In Oracle Database 11g, this value cannot be lower than 9.2.
- COMPATIBLE : This is the default value. The version of the metadata corresponds to the database compatibility level. Database compatibility must be set to 9.2 or higher.
Import
Specifies the version of database objects to be imported. The VERSION parameter simply allows you to identify the version of the objects being imported.
It does NOT mean you can specify VERSION equal to a lower database version to import a higher level dumpfile. For example, you cannot specify VERSION=10.1 to import a dumpfile that is version 11.1.
- VERSION={COMPATIBLE | LATEST | version_string}
-
- COMPATIBLE : This is the default value. The version of the metadata corresponds to the database compatibility level. Database compatibility must be set to 9.2.0 or higher.
- LATEST : The version of the metadata corresponds to the database version.
- version_string : A specific database version (for example, 11.1.0). In Oracle Database 11g, this value must be 9.2.0 or higher.
- COMPATIBLE : This is the default value. The version of the metadata corresponds to the database compatibility level. Database compatibility must be set to 9.2.0 or higher.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Purpose |
Scope |
Details |
References |