My Oracle Support Banner

Create Table Hits ORA-39117 Error During Schema Import and Having A Dependent Type in Different Schema (Doc ID 2448240.1)

Last updated on OCTOBER 18, 2019

Applies to:

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

Symptoms

Create table execution fails during schema import with ORA-39117:

Import: Release 12.1.0.2.0 - Production on Sat Sep 8 10:58:26 2018

Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.
;;;
Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Automatic Storage Management option
Master table "SYS"."SYS_IMPORT_TABLE_01" successfully loaded/unloaded
Starting "SYS"."SYS_IMPORT_TABLE_01":  "/******** AS SYSDBA" parfile=<filename>.par
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
CREATE TABLE "<schema>"."<tablename>" ("BATCH_ID" NUMBER(*,0) NOT NULL ENABLE, "ID" NUMBER(*,0) NOT NULL ENABLE, "CODE" VARCHAR2(200 BYTE), "CONTACT_ID" NUMBER(*,0), "BUSINE
SS_DISTANCE" NUMBER, "PERSONAL_DISTANCE" NUMBER, "DISTANCE_PRICE" NUMBER, "TAX" NUMBER, "PRE_TAXT_COST" NUMBER, "ACTIVITY_PLUS" NUMBER, "ACTIVITY_PLUS_COST" NUMBER, "TO
TAL_COST" NUMBER, "REPORT_IDS" "<schema2>"."<table/array>" , "HAS_CHANGES" NUMBER(*
...
...

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.