oracle11g - Dbms_datadump fails with ORA-39117 for a table with user defined type -
i have table has column of user defined type, tried move table different schema,
it worked fine using command line mode, when tries use dbms_datapump, fails ora-39117 error, below filters had used.
command line mode:
bin/expdp user1/password1 directory=test_dir1 include=table:\"=\'test_table_1\'\",type:\"in \(\'test_type_1\'\)\" reuse_dumpfiles=y dumpfile=test.dmp logfile=expdptest.log bin/impdp user1/password1 directory=test_dir1 include=table:\"=\'test_table_1\'\",,type:\"in \(\'test_type_1\'\)\" dumpfile=test.dmp logfile=impdptest.log remap_schema=user1:user2 transform=oid:n
with above command, table movement successful. same thing using pl/sql block.
===export=== dbms_datapump.metadata_filter ( handle => h1, name => 'name_expr', value => 'in(''test_table_1'',''test_type_1'')' ); dbms_datapump.metadata_filter( handle => h1, name => 'include_path_expr', value => 'in (''table'',''type'')'); ===import=== dbms_datapump.metadata_filter ( handle => h1, name => 'name_expr', value => 'in(''test_table_1'',''test_type_1'')' ); dbms_datapump.metadata_filter( handle => h1, name => 'include_path_expr', value => 'in (''table'',''type'')');
this problem may have nothing impdp
vs dbms_datapump
. used have many problems importing object-relational tables. never found solution , problem appeared "random" - work 1 day , fail reasons never discovered. if remember correctly, guessed there problems object-relational dependencies , fixed problem manually importing few types before rest of import.
another possibility import succeeded , error message wrong. see doc id 783358.1 - ora-39117 incorrectly reported @ impdp level, on support.oracle.com.
Comments
Post a Comment