0% found this document useful (0 votes)
18 views3 pages

Document 2474680.1

The document discusses errors encountered during a schema-level import in an Oracle 12c database, specifically ORA-39083 and ORA-14110 related to partitioning columns of type ROWID. It identifies that the cause of the issue is the presence of a shadow index during the export process and provides a solution to check index status or drop the shadow index before running the export. References to additional resources and a bug report are also included for further assistance.

Uploaded by

splivegma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views3 pages

Document 2474680.1

The document discusses errors encountered during a schema-level import in an Oracle 12c database, specifically ORA-39083 and ORA-14110 related to partitioning columns of type ROWID. It identifies that the cause of the issue is the presence of a shadow index during the export process and provides a solution to check index status or drop the shadow index before running the export. References to additional resources and a bug report are also included for further assistance.

Uploaded by

splivegma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

7/3/25, 19:40 Document 2474680.

1
Copy right (c) 2025, Oracle. A ll rights reserv ed. Oracle Confidential.

IMPDP generates ORA-39083, ORA-14110: Partitioning Column May Not Be Of Type ROWID (Doc
ID 2474680.1)

In this Document

Symptoms
Changes
Cause
Solution
References

APPLIES TO:

Oracle Text - Version 11.2.0.4 and later


Information in this document applies to any platform.

SYMPTOMS

Errors were generated during SCHEMA-level import in a 12c TARGET database:

Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
Primary table "SYS"."SYS_IMPORT_SCHEMA_01" successfully loaded/unloaded
Starting "SYS"."SYS_IMPORT_SCHEMA_01": "/******** AS SYSDBA" DIRECTORY=DATA_PUMP_DIR
SCHEMAS=ctxbug DUMPFILE=ctxbug.dmp LOGFILE=imp_ctxbug.log
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"CTXBUG" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39083: Object type TABLE:"CTXBUG"."DR$RIO$3349$K" failed to create with error:
ORA-14110: partitioning column may not be of type ROWID
Failing sql is:
CREATE TABLE "CTXBUG"."DR$RIO$3349$K" ("DOCID" NUMBER(38,0), "TEXTKEY" ROWID, PRIMARY KEY
("TEXTKEY") ENABLE) ORGANIZATION INDEX NOCOMPRESS PCTFREE 10 INITRANS 2 MAXTRANS 255 TABLESPACE
"USERS" STORAGE( BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) PCTTHRESHOLD 50
PARTITION BY RANGE ("TEXTKEY") (PARTITION "P1" VALUES LESS THAN (MA
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "CTXBUG"."DR$RIO$3349$I":"P1" 7.640 KB 10 rows
. . imported "CTXBUG"."DR$RIO$3349$R":"P1" 5.570 KB 1 rows
. . imported "CTXBUG"."DR$RIO$3349$N":"P1" 0 KB 0 rows
. . imported "CTXBUG"."QUICK" 5.992 KB 2 rows
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/STATISTICS/MARKER
Processing object type SCHEMA_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
Job "SYS"."SYS_IMPORT_SCHEMA_01" completed with 2 error(s) at Mon Nov 19 18:17:20 2018 elapsed 0
00:00:18

CHANGES
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=2fx77ycm5_358&id=2474680.1 1/3
7/3/25, 19:40 Document 2474680.1

CAUSE

EXPDP was performed in the SOURCE database while a shadow index exists for a Text index, see example below:

SQL> -- Some time in the past, a shadow index was created for Text index called QUICK_TEXT in this
example:
SQL> connect ctxbug/ctxbug
Connected.
SQL> show user
USER is "CTXBUG"
SQL> exec ctx_ddl.create_shadow_index('quick_text', 'replace lexer m_lexer language column lang
POPULATE');

PL/SQL procedure successfully completed.

SQL>
SQL> -- Before the EXPDP was run, these exist
SQL> connect / as sysdba
Connected.
SQL>
SQL> select i.idx_id, u.username, i.idx_name, idx_option
2 from ctxsys.dr$index i, dba_users u
3 where u.username = 'CTXBUG'
4 and i.idx_owner# = u.user_id;

IDX_ID USERNAME IDX_NAME IDX_OPTION


---------- ------------ ------------------------- ----------
3349 CTXBUG QUICK_TEXT YA
3353 CTXBUG RIO$3349 BY

SOLUTION

Check index status or the existence of RIO$ at SOURCE before running EXPDP. If RIO$ objects exist, let the index recreation
finish, or drop the shadow index before running EXPDP:

SQL> connect ctxbug/ctxbug


Connected.
SQL> show user
USER is "CTXBUG"
SQL> exec ctx_ddl.drop_shadow_index('quick_text');

PL/SQL procedure successfully completed.

SQL> connect / as sysdba


Connected.
SQL> select i.idx_id, u.username, i.idx_name, idx_option
2 from ctxsys.dr$index i, dba_users u
3 where u.username = 'CTXBUG'
4 and i.idx_owner# = u.user_id;

IDX_ID USERNAME IDX_NAME IDX_OPTION


---------- ------------ ------------------------- ----------
3349 CTXBUG QUICK_TEXT Y

REFERENCES
BUG:28945054 - RIO$ OBJECTS ARE IMPORTED GENERATING ORA-14110
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=2fx77ycm5_358&id=2474680.1 2/3
7/3/25, 19:40 Document 2474680.1

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=2fx77ycm5_358&id=2474680.1 3/3

You might also like