How to reduce the excessive [archived] redo logs that are generated for direct path inserts?
Last updated on JUNE 16, 2017
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms