DataPump Export/Import Ignore LOB Storage Parameters For GLobal Temporary Tables
(Doc ID 2223015.1)
Last updated on AUGUST 02, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 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.
Symptoms
DataPump Export doesn't extract the Lob Storage Parameters in the dump file for global temporary tables.
Example:
-----------
- On source database, a global temporary table is created with the following clause for lob storage:
create global temporary table <TABLE_NAME> (COL1 number, COL2 clob) lob (COL2) store as basicfile (enable storage in row retention max cache reads);
- Checking the dump file created by the export and generating the sql file for that table on the source database shows:
CREATE GLOBAL TEMPORARY TABLE "<SCHEMA>"."<TABLE_NAME>"
( "COL1" NUMBER,
"COL2" CLOB
)
ON COMMIT DELETE ROWS ;
==> DDL statement is incorrect as Lob Storage Parameters clause is missing.
Changes
NONE
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 |
| Changes |
| Cause |
| Solution |
| References |