I’m about simplifying anything for customers as we bring over complex environments into Azure and Oracle databases running on Exadata is a big part of these challenges. Decoupling the database from the engineered features is a crucial part of my work and with Oracle 19c, having customers running on the terminal release isn’t the only reason to upgrade if the database is on an earlier release. As I’ve discussed in other posts, blogs and articles, I have numerous ways to address latency when losing cell node offloading, hybrid columnar compression (HCC), thin cloning with sparse clone, flash cache, flash logging,…
-
-
In my last post, I discussed some of the unique challenges migrating Oracle workloads from Exadata to Azure posed. Engineered systems are not your everyday lift and shift and are rarely simple. Although I covered some focus areas for success, I’d like to get into the migration philosophical questions around cell offloading and IO. cell information is referred to in the average Oracle 12c AWR report almost 350 times. That’s a LOT of data to consider when migrating a workload to a server that won’t have cell nodes to OFFLOAD TO. If cell nodes are creating a ton of different…
-
I know, I know- there’s a number of you out there thinking- I’m being brought in on more and more of these projects due to a recent change for some Exadata backup components many companies kept onsite, (parts that wear out more often, like PDUs and cell disks) which are no longer an option and that moving to Azure is a viable option for these workloads if you know what to identify and address before the move to the cloud. Engineered, Not Iron An Exadata is an engineered system- database nodes, secondary cell nodes, (also referred to as storage nodes/cell…
-
I’ve been busy reading and testing everything I can with Delphix, whenever I get a chance. I’m incredibly fascinated by copy data management and the idea of doing this with Exadata is nothing new, as Oracle has it’s own version with sparse copy. The main challenge is that Exadata’s version of this is kind of clunky and really doesn’t have the management user interface that Delphix offers. There is a lot of disk that comes with an Exadata, not just CPU, network bandwidth and memory. Now you can’t utilize offloading with a virtualized database, but you may not be interested…