You know what " TRACE for EXPDP/IMPDP"
Sometimes DBA has been asked to take logical backup, we call export, and import to original schema or other scheam, to have same image of data. But it is not always wotking as we expected. And we need to find out what's wrong with EXPDP/IMPDP inside. Here is the thing you can try to get internal procedures of EXPDP/IMPDP 'TRACE = 480300' You will see trace files under background_dump_dest location, name like *dw00*.trc and *dm00*.trc. For example, dvtest2_dw00_2572.trc and dvtest2_dm00_2568.trc. On dvtest2_dw00_2572.trc , You can see all detail steps of impdp. Impdp will define internal table for import job . loading PUT_DDL for objects in order. Each object type completion is updated internally KUPW:06:43:01.095: 1: l_valid: -3 - Not Loading REUSE with type TABLESPACE KUPW:06:43:01.096: 1: l_valid : 1 - Loading EXPORT with type NULL KUPW:06:43:01.096: 1: l_valid : 1 - Loading PRETTY with type NULL KUPW:06:43:01.096: 1: l_valid : 1 - Loading SQLTERMINATOR