There have been a significant number of times where I've reviewed an AWR report and thought the best thing for an environment was to UnRAC it. The code and database design simply wasn't designed to run effectively or efficiently on RAC, resulting in high global cache waits, etc.
It's alright the DBA might want to simply keep their RAC skills up-to-date by having it- I understand, I've got 2 decades under my belt as a DBA. The thing is, there are so many cool new tools and products, like Azure CLI, Azure services and automation with DevOps to learn, there's plenty of new skills they'll acquire that will make them more valuable than just knowing Oracle RAC.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.