How to SetOracle11gImport backup10g
11g Export Statement: expdp userid ='Facial/Facial@OrclAs sysdba 'schemas = facial directory = DATA_PUMP_DIRdumpfile = aa. dmp logfile = aa. log version = 10.2.0.1.0
The red text is rewritten as needed. For example, my usersFacialThe password isFacial, Database sid isOrclThe username to be exported by schemas isFacialTo import it to the Oracle database of version 10.2.0.1.0. Aa. dmp and aa. log will be generated in the 11g dpdump directory. For example, if my 11g is installed under the edisk, aa. dmp will be generated in the E: \ app \ Administrator \ admin \ orcl \ dpdump directory.
2. Use the impdp command to restore data on a 10 Gb Server
Preparations: 1. Create a database 2. Create a tablespace 3. Create a user and authorize 4. Copy aa. dmp to the 10 Gb dpdump directory
-- Create a tablespace
Createtablespace TS_Facial datafile 'e: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ ORCL \ Facial. dbf' size 500 M autoextend on next50M;
-- Create a user
Create user Facial identified by FacialDefault tablespace TS_Facial;
-- Authorize the user
Grantconnect, resource, dba to Facial;
Place aa. dmp and aa. log in the E: \ oracle \ product \ 10.2.0 \ admin \ orcl \ dpdump directory
10g Import Statement: impdp userid ='Facial/Facial@OrclAs sysdba 'schemas =FacialDirectory = DATA_PUMP_DIR dumpfile = aa. dmp logfile = aa. logversion = 10.2.0.1.0
The red part is rewritten as needed. For example, my usersFacialThe password isFacial, Database sid isOrcl, The user name to import schemas isFacialTo import it to the Oracle database of version 10.2.0.1.0. Aa. log will be generated in the 10 Gb dpdump directory.
When using expdp, an error may be reported. The solution is found both in metink and Gai.
The ORA-39213 Metadata processing not available.
Executed today EXPDP This error occurs:
Connectedto: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0-Production
Withthe Partitioning, OLAP and Data Mining options
ORA-39006: internal error
ORA-39213: Metadata processing is not available.
MetalinkTo confirm that the problem is a known problem, perform the following steps:
Connect/as sysdba
Executesys. dbms_metadata_util.load_stylesheets;
In my system, the above process is valid:
OracleDatabase 10g Enterprise Edition Release 10.2.0.2.0-Production
Withthe Partitioning, OLAP and Data Mining options
SQL> exec dbms_metadata_util.load_stylesheets
PL/SQLprocedure successfully completed.
SQL> exit
After that, the export can be executed smoothly.