How To Import Objects Into Different Tablespace Other Than From Which They Have Exported
(Doc ID 285417.1)
Last updated on SEPTEMBER 20, 2019
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 8.1.7 to 9.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
2. Importing objects into different tablespace other than from which they have exported
Import decides a tablespace to create objects as following:
- if a user's quota allows it, the user's tables are imported into the same tablespace from which they were exported. However, if the tablespace no longer exists or the user does not have the necessary quota, the system uses the default tablespace for that user as long as the table is unpartitioned, contains no LOB or VARRAY columns, is not a type table, and is not an index-only table with an overflow segment.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!