|Oracle Intelligent Agent User's Guide
Part Number A85251-01
This chapter provides a brief overview of the Intelligent Agent. The following topics are covered:
The Oracle Intelligent Agent is an autonomous process running on a remote node in the network. The Agent resides on the same node as the service it supports. However, the Agent can support more than one service on a particular node. For example, if two databases are installed on one machine, a single Agent can support both databases. The Agent is responsible for:
For information on configuring the Agent, see the Oracle server platform-specific installation documentation for your system.
Enterprise Manager version 1 does not use version 2's middle-tier Management Server. Because this manual is geared towards users of both version 1 and version 2, users of Enterprise Manager version 1 should ignore references to the Management Server.
Intelligent Agents are autonomous because they function without requiring that the Console or Management Server be running. An Agent that services a database can run when the database is down, allowing the Agent to start up or shut down the database. The Intelligent Agents can independently perform administrative job tasks at any time, without active participation by the administrator. Similarly, the Agents can autonomously detect and react to events, allowing them to monitor the system and execute a fixit job to correct problems without the intervention of the administrator.
The Agents operate independently of the Console and Management Server and are able to execute jobs and monitor events when the administrator has logged out of the Console. The Agents queue any job or event messages destined for that administrator, and deliver them to the Management Server. When the administrator logs in to a Console again, the Management Server delivers pending messages to the administrator who is currently logged in. Information about the state of jobs and events are stored in files on the Agent's node. These files have a ".q" extension and are stored in the $ORACLE_HOME/network/agent directory.
Jobs and events are implemented as Tcl scripts. When the Agent executes a job or tests for an event, it runs the appropriate Tcl script.
When the Management Server sends a message to an Agent on behalf of an administrator logged into the Console, it also sends the information about the administrator's language and character set environment. The Agent uses the NLS environment information when it performs database administration tasks on behalf of the administrator. This allows administrators to manage databases in their native languages. For example, an administrator in France can administer a database in Germany and receive messages in French.
The Agent supports Simple Network Management Protocol (SNMP), allowing third-party systems management frameworks to use SNMP to receive SNMP traps directly from the Agent. The Agent provides access to Oracle's database Management Information Base (MIB) variables. You can submit jobs or events that access Oracle MIB variables even when the database resides on a platform that does not support SNMP. For more information on SNMP, see the Oracle SNMP Support Reference Guide.
The data gathering service (also known as Oracle Data Gatherer) is used to collect performance data.
The Oracle Data Gatherer is responsible for handling requests from client applications (for example, Oracle Capacity Planner and Oracle Performance Manager) that want to collect data. For each client application, you specify the performance data to collect (for example, file I/O or CPU usage data) and the time interval between data samples. The Oracle Data Gatherer then collects the requested data for the client at the specified interval.
The Oracle Data Gatherer is part of the Oracle Intelligent Agent, and it is automatically installed when the Agent is installed on a managed host. Therefore, in the following sections, any reference to the Oracle Data Gatherer being installed on a host means that the Oracle Data Gatherer service was installed on the host when the Agent was installed on the host.
The Oracle Data Gatherer collects performance data for:
In general, the Oracle Data Gatherer should be configured on the host where the target (database or host) to be monitored is physically located. In other words, if you want the Oracle Data Gatherer to collect database data from the MEDICAL database on host BENEFITS, then the Oracle Data Gatherer should be installed and configured on host BENEFITS. Similarly, if you want the Oracle Data Gatherer to collect operating system data on host EMPLOYEES, then the Oracle Data Gatherer should be installed and configured on host EMPLOYEES.
In some cases, however, it may not be possible to install and configure the Oracle Data Gatherer on a particular host. The Oracle Data Gatherer can be installed on a host only when both the following requirements are met:
If a host does not meet these requirements, the Oracle Data Gatherer cannot be installed on the host, which means that the Oracle Data Gatherer will not be able to collect operating system statistics from the host. However, you can collect database data from a host on which the Oracle Data Gatherer cannot be installed and configured.
To collect database data from a host on which the Oracle Data Gatherer cannot be installed and configured, install and configure the Oracle Data Gatherer on a different host that meets both of the requirements. You can then use the Oracle Data Gatherer on this host to collect database data remotely on hosts that do not have the Oracle Data Gatherer installed. This is called using an intermediate host Oracle Data Gatherer.
For example, suppose you want to collect database data for the CONSULTANTS database on host EMPLOYEES, but the Oracle Data Gatherer cannot be installed and configured on host EMPLOYEES. If the Oracle Data Gatherer is installed and configured on host BENEFITS, you can use the Oracle Data Gatherer on BENEFITS as an intermediate host Oracle Data Gatherer. The Oracle Data Gatherer on BENEFITS is able to collect database statistics from the CONSULTANTS database on host EMPLOYEES.
You might also want to use an intermediate host Oracle Data Gatherer if an additional process footprint/overhead cannot be tolerated on the host where you want to collect database data. Of course, in this situation the collection activity will still take place against the database. This minimal collection activity overhead will be present regardless of the host where the Oracle Data Gatherer is located.