Hi,
I am encountering a problem exporting a particular object type - SYNONYM - on a particular schema in my database.
expdp system/********* directory=datapump dumpfile=backup20150728 logfile=backup20150728_export.log schemas=SCHEMA_1, SCHEMA_2 trace=480300 metrics=yes
(SCHEMA_1 and SCHEMA_2 are not the real names!)
This hangs at the "processing object type schema_export/pre_schema/proact_schema" stage
If I add exclude=SYNONYM as an option, the export completes within 2 minutes without any issues. Equally, if I remove SCHEMA_1 without exluding SYNONYM the export works fine. It therefore seems logical that the issue is with SYNONYM on SCHEMA_1.
I can't post the entire trace files as this is all being run on a network from which this is not possible. However, the last few lines of the the orcl_dw00_NNNNN.trc read:
KUPF$FILE.WRITE_LOB called.
KUPF$FILE.WRITE_LOB returned.
MD FilePieces Count: 1
FORALL called.
FORALL returned.
DBMS_LOB.TRIM called. v_md_xml_clob
DBMS_LOB.TRIM returned.
DBMS_METADATA.FETCH_XML_CLOB called. Handle: 200001
If I list system processes using: select username, machine, program, sid, status from gv$session where username='SYSTEM'; I can see that ORACLE.EXE (DW00) is active with a SID of 105.
If I then select event, state, wait_class from v$session_wait where sid=105; I get:
latch: cache buffers chains
WAITED SHORT TIME
Concurrency
Earlier when I ran the same query I got:
Datapump dump file I/O
WAITED SHORT TIME
User I/O
I'm not sure why I'm getting a different result.
Thoughts? Could it be something in my that schema's SYNONYMs causing this?