IMPDP: The job SYS_IMPORT_FULL_01 has halted due to a fatal error

Question

Hi,
I'm having problems importing a database whose export was successful.
The tool I'm using is expdp and impdp.
The source schema is in a tablespace different from the target schema, but in the same instance of the Oracle database.
I granted the role of EXP_FULL_DATABASE for the source user and granted the role IMP_FULL_DATABASE to the target user.
Specifically, the following happens: I can export the schema and can successfully import the first four tables to the target schema. So the impdp provides the following message:
Processing object type SCHEMA_EXPORT / TABLE / TABLE_DATA
. . imported "BDE_INEA_DES". "GPL_DECLIV_FRAGIL" 328.4 MB 668 706 lines
. . imported "BDE_INEA_DES". "GLN_CURVA_NIVEL" 336.3 MB 124 324 lines
. . imported "BDE_INEA_DES". "GPL_APP_10" 2920 lines 238.7 MB
. . imported "BDE_INEA_DES". "GLN_CURVA_NIVEL_10" 200.8 MB 15 344 lines
The job "BDE_INEA_DES". "SYS_IMPORT_SCHEMA_01" was halted due to a fatal error at 11:52:41
I've tried exporting using SYSTEM user and the user's schema source owner. I tried the same procedures with the import, but without success.
Information of my OS:
Windows Server 2008 R2 x64
Information of Oracle database:
SQL> SELECT * FROM V $ VERSION;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL / SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for 64-bit Windows: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production

Answer 1

Follow these steps. You will get exactly what you are trying to find.
1) spool invalidobj_and_registry.txt
SELECT SUBSTR(comp_id,1,15) comp_id, status, SUBSTR(version,1,10)
version, SUBSTR(comp_name,1,30) comp_name
FROM dba_registry
ORDER BY 1;
SELECT status, object_id, object_type, owner||'.'||object_name "OWNER.OBJECT"
FROM dba_objects
WHERE status != 'VALID'
ORDER BY 4,2;
spool.off
2) $ sqlplus "/as sysdba"
sql>EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
sql>EXEC DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;
3) Run your import with these two extra parameters along with your parameters
CONTENT=METADATA_ONLY METRICS=Y TRACE=480300
4) As soon as impdp job started:
-- In SQL*Plus, obtain Data Pump processes info:
CONNECT / as sysdba
select to_char(sysdate,'YYYY-MM-DD HH24:MI:SS') "DATE", s.program, s.sid, s.status, s.username, d.job_name, p.spid, s.serial#, p.pid
from v$session s, v$process p, dba_datapump_sessions d
where p.addr=s.paddr and s.saddr=d.saddr;
-- Get the sid and serial# for DM00 and DW01 and execute:
exec DBMS_SYSTEM.SET_EV([SID],[SERIAL#],10046,12 ,'');
for ***both*** of them.
After hang is noticed please leave the import running for one more hour and kill it.
Please check:
- alert log
- impdp log file
- trace files generated during import time in bdump directory
++ before restarting the impdp check if there are orphan Data Pump jobs left in database. Use Note 336014.1 - "How To Cleanup Orphaned DataPump Jobs In DBA_DATAPUMP_JOBS ?