What is OEM grid Agent?

i want to install 11g OEM grid monitoring tool. can you tall me what AGENT means? and what is it for?
ajaybeldeAsked:
Who is Participating?
 
cklautauConnect With a Mentor Commented:
You have to install the agent in any machine that you want to monitor.
The agent is responsible for collecting information on the machine and it sends info to grid server.
0
 
ajaybeldeAuthor Commented:
Do we need separate agent for each Database on a server?
0
 
Javier MoralesConnect With a Mentor Oracle DBACommented:
No, one agent may monitor several databases in a host, even several database versions.

I recommend you to install the last agent version 11.1.0.1  It works fine to collect data from databases Oracle9i, 10g and 11g... and so it works fine if your Oracle Grid Control is version Oracle10g.
0
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

 
ajaybeldeAuthor Commented:
Thanks
0
 
cklautauCommented:
Techlevel is correct: you need just 1 agent to monitor everything the machine hosts.
Be careful because some plugins are not free; you may monitor OS, databases (Oracle is free, of course), app server, etc...
0
 
Javier MoralesConnect With a Mentor Oracle DBACommented:
Yes, cklautau is right, some plugins of Oracle Grid Control are not free, but no worries about the agents...

And so, there's a consideration to agent install

If there's a host with 3 databases single instance, and that host belongs to a cluster... and you want to monitor a database that's in a container/zone (solaris) or package (hpux) that may "switchover" filesystems and services between the nodes, then you have to install one agent per database, and build the following architecture.

NODE 1
 - database standalone  orcl1
 - database standalone  orcl2
 - database standalone  orcl3
 - database in a zone     orclus1

NODE 2
 - database standalone  test1

you will have to install:
  - One agent per node 1, another for node 2 (to monitor the standalones).
  - and one aditional agent to monitor the oclus1 database, that switches when the database is switched between nodes.

Otherways, if you have to move the package/database to another node, the agent would raise "database is down" and the agent in node2 would not be able to monitor the new orclus1 database started up suddenly.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.