Database Administration (MOSC)

MOSC Banner

Why Does The Primary Key Constraint lands in Defalut Tablespace After Import?

edited Dec 22, 2022 7:23AM in Database Administration (MOSC) 8 commentsAnswered

Hi,

We have recently moved a schema from Oracle 18x 12.x (Standard Edition) to 19.x Container Database (Pdb) using Expdp and Impdp.

Sorry for I need to correct my DB versions... 12.2.0.1 exact Bundle WINDOWS DB BUNDLE PATCH 12.2.0.1.190416(64bit):29394003


In our source database (18.x 12.x SE) all table index were defined in a separate Tablespace.

But after Import in 19.x (EE) all primary key are in a users Default Tablespace. And rest Indexes are imported in other tablespace like it was defined previously.

Have you ever noticed this kind of phenomenal?

Is there any Explanation for this ?

How we can impose Expdp and Impdp to create Primary key as in the original defined Tablespace?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center