Default: the default database edition on the remote node from which objects will be fetched
Purpose
Specifies the database edition on the remote node from which objects will be fetched.
Syntax and Description
SOURCE_EDITION=edition_name
If SOURCE_EDITION=edition_name is specified, then the objects from that edition are imported. Data Pump selects all inherited objects that have not changed and all actual objects that have changed.
If this parameter is not specified, then the default edition is used. If the specified edition does not exist or is not usable, then an error message is returned.
Restrictions
The SOURCE_EDITION parameter is valid on an import operation only when the NETWORK_LINK parameter is also specified. See "NETWORK_LINK".
This parameter is only useful if there are two or more versions of the same versionable objects in the database.
The job version must be set to 11.2 or later. See "VERSION".
Example
The following is an example of using the import SOURCE_EDITION parameter:
> impdp hr DIRECTORY=dpump_dir1 SOURCE_EDITION=exp_edition
NETWORK_LINK=source_database_link EXCLUDE=USER
This example assumes the existence of an edition named exp_edition on the system from which objects are being imported. Because no import mode is specified, the default of schema mode will be used. The source_database_link would be replaced with the name of the source database from which you were importing data. The EXCLUDE=USER parameter excludes only the definitions of users, not the objects contained within users' schemas. (Note that there is no dump file generated because this is a network import.)
Oracle Database SQL Language Reference for information about how editions are created
Oracle Database Development Guide for more information about the editions feature, including inherited and actual objects