Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Database control is a web based tool for managing a single Oracle database that is installed on the same box as the database itself. Grid Control is a web based tool for managing multiple Oracle databases that can be installed on a separate server and has its own database.

We are currently using the 10g version of Grid Control and are considering the pros and cons of upgrading to the 11g version of Grid Control vs. abandoning it for DB Control. As such we would like to quantify what features/benefits we would loose and what features/benefits we would gain with each route. We are interested in the obvious as well as the obscure/smaller/intrinsic/potential.

share|improve this question
up vote 3 down vote accepted

In Oracle Grid Control you can make a global view of your entire enterprise. This is an advantage above DB Control. It is slightly easier to authorize employees for certain targets in Grid Control. If your mail gateway changes, you have the advantage of only one location to change. When making clones, Grid Control has the advantage of not having repository parts in the target databases.

On the other hand, DB Control is closer to the database and most of the times better support for new features. Oracle Grid Control Requires quite some resources to run and in many cases at least one dedicated dba to keep it running. You have no single point of failure for management. Oracle DB Control is very easy to setup. With a little smart thinking you can build a central page with links to all DB Consoles that you want, complete with links to the documentation. Grid Control easily gets mixed up when making clones, even without a local repository in the target.

I think it is a personal choice. At the moment, after having wrestled with many GC installations, I think having an own repository for historic data and links to Oracle DB Consoles is not a bad idea.

share|improve this answer
Wow! That mirrors my assessment very closely. I'm going to leave it open a bit longer to see if I can get a few other answers. Could you please explain your point about it being slightly easier to authorize employees for certain targets? Is it only easier when the user doesn't already have a login on the target or are there other situations in which it would be easier? – Leigh Riffel Apr 20 '11 at 12:54
It is easier to grant access to targets in GC because you have your administrators administrated in GC, with their privs. The access in the targets depends on what is defined in the targets. SSO would be so nice .... Too bad that it is such a setup work. – ik_zelf Apr 20 '11 at 13:28
I see. I was thinking that each GC user would also have a target user, but since that isn't necessary you are correct - the setup in that situation would be easier. We have local users for all our GC users, so the GC setup is an extra step we would like to do away with. SSO nice indeed. Thanks for your thoughts (+1). – Leigh Riffel Apr 20 '11 at 14:39

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.