How to reduce the excessive [archived] redo logs that are generated for direct path inserts?
(Doc ID 2176216.1)
Last updated on FEBRUARY 19, 2019
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 and later
Oracle 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.
We can see high redo generation for direct path inserts even when NOLOGGING option is specified for both the table and the B*tree indexes. This Document describes the causes and workaround for this Issue.
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