IN-MEMORY SERIES

This is a reference list grouping some IN-MEMORY post i published.I’ll be updating it  whenever I add a new one.

• Oracle database 12c in-memory – part1 (unwanted behavior)
• ORACLE 12C in-memory : Part 2 (Read consistency)
• Oracle 12C In-memory : Part 3 (IMCU pruning)
• ORACLE 12C in-memory : Part 4 (IMCU Stale entries)
• Improving IN-MEMORY query with Attribute Clustering (IMCU pruning and compression ratio)
• ORACLE IN-MEMORY transaction journal or buffer cache ?
• In-Memory : Optimizer cost calculation some anomaly ! (IM Quotient, IM Journal Rows)
• IN-MEMORY population/[trickle] re-population : How much work ? You may be surprised !
• IN-MEMORY population and auto I/O slot resize

 

IN-MEMORY population and auto I/O slot resize

In my last blog post on IN-MEMORY when investigating the amount of work done on behalf of  IN-MEMORY population/[trickle] re-population i have done some observation concerning auto I/O slot resize.So here is more detail in a very short post(Sadly no time for a deeper investigation 😦 ).

Slow INDEX FULL SCAN (MIN/MAX) after rollback

Last week i was called by multiple users signaling a total slowdown of the the “system”. After a few check i decided to trace one of the affected user action.There was only a single SQL statement consuming mostly of the time and it was as simple as this :