Performance Impact On Compressed Tables In a DB Utilizing DB_BLOCK_CHECKING and DB_BLOCK_CHECKSUM
(Doc ID 1538563.1)
Last updated on FEBRUARY 02, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.2.0.3 [Release 11.1 to 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
Symptoms
The following test shows timing information for a 100000 row insert, update, and delete on a table enabled with and without OLTP compression. Results may vary and are intended to show the most significant
timing differences after parameter changes.
Changes
Enabling table compression
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 |