Some Data Pump issues:
+ DBMS_DATAPUMP Import via NETWORK_LINK fails
+ STATUS parameter giving bad performance
By Mike Dietrich-Oracle on Jun 30, 2015
One of my dear Oracle ACS colleagues (Danke Thomas!) highlighted this issue to me as one of his lead customers hit this pitfall a week ago. .
DBMS_DATAPUMP Import Over NETWORK_LINK fails with ORA-39126 / ORA-31600
ORA-31600: invalid input value IN ('VIEWS_AS_TABLES/TABLE_DATA') for parameter VALUE in function SET_FILTER.
This can be cured with the patch for bug19501000 - but this patch can conflict with:Bug 18793246 EXPDP slow showing base object lookup during datapump export causes full table scan per object and therefore may require a merge patch - patch 21253883 is the one to go with in this case.
Another issue Roy just came across:
Data Pump is giving bad performance in Oracle 184.108.40.206 when the STATUS parameter option is used on command line
It looks like the routines we are using to get status are significantly slower in 12c than in 11g. On 220.127.116.11 a STATUS call of expdp/impdp runs in 0.2-0.3 seconds, but in 18.104.22.168 it takes 0.8-1.6 seconds. As a result the client falls behind on 22.214.171.124; it is taking about 0.5-0.8 seconds to put out each line in the logfile because it is getting the status each time. With over 9000 tables in a test that half a second really adds up. The result in this test case was that the data pump job completed in 35 minutes, but it took another 30-35 minutes to finish putting out messages on the client (the log file was already complete) and return control to the command line. This happens only when you use STATUS on the command line.
Don't use the STATUS parameter on the expdp/impdp command line in Oracle 126.96.36.199 until the issue is fixed. This will be tracked under Bug 21123545.