What are the pros/cons of Oracle's Grid Control compared to DB Control? 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.
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.