EM12c and Hardware
I often hear, “My EM12c environment is slow!” and I just as often am granted access to the environment and find out that EVERYTHING is running on an old single core server with 2Gb of RAM someone found lying around. Enterprise Manager is often an after thought to many IT organizations. After all the work has gone into the production environments that build revenue, there is often a disconnect on how important information on the health and status of those revenue machines are, resulting in Enterprise Manager receiving the “cast off” servers for their hosted environment.
So today we are just going to talk about sizing out an EM12c environment- no tuning, yet, (but we’ll get to it!)
How does the team I work with decide what recommendations to make and why is it important to make those recommendations?
The questions to ask when designing or upgrading an EM12c environment are:
- How many targets will you be monitoring?
- Here are the features we have available outside of just the basic monitoring, etc. What do you foresee the business finding the most value in?
- How many users will be accessing the Enterprise Manager console?
- Do you have any unique firewall or network configurations?
The basic sizing recommendations, along with recommendations to meet MAA, (Maximum Availability Architecture) are shown below, decision factors are on number of targets and users*:
Armed with this info, is your EM12c environment under-size or under-powered? Next, we’ll talk about why the database is not the only thing you should be tuning in your EM12c environment and why the SCP, (Strategic Customer Program) has so much value!
*There are other factors, including features, management packs, plug-ins, etc. that can also impact the build and design of an EM12c environment for optimal performance.
Pingback: EM12c and Hardware - Oracle - Oracle - Toad World
Very Valuable info.. Thanks. Looking forward for OMS and Repository tuning stuff.
Thanks,
– Amitabh
Great post Kellyn. I wanted to add to it with one more point that often enough there’s a disconnect between what is actually slow, EM or the actual target the user is accessing via the tool.
A perfect example is when a user accesses a Database Target during a period where it experiences “slowness”. This is often misinterpreted as EM slowness. What the end user may not realize is, when they’re accessed the “Performance” tab for a Database Target, they are actually logged into the managed instance.
That being said, I’m sure an undersized EM server is a definite cause for actual EM slowness.
Cheers!
Maaz
Yes, but not there yet, Maaz, this post was about sizing an EM environment. We won’t get to different areas of tuning for a bit yet and knowing what is causing the pain.
Pingback: EM12c and Hardware | DBA Kevlar | COPY SOFT