Impdp Transportable Tablespace Of Partitioned Iot Table Is Failing With Ora-8103 (Doc ID 1260157.1)

Last updated on FEBRUARY 02, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.4 and later
Information in this document applies to any platform.

Symptoms


===================
-- Problem Statement:
Customer facing the following errors during impdp and imp, for Transportable Tablespaces:

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SYS"."SYS_IMPORT_TRANSPORTABLE_01" successfully loaded/unloaded
Starting "SYS"."SYS_IMPORT_TRANSPORTABLE_01": sys/******** AS SYSDBA parfile=impdp_imp_mobena0.par
Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
Processing object type TRANSPORTABLE_EXPORT/TABLE
ORA-39083: Object type TABLE failed to create with error:
ORA-08103: object no longer exists
Failing sql is:
CREATE TABLE "MOBEAFO"."V480_DUPCHECK_KEYS_NEW" ("PERIOD" NUMBER(2,0) CONSTRAINT

Changes

We try to migrate a 90GB tablespace with datapump transportable tablespace option.
We migrate from database "EMOXXX" to database "MOBXXX"
The tablespace contains a partitioned and self-contained IOT,
the tablespace is locally managed with segment space management manual.

And there has been partition maintenance operations performed on this object.
.
Import fails with
ORA-08103: object no longer exists
Failing sql is:
CREATE TABLE "MOBEAFO"."V480_DUPCHECK_KEYS_NEW" ("PERIOD" NUMBER(2,0)
CONSTRAINT

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms