Effects of Using the SQL ENCRYPT Clause

If you specify the SQL ENCRYPT clause when you create an external table, then keep the following in mind:

  • The columns for which you specify the ENCRYPT clause will be encrypted before being written into the dump file.

  • If you move the dump file to another database, then the same encryption password must be used for both the encrypted columns in the dump file and for the external table used to read the dump file.

  • If you do not specify a password for the correct encrypted columns in the external table on the second database, then an error is returned. If you do not specify the correct password, then garbage data is written to the dump file.

  • The dump file that is produced must be at release 10.2 or higher. Otherwise, an error is returned.

See Also:

Oracle Database SQL Language Reference for more information about using the ENCRYPT clause on a CREATE TABLE statement