Oracle 11g Release 1 (11.1) Data Pump import Mode

Content

One of the most notable features of import is the import mode, because to a large extent, the mode determines what to import. Apply the specified mode to the operation source, such as the source or dump file set, or another database (ifNETWORK_LINKParameters .)

When the import operation source is a dump file set, specifying a mode is optional. If the import mode is not specified, the entire dump file set in the load mode is attempted.

Specify the mode in the command line with appropriate parameters. The import mode is as follows:

• Full Import Mode
• Schema mode
• Table mode
• Tablespace mode
• Transportable Tablespace mode
• Oracle 11g Release 1 (11.1) Data Pump export Mode

Note:

When you importFull-modeWhen a dump file is created in export mode, the import operation will try to copy from the source databaseSYSThe password of the account. Sometimes this will fail (for example, if the password is in a public password file ). If the Import fails, you must set the password of the SYS account in the target database.

Note:

Jobs (created by Oracle Database Job Scheduling) are always imported to the mode of importing users. After the import, if you queryDBA_JOBSView, you will seeLOG_USERAndPRIV_USERThe value is set to the users being imported, regardless of how they are set on the export platform.

To solve this problem, you must execute export and import as the job owner.

 

Full Import Mode

UseFULLThe parameter specifies "full import ". In this mode, all the content of "Source (dump file or another database)" is loaded to the target database. For file-based imports, This is the default. If "Source" is another database, you must haveIMP_FULL_DATABASERole.

Users who do not have permission cannot import cross-mode references. For example, you cannot import a trigger. It defines a table in the import user mode, but in another user mode.

If you useNETWORK_LINKIf the parameter is completely imported, you needIMP_FULL_DATABASEAndEXP_FULL_DATABASERole.

Example 1: This example shows how to import a dump file.Expfull. dmp. In this exampleDIRECTORYParameters must be inDUMPFILEAndLOGFILESpecify the directory object in the parameter. Directory objects can be different, as shown below.

impdp hr DUMPFILE=dpump_dir1:expfull.dmp FULL=y 

LOGFILE=dpump_dir2:full_imp.log

 

Schema mode

UseSCHEMASThe parameter specifies "Mode import ". In this mode, only objects in the specified mode are loaded. "Source" can beFull,Table,TablespaceOrSchema-modeThe exported dump file set or another database. If you have the IMP_FULL_DATABASE role, you can specify a mode list and the mode created in the database (including the system permission granted), except for the objects contained in the mode.

Users who do not have the permission cannot import cross-mode references unless other modes are mapped to the current mode. For example, you cannot import a trigger. It defines a table in the import user mode, but in another user mode.

Example 2: This example shows the dump fileExpdat. dmpImportHrMode.Schemas. logWrite log filesDpump_dir1.

impdp hr SCHEMAS=hr DIRECTORY=dpump_dir1 LOGFILE=schemas.log

DUMPFILE=expdat.dmp

1 2 Next Page