Last updated on MARCH 27, 2014
Applies to:Oracle Server - Enterprise Edition - Version: 184.108.40.206
Information in this document applies to any platform.
=== ODM Question ===
We are in process of testing table compression feature with: compress for all operations, however we are trying to determine:
1. Why so much undo is being generated, we believe this is due to the before image of the block being retained in undo segment every time compression is applied to the block?
Initially we ran few test which indicated, column: v$transaction.used_ublk (undo block) and statistic: heap block compress increased every time compression occurred.
2. What is the correct session level statistic that verifies "how many" times compression took place?
3. What is the difference between: HSC OLTP positive compress and heap block compress?
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