My Oracle Support Banner

ORA-39059 On Schema Import From a Full Export Using Dbms_datapump API (Doc ID 784793.1)

Last updated on OCTOBER 07, 2019

Applies to:

Oracle Database - Standard Edition - Version 10.2.0.3 and later
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

ORA-39059 is reported on a Datapump Schema Import using the following syntax:

  SQL>exec schema_impdp('<schema_name1>','<schema_name2>','dpexp_schema','dpimp_schema');

The export dump file is create using DataPump API (dbms_datapump) with these options:

begin
h1 := dbms_datapump.open
(
operation => 'export',
job_mode => 'full',
version => 'compatible'
);

dbms_datapump.add_file
(
handle => h1,
filename => v_export_log,
directory => in_directory,
filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE
);

dbms_datapump.add_file
(
handle => h1,
filename => v_export_file,
directory => in_directory,
filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_DUMP_FILE
);

dbms_datapump.start_job(h1);

exception
when others then
...
end;

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.