ORA-00932 WHILE USING IMPDP WITH REMAP_SCHEMA INVOLVING TYPE WITH DEFAULT SECTION
(Doc ID 1367290.1)
Last updated on MAY 17, 2021
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database 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.
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.
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
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