In a previous blog post, I showed how using flash storage on Exadata can extend the Oracle in-memory capacity by using flash storage in conjunction
Exadata features save the day for me more often than not, but it’s also the built-in features of Oracle Database that come to the rescue
While testing the In-Memory feature extensions at the Exadata storage level, I thought I was going to hit a limitation that would prevent a full
An alternate title for this post: “is it a bug or a feature”? I was setting up a 21c database on Exadata when I ran
Exadata extends the concept of SQL Quarantines at the cell storage level: the behavior of Exadata quarantined SQL_IDs and how they are treated is different
All of Oracle’s database technologies fed into the backbone of Exadata over 10 years ago — but does the process work in the other direction?