Export Of External Tables Defined Without Access Parameters Creates a Huge Dump File

(Doc ID 390449.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Server - Enterprise Edition - Version: to
This problem can occur on any platform.


You created the following external table without access parameters based on alert.log file:

sqlplus "/ as sysdba"
create or replace directory bdump_dir as 'e:\oracle\admin\wipdba\bdump';
grant read, write on directory bdump_dir to test;

connect test/passwd
create table alert_log
   alert varchar2(4000)
organization external
   default directory bdump_dir
   location ('alert_wipdba.log')
reject limit unlimited;

Then you started a full database export and observed that the dump file size increased extremely. You tried with ROWS=N and the dump file is huge, too.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms