Why Does The Primary/Unique Key Constraint Point To A Different Index After Import?
(Doc ID 1455492.1)
Last updated on NOVEMBER 14, 2023
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Database - Enterprise Edition - Version 10.1.0.2 and later
Oracle Database Cloud Service - Version N/A 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
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.
Goal
You started DataPump export/import to transfer a table with indexes and constraints to another database. After import, you observed that the primary key constraint is using a different index than the originally defined one.
The next test demonstrates this:
Solution
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
| Goal |
| Solution |
| References |