Using FROMUSER/TOUSER Fails to Generate Tables With LOBs into TOUSER Tablespace
(Doc ID 91969.1)
Last updated on FEBRUARY 18, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 8.1.5.0 and laterOracle Database Cloud Schema 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
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
This problem can occur on 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.
Symptoms
In 8.1.5, an import FROMUSER/TOUSER including a table with LOB clauses cannot import the table and its LOB segments into the TOUSER's tablespace though the Import utility can be forced into placing objects into the TOUSER's tablespace using the traditional method:
1. Set QUOTA=0 on the FROMUSER's tablespace for the schema which will own the objects after import.
2. Set that TOUSER's DEFAULT TABLESPACE to the intended destination.
3. Make sure the user has sufficient QUOTA on the destination tablespace.
4. Perform the import.
The import utility will still try to import those objects into the original tablespace.
Even if the TOUSER has no QUOTA on the FROMUSER's tablespace, the operation will fail and the utility will not check the TOUSER's default tablespace and will not try to import the objects into the TOUSER's tablespace.
Example:
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |