Compression Is Not Working On Bulk Loads For Tables with >255 Columns (Chained Rows) Starting With 12.1.0.2.160119
(Doc ID 2263452.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle 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
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Tables that have > 255 columns ("wide tables") cause the row to be split into multiple row pieces, also known as a chained row. After applying one of the following patches, compression no longer occurs for bulk loads or direct loads with chained rows:
- 12.1.0.2.160719 (Jul 2016) Database Patch Set Update (DB PSU)
- 12.1.0.2.160119 (Jan 2016) Bundle Patch for Engineered Systems / DB In-Memory (DBBP)
- 12.1.0.2.160719 (Jul 2016) Bundle Patch for Windows Platforms
This can lead to side effects such as the following:
- Additional space need to be considered for such tables (double space) when reorganizing
- Compression can still be used but only with insert/update/delete and avoiding bulk loads
Changes
You applied one of the following (or higher) bundled patches:
- 12.1.0.2.160719 (Jul 2016) Database Patch Set Update (DB PSU)
- 12.1.0.2.160119 (Jan 2016) Bundle Patch for Engineered Systems / DB In-Memory (DBBP)
- 12.1.0.2.160719 (Jul 2016) Bundle Patch for Windows Platforms
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 |