Default: There is no default; the value is user-supplied.
Purpose
Specifies a password for accessing encrypted column data in the dump file set. This prevents unauthorized access to an encrypted dump file set.
It is also required for the transport of keys associated with encrypted tablespaces and tables with encrypted columns during a full transportable export or import operation.
The password that you enter is echoed to the screen. If you do not want the password shown on the screen as you enter it, then use the ENCRYPTION_PWD_PROMPT parameter.
Syntax and Description
ENCRYPTION_PASSWORD = password
This parameter is required on an import operation if an encryption password was specified on the export operation. The password that is specified must be the same one that was specified on the export operation.
Restrictions
This parameter is valid only in the Enterprise Edition of Oracle Database 11g or later.
Data Pump encryption features require that the Oracle Advanced Security option be enabled. See Oracle Database Licensing Information for information about licensing requirements for the Oracle Advanced Security option.
The ENCRYPTION_PASSWORD parameter is not valid if the dump file set was created using the transparent mode of encryption.
The ENCRYPTION_PASSWORD parameter is required for network-based full transportable imports where the source database has encrypted tablespaces or tables with encrypted columns.
Encryption attributes for all columns must match between the exported table definition and the target table. For example, suppose you have a table, EMP, and one of its columns is named EMPNO. Both of the following situations would result in an error because the encryption attribute for the EMP column in the source table would not match the encryption attribute for the EMP column in the target table:
The EMP table is exported with the EMPNO column being encrypted, but before importing the table you remove the encryption attribute from the EMPNO column.
The EMP table is exported without the EMPNO column being encrypted, but before importing the table you enable encryption on the EMPNO column.
Example
In the following example, the encryption password, 123456, must be specified because it was specified when the dpcd2be1.dmp dump file was created (see "ENCRYPTION_PASSWORD").
> impdp hr TABLES=employee_s_encrypt DIRECTORY=dpump_dir DUMPFILE=dpcd2be1.dmp ENCRYPTION_PASSWORD=123456
During the import operation, any columns in the employee_s_encrypt table that were encrypted during the export operation are decrypted before being imported.