COMPRESS FOR ALL OPERATIONS generates lot of redo
Last updated on MAY 12, 2017
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 11.1 to 12.1]
Information in this document applies to any platform.
COMPRESS FOR ALL OPERATIONS generates significantly more redo than NOCOMPRESS or, even COMPRESS (and load data with direct load)
With "COMPRESS FOR ALL OPERATIONS" database calls the code to try to compress the current block for all operations. The undo for such compression is a before block image.Hence the redo with "COMPRESS FOR ALL OPERATIONS" includes extra redo for the UNDO (before images) of blocks.
So even if the effect of the attempt to compress the block is minimal undo will have to be dumped (before image) for that attempt.
This behavior is specific for 11g (and onwards) as COMPRESS FOR ALL OPERATIONS is not available on pre-11g releases.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms