My Oracle Support Banner

Transform=disable_archive_logging:Y Is Not Working When using Datapump Import on a Table with a BLOB Column (Doc ID 3027067.1)

Last updated on JUNE 11, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.19.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On 19c version, the Data Pump Import transform=disable_archive_logging:Y parameter is not working when importing a table into the database.

On the source database, a datapump export of a table with large size BLOB column was taken and while importing this table into an Oracle Database 19C, a huge amount of redolog files are generated, exhausting the space on the mount point even while using "transform=disable_archive_logging:Y" in the datapump import command. The parameter is supposed to disable the redo log generation, but it doesn't work as expected. The redolog files generated are more than the size of the table being imported.

Changes

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.