CNDBA社区
ORA-39083: Object type TABLE:"BITPOWER"."MASTERINFO" failed to create with error:
ORA-02289: sequence does not exist
Failing sql is:
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "BITPOWER"."ECAT_TEMPLATE" 1.024 MB 13418 rows
. . imported "BITPOWER"."CLASSIFICATION_INFO":"SYS_P99988" 621.1 MB 14299998 rows
. . imported "BITPOWER"."CLASSIFICATION_INFO":"SYS_P2262" 23.14 KB 276 rows
. . imported "BITPOWER"."CLASSIFICATION_INFO":"SYS_P473" 1.885 MB 40100 rows
. . imported "BITPOWER"."CLASSIFICATION_COLOR" 6.664 KB 70 rows
Processing object type TABLE_EXPORT/TABLE/COMMENT
ORA-39112: Dependent object type COMMENT:"LOTID" skipped, base object type TABLE:"BITPOWER"."MASTERINFO" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
ORA-39112: Dependent object type INDEX:"BITPOWER"."MASTERINFO_IDX_DEVICE1" skipped, base object type TABLE:"BITPOWER"."MASTERINFO" creation failed
ORA-39112: Dependent object type INDEX:"BITPOWER"."MASTERINFO_IND1" skipped, base object type TABLE:"BITPOWER"."MASTERINFO" creation failed
ORA-39112: Dependent object type INDEX:"BITPOWER"."MASTERINFO_IND2" skipped, base object type TABLE:"BITPOWER"."MASTERINFO" creation failed
ORA-39112: Dependent object type INDEX:"BITPOWER"."PRIMARY_KEY1" skipped, base object type TABLE:"BITPOWER"."MASTERINFO" creation failed
ORA-39112: Dependent object type INDEX:"BITPOWER"."MASTERINFO_INX_GETSN1" skipped, base object type TABLE:"BITPOWER"."MASTERINFO" creation failed
Processing object type TABLE_EXPORT/TABLE/INDEX/FUNCTIONAL_INDEX/INDEX
ORA-39112: Dependent object type INDEX:"BITPOWER"."MASTERINFO_INX_PRIORITY1" skipped, base object type TABLE:"BITPOWER"."MASTERINFO" creation failed
官网解释：分区表必须为相同的block sizes，因为源端数据库block sizes为16384，目标端为8192，所以发生错误。
While creating the table, the default tablespace is not set. The user default tablespace is USERS which has an 8K block size. So, that is set as the table's default tablespace. Since this is a table with subpartitions, it means if a new subpartition is created without assigning a tablespace, it would go in to the default tablespace for the table which has a different block size. This is not allowed for partitioned tables. All partitions must go in to tablespaces with the same block sizes.
解决方案，将源端建表的SQL拿出来，导入到目标端,impdp的时候使用truncate方式
impdp system/wwwwww@xxx.xxx.xxx.xxx:1521/PDB01 directory=ORADATA dumpfile=xxx.dump logfile=xxx.in table_exists_action=truncate remap_tablespace=tbs01:USERS
版权声明：本文为博主原创文章，未经博主允许不得转载。
oracle
