Explaining and Tuning "Insufficient memory to populate table to inmemory area" Errors When OEM and In-Memory Views Show Free Space In-Memory Pool
(Doc ID 2343783.1)
Last updated on MARCH 06, 2023
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle 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
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- OEM / Grid Control shows large amounts of free space in the in-memory pool
- V$/GV$IM_SEGMENTS show the inmemory_size of the segments is smaller than the total pool size
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 |
| Cause |
| Solution |
| Single Instance tuning or RAC tuning when ALL In-Memory objects are set to duplicate across all instances |
| RAC Tuning when Objects are distributed "BY ROWID RANGE", "BY PARTITION", "BY SUBPARTITION" |
| RAC Tuning when Objects are auto-distributed without duplicate |
| References |