DataPump Export (EXPDP) Fails With Error ORA-39826

DataPump Export (EXPDP) Fails With Error ORA-39826 

ORA-31693: Table data object failed to load/unload and is being skipped due to error:

ORA-31693: Table data object "HR"."TEST1" failed to load/unload and is being skipped due to error:

ORA-02354: error in exporting/importing data

ORA-39826: Direct path load of view or synonym (HR.TEST1) could not be resolved.

References : Doc ID 1546646.1 

SYMPTOMS

Datapump export log file contains the errors:

ORA-31693: Table data object "HR"."TEST1" failed to load/unload and is being skipped due to error:

ORA-02354: error in exporting/importing data

ORA-39826: Direct path load of view or synonym (HR.TEST1) could not be resolved.

CHANGES AND CAUSE

This is designed behaviour. The fix for unpublished Bug 9847421 introduced a new set of checks for object name resolution which includes the generation of the ORA-39826 error message (outlined in Bug 14006984).

Export backup has completed and backup was validated.  The below error was because of table was dropped during the runtime of EXPDP export that’s why doesn't find the table at the time of exporting that table.

SOLUTION

Please check whether the objects reported in the error message exist or not. The example below is related to the object mentioned in above error message:

vm215:ORCL $> sqlplus  / as sysdba

SELECT OWNER, OBJECT_NAME, OBJECT_TYPE, STAUS, LAST_DDL_TIME

FROM   DBA_OBJECTS

WHERE  OWNER = 'HR' AND OBJECT_NAME IN ('TEST1');

no row selected

If the query returns no rows, then you can expect the ORA-39826 is raised. You should make sure that the object exists when it is exported and it is not removed during the runtime of export. Dropping an object during the master control table of DataPump export is created and filled but before the actual table contents are exported, will result in these type of error.