The Data Pump method for moving data between different database versions is different from the method used by original Export and Import. Initialization parameters should be sufficient upon installation. Data Pump chooses the best method toĮnsure that data and metadata are exported and imported in the most efficient manner. Unlike Original Export and Import, which used the BUFFER, COMMIT, COMPRESS,ĬONSISTENT, DIRECT, and RECORDLENGTH parameters, Data Pump needs no Both parameters work with Data Pump Import as well, and you can use different INCLUDE and EXCLUDE options for different operations on the same dump file. You cannot mix the two parameters in one job. The EXCLUDE parameter allows you to specify which object (and its dependent objects) you want to keep out of the export job. The INCLUDE parameter allows you to specify which object (and its dependent objects) you want to keep in the export job. Note how the FROMUSER/TOUSER syntax is replaced by the REMAP_SCHEMAĢ) Example export of an entire database to a dump file with all GRANTS, INDEXES,Ĭmd> exp username/password FULL=y FILE=fulldb.dmp GRANTS=y INDEXES=y ROWS=yĬmd> expdp username/password FULL=y INCLUDE=GRANT INCLUDE= INDEXĭIRECTORY=dpumpdir1 DUMPFILE=fulldb.dmp CONTENT=ALL
Once the directory access is granted, the user scott can export his database objects with command arguments:Ĭmd> expdp username/password DIRECTORY=dpumpdir1 dumpfile=scott.dmpĬOMPARISON OF COMMAND-LINE PARAMETERS FROM ORIGINAL EXPORT AND IMPORT TO DATA PUMPġ) Example import of tables from scott’s account to Nav’s accountĬmd> imp username/password FILE=scott.dmp FROMUSER=scott TOUSER=Nav TABLES=(*)Ĭmd> impdp username/password DIRECTORY=dpumpdir1 DUMPFILE=scott.dmp Similarly, the Oracle database requires permission from the operating system to read and write files in the directories. You are not given direct access to those files outside of the Oracle database unless you have the appropriate operating system privileges. Note that READ or WRITE permission to a directory object means only that the Oracle database will read or write that file on your behalf.
sql> GRANT READ,WRITE ON DIRECTORY dpumpdir1 TO scott For example, to allow the Oracle database to read and to write to files on behalf of user scott in the directory named by dpumpdir1, you must execute the following command:Ģ. sql> CREATE DIRECTORY dpumpdir1 AS ‘ D:\test\ ’ Īfter a directory is created, you need to grant READ and WRITE permission on theĭirectory to other users. You would login to SQL*Plus as system and enter the following SQL command toġ. In the following example, the following SQL statement creates a directory object named dpumpdir1 that is mapped to a directory located at If a directory object is not specified, a default directory object called data_pump_dir is provided. In order to use Data Pump, the database administrator must create a directory object and grant privileges to the user on that directory object. There is now a very powerful interactive command-line mode which allows the user to monitor and control Data Pump Export and Import operations.ĬHANGING FROM ORIGINAL EXPORT/IMPORT TO ORACLE DATA PUMP These server processes access files for the Data Pump jobs using directory objects that identify the location of the files.
Two new concepts in Oracle Data Pump that are different from original Export and Import.ĭata Pump differs from original Export and Import in that all jobs run primarily on the server using server processes.