By Maria Colgan-Oracle on Apr 18, 2016
I recently got a question from a customer who has just begun adopting Database In-Memory and thought it was worth answering as a blog post in case anyone else had encountered the same scenario and was wondering what was going on.
Here is the question I got:
“I've observed a scenario where a table is fully populated in the In-Memory column store with 0 in the BYTES_NOT_POPULATED column in v$im_segments, but after some time, the BYTES_NOT_POPULATED column shows a non-zero value. Why is Oracle purging part of my table from memory?”
Let me begin to answer this by assuring you all that Oracle does not purge your data out of the In-Memory column store.[Read More]