OEM overhead in performance monitoring

Question

Is it necessary to use OEM Grid Control, not the local Database Control, to avoid the overhead of monitoring? Should I install OEM Grid on another server to monitor the performance of I/O, CPU, and other indicators on my database server?

Answer 1

830252 wrote:
I hoped for the answer that the Grid Control is not necessary. I have only one database instance to monitor and the Grid Control requires several pieces to be installed, agents, WebLogic server and a database for the repository, plus some patches. This seems to be a bigger project in itselft. There is a long list of requirements and pre-requisites. The monitoring that I need to do is actually very limited in scope. I have only parts of the applications to monitor at the performance testing time. This is not a system in production.The basic functionality for monitoring and administering a single database is pretty much the same. What Grid Control brings to the table is a single portal for administering multiple databases. If you only have one db, Grid would be overkill for no additional benefit.
And contrary to what some think, you can use dbcontrol when handling multiple databases, but each db will have to have its own instance of dbcontrol, and if they are on the same host, they will each need to be configured with its own port, and thus will be accessed with its own url.