ORA-31684 And ORA-39111 Errors Are Raised During Impdp For An Index Even If EXCLUDE=INDEX Is Used
(Doc ID 1992604.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 11.2 to 12.1]
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data .Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Why are the ORA-31684 and ORA-39111 errors raised during Impdp for an index even if exclude=index is used?
The example below contains the steps to reproduce the error:
==> the constraint is dropped but the index is still there. Why?
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