Oracle Enterprise Manager Configuration Guide | ![]() Library |
![]() Product |
![]() Contents |
![]() Index |
The Oracle Intelligent Agents are processes running on remote nodes in the network. Oracle Enterprise Manager uses Intelligent Agents for the following tasks:
This Agent Configuration chapter discusses the following topics:
Topics | Page |
---|---|
Intelligent Agents are shipped with the database and installed on remote, managed machines. The Intelligent Agent must be installed in the ORACLE_HOME directory.
For information on installing the Intelligent Agent, please refer to the Oracle Enterprise Manager Installation (CD-ROM insert).
This section contains the following topics:
Topic | See Page |
---|---|
At startup, the agent discovers new services on the machine where it is installed and creates its configuration files: snmp_ro.ora, snmp_rw.ora, and services.ora.
To determine what services are available on its machine (services that the agent will manage), the agent uses the following discovery algorithm:
If a database or any other new service is installed on the node where the agent resides, the agent must be restarted to add the new service to the agent configuration files.
In order for the agent to execute jobs on a managed node
To create a new local Windows NT user account, perform the following steps
To assign the privilege to an existing account, perform the following steps.
If you have both a local and a domain user with the same name, the local user takes precedence.
Remember that the preferred credentials in the Console need to be set for this user. Refer to Setting Preferences on page 2-9.
This section contains information on controlling the agent through Windows NT and the DOS prompt. It also contains a section on troubleshooting the agent.
To start the agent on Windows NT, perform the following steps:
To stop the agent on Windows NT, perform the following steps:
Step | Action |
---|---|
1 |
Double-click the Services icon in the Control Panel folder. |
2 |
Select the OracleAgent service. |
3 |
Click the Stop push-button to stop the agent. |
To start or stop the Agent from the DOS command prompt, enter the appropriate command.
If you want to... | Enter the following command |
---|---|
Start the agent from the DOS prompt |
net start oracleagent |
Stop the agent from the DOS prompt |
net stop oracleagent |
To verify that the agent is running, look for its status in the control panel services.
Make sure the agent service is up by checking the OracleAgent service in your control panel. If the agent did not start up, use any of the following hints listed below.
Install the Oracle Intelligent Agent from the Oracle CD-ROM. The Intelligent Agent is a separate component to select.
After you have successfully installed the agent, the Oracle Installer prompts you to run root.sh.
root.sh, which is a shell script, updates/creates an oratab file. The oratab file is a list of all services to be discovered by the agent and controlled by the Oracle Enterprise Manager. For each database created, the entry is of the form: <SID>:<$ORACLE_HOME>:[Y/N]
The agent is normally configured by root.sh as a setuid program. If root.sh was successful, the agent will have been installed as setuid root so that the agent can run jobs as the users whose name and password are given in the Preferred Credentials for that host.
If the agent is not a setuid program, all Enterprise Manager jobs are run with the permissions of the user who started the agent.
Note that the agent being set to setuid root does not have the same effect as having the root user start the agent. Having the root user start the agent may cause security problems. Consult your platform documentation for exact details on setuid programs.
To verify that root.sh had been run successfully, perform the following steps:
The output of the ls -al command for dbsnmp should be in the form
-rwsr-xr-x 1 root g651 1497980 Jun 12 21:04 dbsnmp
root is the owner. dbsnmp is the agent executable. In this example, the name of the group is g651.
The oratab file must have entries for the database SIDs and Oracle Homes. These entries are written by root.sh shell script. If root.sh was not successful, perform the following steps:
su root
$
ORACLE_HOME/orainst
directory by typing
cd $ORACLE_HOME/orainst
./root.sh
This section contains the following topics:
Topic | See Page |
---|---|
At startup, the agent discovers new services on the machine where it is installed and creates its configuration files: snmp_ro.ora, snmp_rw.ora, and services.ora.
To determine what services are available on its machine (services that the agent will manage), the agent uses the following discovery algorithm
If a database or any other new service is installed on the node where the agent resides, the agent must be restarted to add the new service to the agent configuration file.
$ORACLE_HOME/network/agent
directory.
On UNIX, Oracle Enterprise Manager uses the lsnrctl to start and stop the agent. The relevant lsnrctl commands to control the UNIX agent are listed in the table below.
If you want to... | Enter the command... |
---|---|
Start the agent on UNIX platforms |
lsnrctl dbsnmp_start |
Stop the agent on the UNIX platform |
lsnrctl dbsnmp_stop |
Verify status of the agent |
lsnrctl dbsnmp_status |
For additional information or restrictions for your platform, see the Intelligent Agent README.
Make sure agent listener is working. Enter the command:
lsnrctl dbsnmp_status
If the agent did not start up, use any of the following hints listed below.
If you want to launch jobs and events against several databases, the Oracle tools must be installed in the same $ORACLE_HOME as the same release of the agent. By default, the tcl scripts will locate the tools from the $ORACLE_HOME of the agent.
Please do not modify the tcl scripts which come with the agent. If you want to submit a job different than the ones that are predefined with the agent, use the TCL Job where you are allowed to pass in arbitrary scripts and have the agent execute them.
The Intelligent Agent 7.3.4 does not use Oracle Names to discover services it manages. It uses GLOBAL_DBNAME parameters in listener.ora files to determine which databases that listener services. The Oracle Enterprise Manager console then uses the GLOBAL_DBNAME parameters to name the database in the hierarchal view.
The GLOBAL_DBNAME parameter typically describes the name of the database as it is registered with the Names Server, for example, the name and domain of the database as given in the database initialization parameter file. Values of the GLOBAL_DBNAME parameters must be unique.
Agents prior to version 7.3.4 did not use the GLOBAL_DBNAME parameters from listener.ora. For example, Intelligent Agent 7.3.3 does not use the GLOBAL_DBNAME parameters. Instead, it polls the tnsnames.ora file for database services to add to the Oracle Enterprise Manager console.
If you are running Oracle Names on a machine managed by an Oracle Intelligent Agent, it is assumed that the databases have already been registered with a Names Server and their aliases are defined by the GLOBAL_DBNAME parameters in the listener.ora files.
When running jobs or monitoring events in this environment, the Intelligent Agent does not resolve database aliases via Oracle Names.
For more information on how the Enterprise Manager Console works with Oracle Names, see Chapter 2, Console Configuration.
If you are planning to manage two or more Oracle databases on the same node, make sure the GLOBAL_DBNAME parameters in your listener.ora
files are different for all databases.
The catsnmp.sql script is only installed when you install the database. When an Oracle database is installed, the catsnmp.sql script is automatically run by catalog.sql to create the necessary dbsnmp user account (the user dbsnmp with password dbsnmp) and the SNMPAGENT role for the Intelligent Agent (for 7.3.3 and later).
If you want to change the user name and password, you need to open, edit, and run catsnmp.sql for your own user and password before you edit the snmp_rw.ora
.
The following parameters are not automatically generated, but may be added to the file:
SNMP.CONNECT.<svcname>.NAME = <USERNAME> SNMP.CONNECT.<svcname>.PASSWORD = <password>
To determine whether the SNMPAGENT role exists in a database, enter the following SQL command:
SELECT * FROM dba_roles;
If the SNMPAGENT role does not appear, run the catsnmp.sql script on the database.
If you already have several versions of the database running, you must run the catsnmp.sql script on each of these database in order to have the correct setup for all the grants and views the agent needs to contact.
To run the script, you must log in as SYS.
The location of catsnmp.sql varies based on the database version you are running and the platform. For example, on NT for an Oracle 7.3.4 database, the script is located at ORACLE_HOME\rdbms73\admin.
![]() ![]() Prev Next |
![]() Copyright © 1997 Oracle Corporation. All Rights Reserved. |
![]() Library |
![]() Product |
![]() Contents |
![]() Index |