Oracle's 11GR2 version does not make much of a change to the data pump, mainly by adding support for the original version parameters and removing some small restrictions.
This article describes the support of the data pump version.
In 11.2, Oracle added functionality to the version, and the data pump also supports exporting to the specified version or importing the object into the specified version.
Sql> Conn YANGTK/YANGTK
is connected.
Sql> Select Sys_context (' USERENV ', ' Current_edition_name ') from dual;
Sys_context (' USERENV ', ' current_edition_name ')
-----------------------------------------------------------------------
Ora$base
Sql> Select Synonym_name
2 from User_synonyms;
Synonym_name
------------------------------
S_1
Sql> Create edition my_edition;
Version has been created.
Sql> Alter session Set edition = My_edition;
The session has changed.
sql> create synonym s_my_edition for t;
The synonym has been created.
Sql> Host
[Oracle@bjtest ~]$ expdp yangtk/yangtk directory=d_output dumpfile=my_edition.dp include=synonym source_edition=my_ Edition
Export:release11.2.0.1.0-production on Monday September 14 08:10:53 2009
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connect to: Oracle database11genterprise Edition release11.2.0.1.0-64bit Production
With the partitioning, OLAP, Data Mining and real application testing options
Start "YANGTK". Sys_export_schema_01 ": yangtk/******** directory=d_output dumpfile=my_edition.dp include=synonym source_edition=my_ Edition
Using the blocks method to estimate ...
Working with Object Types Schema_export/table/table_data
Total estimate using the blocks method: 0 KB
Working with Object Types schema_export/synonym/synonym
This article URL address: http://www.bianceng.cn/database/Oracle/201410/45402.htm
The primary table "YANGTK" was successfully loaded/unloaded. Sys_export_schema_01 "
******************************************************************************
Yangtk. The set of dump files for sys_export_schema_01 is:
/home/oracle/my_edition.dp
The job "YANGTK". Sys_export_schema_01 "completed successfully at 08:11:02
[Oracle@bjtest ~]$ impdp yangtk/yangtk directory=d_output dumpfile=my_edition.dp target_edition=ora\ $base
Import:release11.2.0.1.0-production on Monday September 14 08:13:08 2009
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connect to: Oracle database11genterprise Edition release11.2.0.1.0-64bit Production
With the partitioning, OLAP, Data Mining and real application testing options
The primary table "YANGTK" was successfully loaded/unloaded. Sys_import_full_01 "
Start "YANGTK". Sys_import_full_01 ": yangtk/******** directory=d_output DUMPFILE=MY_EDITION.DP target_edition=ora$base
Working with Object Types schema_export/synonym/synonym
ORA-31684: Object type synonym: "yangtk". S_1 "already exists
The job "YANGTK". Sys_import_full_01 "has been completed, but there are 1 errors (completed at 08:13:11)
[Oracle@bjtest ~]$ exit
Exit
Sql> Select Synonym_name
2 from User_synonyms;
Synonym_name
------------------------------
S_1
S_my_edition
Because version my_edition is a ora$base version, you can see synonyms created by the parent version. When you export synonyms for the my_edition version, S_1 and s_my_edition two objects are exported.
When importing to the target version ora$base, only the synonym s_my_edition is imported into the target version because S_1 already exists.
The export and import version of the data pump only specifies the version object that is exported or imported, and the corresponding information is not saved in the file saved by the data pump, so if target_edition is not specified at the time of the import, Oracle is imported to the default version. It is not related to the version specified when exporting.
Author: 51cto Blog Oracle Little Bastard