By rickramsey on Jul 15, 2011
photo courtesy of Square Space.
I don't like to budget my spending, I don't like to count my calories, and I don't like to plan my rides too carefully. Takes all the adventure out of life.
But it's different at work.
If you are accustomed to working with either the resource manager for Oracle Solaris or the resource manager for Oracle Database, you may be wondering what the other resource manager is for. Can you simply pretend it doesn't exist until the quarter is over? Or will it act like your wife's cat and break something if you ignore it? Could it, perhaps, be better than the one you're used to? What if you combined them?
This might help ...
This white paper not only describes the differences between Oracle's Solaris resource manager and its database resource manager, it shows you how to use them together in the best way. Apparently that's referred to as consolidated resource management. (If you ask me, they shoulda called it amalgamated resource management, but the people in the Naming Department stopped consulting me years ago, after I suggested they name the next SunOS Jaws.)
(Think about it. Java on Jaws. It woulda rocked.)
Anyhow, because it is a white paper, it does spend a little time talking about resource management in general and the role of Oracle's resource managers in server workload consolidation. Did you know that resource management is particularly good at maintaining a service level agreement (SLA)? It makes sense, right, but it's not something I would have used to start a conversation in a biker bar. What I did know is that SLA used to mean Symbionese Liberation Army).
Control mechanisms, which resource manager to use for what, and how this all plays in a high-availability environment are also covered in this first of four papers on resource management. Read it. You'll learn a lot that you thought you already knew.- Rick
System Admin and Developer Community of OTN
OTN Garage Blog
OTN Garage on Facebook
OTN Garage on Twitter