My Oracle Support Banner

ORA-00932 WHILE USING IMPDP WITH REMAP_SCHEMA INVOLVING TYPE WITH DEFAULT SECTION (Doc ID 1367290.1)

Last updated on MARCH 05, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.7 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

While doing an datapump import with the remap_schema option and if a table contains TYPES which has a default section defined, impdp with ORA-00932

To explain the issue, here is a small testcase.

Drop users


As you can see, the datatype section has been successfully mapped to the new user (<USERNAME2><USERNAME1>), but the default section still points old user (<USERNAME1>).

CREATE TABLE "<USERNAME2>"."<TABLE_NAME>" (<COLUMN_NAME1> NUMBER(38,0) NOT NULL ENABLE,
"<USERNAME2>"."<COLUMN_NAME2>" "STRING_ARRAY" DEFAULT "<USERNAME1>"."STRING_ARRAY"('','','')
       ^^^^^^^ successfully mapped                 ^^^^^^ unsuccessful in mapping
"<USERNAME2>"."<COLUMN_NAME3>" "NUMBER_ARRAY" DEFAULT "<USERNAME1>"."NUMBER_ARRAY"(0,0,0))                         
       ^^^^^^^ successfully mapped                 ^^^^^^ unsuccessful in mapping

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.