1
Agent Configuration

The Oracle Intelligent Agents are processes running on remote nodes in the network. Oracle Enterprise Manager uses Intelligent Agents to run jobs, monitor events, and gather data on remote sites and to discover services on the node where it resides.

This Agent Configuration chapter discusses the following topics:

• Installing the Intelligent Agent on Windows NT on page 1-2
• Configuring SNMP on Windows NT on page 1-2
• Configuring an Intelligent Agent on Windows NT on page 1-2
• Installing the Oracle Intelligent Agent on UNIX on page 1-10
• Running the root.sh Shell Script on page 1-10
• Configuring SNMP on UNIX on page 1-12
• Configuring an Intelligent Agent on UNIX on page 1-13
• Configuring the Data Gathering Service on page 1-18
• Oracle Intelligent Agent and Oracle Names on page 1-22
• Roles and Users Required by the Agent on page 1-23
• Creating Password Files for Oracle NT DB on page 1-24

Please check the compatibility matrix in the Oracle Enterprise Manager Readme before installing or using Enterprise Manager. The readme is located in the $ORACLE_HOME\SYSMAN\ADMIN directory.

Installing the Intelligent Agent on Windows NT

Intelligent Agents are shipped with the database and installed on remote, managed machines. The Intelligent Agent must be installed in an ORACLE_HOME directory. The agent is installed as a service, called OracleAgent.

The Data Gatherer, which collects performance data used by the Oracle Capacity Planner and the new Java-based Oracle Performance Manager, is installed along with the Intelligent Agent. For information about configuring and upgrading the agent data gathering service, refer to Configuring the Data Gathering Service on page 1-18.

For information on installing the Intelligent Agent, please refer to the Oracle Enterprise Manager Installation (CD-ROM insert).

Configuring SNMP on Windows NT

Monitoring consoles use an SNMP Master Agent to communicate with the Intelligent Agent. The SNMP Master Agent and the Oracle Intelligent Agent must be configured correctly before the Oracle Intelligent Agent can communicate over SNMP to the Master Agent.

For the general procedures for configuring SNMP for Oracle databases and Oracle Enterprise Manager, refer to the Oracle SNMP Support Reference Guide.

For more comprehensive configuration information, see the installation or configuration guide specific to your platform since the SNMP configuration differs from platform to platform.

Configuring an Intelligent Agent on Windows NT

This section contains the following topics:

• Agent Discovery Algorithm on page 1-3
• Creating a Windows NT User Account for Running Jobs on page 1-4

Agent Discovery Algorithm

At agent startup, a script is executed which reads configuration parameters from the Windows NT registry, listener.ora file, and the tnsnames.ora file (if it exists).

The agent discovers new services on the machine where it is installed and creates/rewrites/appends to 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:

1. The agent reads the Windows NT registry for the values of the services installed on that machine.
2. Based on values of the services, the agent reads the listener.ora files to determine the SIDs and ORACLE_HOME directories of the databases which are serviced by that listener.
3. The agent also reads the listener.ora files for the global names of those databases (GLOBAL_DBNAME parameters).
4. If GLOBAL_DBNAME parameters are not found in listener.ora, the agent searches for a tnsnames.ora file in a location set by the TNS_ADMIN environment variable.
5. If the TNS_ADMIN variable, which is either in environment or Registry under ORACLE_HOME, is not set, the agent looks for a tnsnames.ora file in the standard location, $ORACLE_HOME\net80\ADMIN.
6. If the tnsnames.ora file is not found, the database alias, <SID>_<hostnames>, is assigned to a database service. The service will be known to the agent by this alias, and it will be visible as such at the Oracle Enterprise Manager Console.

If multiple aliases exist for the same instance in the TNSNAMES.ORA, the agent will use the one listed first. If you prefer to use a different alias, reorder the TNSNAMES.ORA entries and restart the Agent.

 

Note:  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.

   

Creating a Windows NT User Account for Running Jobs

In order for the agent to execute jobs on a managed node

• an NT user account must exist that has the advanced user right, "logon as batch job." The privilege can be assigned to an existing local or domain user, or a new NT user.
• the preferred credentials for the node must be set for that user in the Oracle Enterprise Manager console. Refer to Setting Preferences on page 2-12.
• the user must have read/write permissions to ORACLE_HOME\NET80 directory as well as write permissions to the TEMP directory or the ORACLE_HOME directory.

 

Note:  If you do not set up the "logon as batch job" privilege, you will receive the "Failed to authenticate user" message when you run jobs on the node.

   

Please follow one of the procedures listed below.

Creating a New NT User Account

To create a new Windows NT user account on the local NT machine (not the database) and grant the "log in as batch jobs" privilege to this user, perform the procedure below.

1. Select the User Manager from the Administrative Tools program group. See the Windows NT documentation for information on the tools.
2. Select New User from the User menu and check for the following:
• The "User Must Change Password at the Next Logon" option box is not checked
• "SYSTEM" or "system" is not used for the user name.
3. Under the Policies menu of the User Manager NT utility, select the User Rights option.
4. Check the "Show Advanced User Rights" box.
5. Select "Logon as a batch job" from the list of privileges.
6. Give the selected user this privilege.

Assigning Privileges to an Existing NT User Account

To assign privileges to an existing local user account, perform the following steps.

1. Choose the user on the User Manager panel and check for the following:
• The "User Must Change Password at the Next Logon" option box is not checked
• "SYSTEM" or "system" is not used for the user name.
2. Under the Policies menu of the User Manager NT utility, select the User Rights option.
3. Check the "Show Advanced User Rights" box.
4. Select "Logon as a batch job" from the list of privileges.
5. Add the advanced user right to this user.

Configuring a Domain User as Your Agent User

 

Note:  Domain users are not supported with 7.3.3 and earlier versions of the agent.

   

To configure a domain user as your agent user, perform the following steps.

1. Under the Policies menu of the User Manager NT utility, select the User Rights option.
2. Check the "Show Advanced User Rights" box.
3. Select "Logon as a batch job" from the list of privileges.
4. Click the Add button.
1. Fill in the "List Names From" field: (choose your domain)
2. Click Show Users button.
3. In the listbox, choose the domain user.
4. Click Add.
5. Click OK.
5. In the User Rights Policy window, click OK.

 

Note:  If you have both a local and a domain user with the same name, the local user takes precedence.

   

Controlling Operations of the NT Agent

This section contains information on controlling the agent through Windows NT and the DOS prompt. It also contains a section on troubleshooting the agent.
 

Note:  Oracle Enterprise Manager and the agent use Net8 to communicate with the databases in question. Please verify that Net8 can connect to every SID in question before attempting to use the agent.

   

Starting the Intelligent Agent on Windows NT

To start the agent on Windows NT, perform the following steps:

1. Double-click the Services icon in the Control Panel folder.
2. Select the OracleAgent service.

The Startup Type is set to Manual, which allows the agent to be started by a user. If you want the agent to start automatically whenever you start the system, set the Startup Type for Automatic.

1. Click the Startup push-button. A Service Startup dialog box appears.
2. Choose Automatic under the Startup Type.
3. Click OK on the Service Startup dialog box.
3. Click the Start push-button to start the agent.

Stopping the Intelligent Agent on Windows NT

To stop the agent on Windows NT, perform the following steps:

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.

Verify Agent is Running

To verify that the agent is running, look for its status in the control panel services or type netstart at a command prompt. OracleAgent should appear in the list of services.

You may also view the NT Task Manager to see the dbsnmp process information.

Starting, Stopping, and Verifying the Status from the DOS prompt

To start or stop the Agent from the DOS command prompt, enter the appropriate command. From the DOS command prompt, you can also verify that the service is running.

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
Verify status of the agent from the DOS prompt	net start

 

Troubleshooting the NT Agent If It Did Not Start Up

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.

1. Check for messages written to the NT Event Viewer (under Administrative Tools) since this is where the NT agent writes any problems associated with startup.
2. Check if snmp_ro.ora, snmp_rw.ora, and services.ora are created by the agent on startup. snmp_ro.ora and snmp_rw.ora are in the ORACLE_HOME\NET80\admin directory, and services.ora is in the ORACLE_HOME\NET80\agent directory.

Compare the services listed with the services which are available on the machine. Please refer to Appendix A, "Configuration Files" for valid sample files.


If services are missing, check the following files for inconsistency or corruption:

• listener.ora
• tnsnames.ora
3. Check that you do not have a system path set to external drives.

The agent is a service and runs by default as SYSTEM. It also needs DLLs from the ORACLE_HOME/BIN directory. If you need mapped drives in your path, you MUST NOT set them in the SYSTEM path.


To set your own path:

1. Move mapped drive paths out of SYSTEM path variables and into your own.
2. Reboot to "unset" the systems path.
4. Check if you have TCP/IP installed. TCP/IP is a requirement.
5. If you still do not know why the agent did not start, trace the agent.
1. Set the following variables in snmp_rw.ora:

nmi.trace_level=admin (or 16 if you want maximum information)


nmi.trace_directory=<any directory in which the Oracle user has write privileges>

2. Restart the agent.
3. Check the log files located in the ORACLE_HOME/NET80/LOG directory.

NMI.LOG should show general agent problems.


NMICONFIG.LOG should show problems with autodiscovery.

6. Ensure that the DNS Host entry is set to the node name in the listener.ora and tnsnames.ora files.
1. Run the start button-> settings-> control panel-> network-> protocol-> TCP/IP properties.
2. Check the DNS Host entry. For example, make sure that the entry is not set to the name of the previous engineer.
7. Turn on tracing for the daemon.
1. Open net80/admin/sqlnet.ora and add the lines daemon.trace_level=13 and daemon.trace_directory=e:\orant\net80\trace.
2. Close the console to stop the daemon.
3. Open the console to restart the daemon in trace mode.
4. Submit a job and view the daemon.trc file for daemon and console problems.

Installing the Oracle Intelligent Agent on UNIX

Install the Oracle Intelligent Agent from the Oracle CD-ROM as per the Oracle Enterprise Manager Installation Guide. The Intelligent Agent is a separate component to select.

Running the root.sh Shell Script

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 the file where the user will place references to all databases 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.

To run a setuid program,

chown root dbsnmp
chmod 755 dbsnmp

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:  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.

   

The node credentials, the preferred credentials settings for the node, should be set to the user who starts the agent. It is the current username and password which appear when you click File-> Preferences and highlight the desired node name.

The user who submits node jobs to the UNIX node should ultimately be the owner of the ORACLE_HOME or the same user who started the Intelligent agent on UNIX. If the root.sh does not have the setuid set, then any job submitted to the agent will run with the privileges of the user indicated above. root.sh will allow the user to set the preferred credentials for that node to impose its privileges on the job.
 

Note:  Please be aware that only one intelligent agent can be run on one UNIX machine although more than one Oracle Home can exist.

    

Note:  If you have a 7.3.3 or below agent, installing an 8.0.x database is not recommended.

   

Verifying that root.sh Had Been Run Successfully

To verify that root.sh had been run successfully, check the file permissions on dbsnmp.

1. Enter cd $ORACLE_HOME/bin

This changes the directory to the $ORACLE_HOME/bin directory where the agent executable resides.

2. Enter ls -al dbsnmp

This lists all relevant details about dbsnmp.

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. If root is the owner and -rwsr-xr-x are the permissions, then root.sh had been run successfully.

Running root.sh

Check the oratab file for entries for the database SIDs and Oracle Homes. Please refer to the Agent Discovery Algorithm on page 1-13 and your operating system-specific manual for the location of the oratab file.

Values of the Oracle Homes and SIDs should have been written by the root.sh shell script. If there are no entries in the oratab file, perform the following steps:

1. Switch user to root by typing

su root

2. Change directory to the $ORACLE_HOME/orainst directory by typing

cd $ORACLE_HOME/orainst

3. Run the root.sh shell script by typing

./root.sh

4. Answer the questions asked. For each database created, the entry is of the form: <SID>:<$ORACLE_HOME>:[Y/N]

You will then be automatically exited out of root.sh.

Configuring SNMP on UNIX

Monitoring consoles use an SNMP Master Agent to communicate with the Intelligent Agent. The SNMP Master Agent and the Oracle Intelligent Agent must be configured correctly before the Oracle Intelligent Agent can communicate over SNMP to the Master Agent.

For the general procedures for configuring SNMP for Oracle databases and Oracle Enterprise Manager, refer to the Oracle SNMP Support Reference Guide.

For more comprehensive configuration information, see the installation or configuration guide specific to your platform since the SNMP configuration differs from platform to platform.

Configuring an Intelligent Agent on UNIX

This section contains the following topics:

• Agent Discovery Algorithm on page 1-13
• Setting the $ORATAB/ORATAB System Environment on page 1-14

Agent Discovery Algorithm

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.
 

Note:  Before attempting to start the agent, please test the Net8 connectivity by using the tnsnames aliases to connect to different SIDs. The agent depends on valid configurations of tnsnames.ora and listerner.ora. Refer to Testing the Connectivity to Any SID on page C-4.

   

To determine what services are available on its machine (services that the agent will manage), the agent uses the following discovery algorithm

1. The agent reads the oratab file for values of all the Oracle Homes and SIDs. Depending on the platform, the oratab file can be located in either of the following locations:
• /etc
• /var/opt/oracle
2. Based on the Oracle Homes values found in oratab, the agent reads the listener.ora files to determine which databases are serviced by that listener.
3. The agent also reads the listener.ora files for the global names of those databases (GLOBAL_DBNAME parameters).
4. If GLOBAL_DBNAME parameters are not found in the listener.ora file, the agent searches for tnsnames.ora files in a location set by the TNS_ADMIN environment variable. The standard location of thetnsnames.ora file is $ORACLE_HOME/network/admin. On Solaris the tnsnames.ora can be located in the /var/opt/oracle directory. On other UNIX systems, the tnsnames.ora can be located in the /etc directory. You can set a $TNS_ADMIN environment variable if you do not want to use any of the default locations.
5. If the TNS_ADMIN variable is not set, the agent looks for tnsnames.ora files in the standard locations. For example: $ORACLE_HOME/NETWORK/admin.
6. If tnsnames.ora files are not found, the database aliases are created as <SID>_<HOSTNAME>.

If multiple aliases exist for the same instance in the TNSNAMES.ORA, the agent will use the one listed first.If you prefer to use a different alias, reorder the TNSNAMES.ORA entries and restart the Agent.

 

Note:  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.

   

Setting the $ORATAB/ORATAB System Environment

It is recommended that you set the $ORATAB/ORATAB system environment variable before starting the agent.

The 733 and later agents on UNIX look at the ORATAB file to get a list of databases and their locations local to the server. The file contents look like this:

v732:/u01/oracle/product/7.3.2:n

v733:/u02/oracle/product/7.3.3:y

v732 and v733 are the names of the SIDs, followed by the ORACLE_HOME and then either a "y" or "n" for automatic startup.

To set the oratab environment variable ($ORATAB), type:

setenv ORATAB /etc/oratab

In the example above, ORATAB is the name you want to call the environment variable and /etc/oratab is the location and file to be used.

Controlling Operations of the UNIX Agent

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 in ORACLE_HOME/net80/agent/doc/readme.wri or ORACLE_HOME/network/agent/doc/readme.wri.

Troubleshooting the UNIX Agent If It Did Not Start Up

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.

1. Check the ORACLE_HOME/NETWORK/log/dbsnmp*.log file for errors on UNIX.
2. Check that the Oracle user has write permissions to ORACLE_HOME/AGENT/LOG as well as ORACLE_HOME/NETWORK/AGENT.
3. Check snmp_ro.ora, snmp_rw.ora, and services.ora for the entries created by the agent. snmp_ro.ora and snmp_rw.ora are in the ORACLE_HOME/NETWORK/ADMIN directory, and services.ora is in the ORACLE_HOME/NETWORK/AGENT directory.

Compare the services listed with the services which are available on the machine. Please refer to Appendix A, "Configuration Files" for valid sample files.


If services are missing, check the following files for inconsistency or corruption:

• listener.ora
• tnsnames.ora
• oratab
4. If you still do not know why the agent did not start, trace the agent by setting the following variables in snmp_rw.ora:
• nmi.trace_level=admin (or 16 if you want more information)
• nmi.trace_directory=<any directory which the Oracle user can write to>
• nmi.trace_file=agent
5. If you have upgraded the database software and one of your machines is having problems with the generated snmp_ro.ora, snmp_rw.ora or services.ora file, follow the instructions below:
1. Run catsnmp.sql under the INTERNAL or SYS account (NOT the dbsnmp account). Normally the catsnmp.sql script is run from catalog.sql upon database creation but since this is an upgrade, you may not have run this script yet. If the necessary scripts have not been run, the dbsnmp account is not created.
2. If you have more than one SID or older SIDs referenced in the oratab, run catsnmp.sql against each of them also.
3. The snmp_ro.ra file is a read only file which means that all changes to the file will be overwritten each time the agent is started. You can make changes (if needed) to the snmp_rw.ora file.

If you are trying to do backups, you must run backupts.sql with the dbsnmp/dbsnmp account.

 

Warning:  Please do not modify the tcl scripts (job and events scripts written in Tool Command Language) 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.

   

Configuring the Data Gathering Service

This section contains information on configuring the data gathering service for collecting Oracle database and host information.

Oracle Data Gatherer, which is part of the Oracle Enterprise Manager framework, collects performance data. This performance data is used by the Oracle Capacity Planner and the new Java-based Oracle Performance Manager. If you are not using either of these two products, you do not need to install and configure the agent data gathering service.

Requirements

The data gathering service (Oracle Data Gatherer) is intended to be located on the host where the monitored target (database or host) is physically located. In order to use the data gathering service to collect host-based performance statistics, Oracle Data Gatherer must be located on the monitored host.

However, in the case of collecting performance statistics for databases, Oracle Data Gatherer is not required to be installed and configured on the host where the database is located. Because it can collect database statistics remotely, Oracle Data Gatherer may be installed and configured on another node. Both the Oracle Capacity Planner and Oracle Performance Manager provide the ability to access performance statistics for a database through a data gathering service on an intermediate node.

It may be necessary or desirable to use this type of intermediate node data gatherer for the following scenarios:

• If the database to be monitored is a version before 8.0.4. Oracle Data Gatherer is introduced with 8.0.4 of the Oracle database and is not currently available in a configuration that can be installed with a pre-8.0.4 database.
• If an additional process footprint/overhead cannot be tolerated on the host where the monitored database is located. Of course the collection activity will still take place against the database, and that overhead will be present regardless of whether the data gathering service is located remotely or not.

Remember, however, that if Oracle Data Gatherer is not available on a host machine, then it is not currently possible to collect any host/operating-system performance statistics. This configuration limits data collection to database data on remote hosts.

Oracle Data Gatherer is installed along with the Intelligent Agent.

Upgrading the Data Gatherer

If you have a previous version of Oracle Data Gatherer installed and you have installed the new version of Oracle Data Gatherer into a different Oracle Home from the previous version, you should move the Capacity Planning configuration (called state files) and data files associated with the previous version of Oracle Data Gatherer to the Oracle Home where you have installed the new version of Oracle Data Gatherer.

The Oracle Data Gatherer state and data files are located in the odg/reco directory below the Oracle Home ($ORACLE_HOME/odg/reco) directory.

If you do not move these files, any binary data files created by Oracle Data Gatherer which have not yet been loaded into the Capacity Planner database will be lost, and the setup of what data is being collected for Capacity Planner will need to be entered into the Capacity Planner again following the installation of the new Oracle Data Gatherer.

It is not necessary to move any of these files if you have installed the new version of Oracle Data Gatherer into the same Oracle Home as the previous version or if you do not currently use the Oracle Capacity Planner.

Controlling Operations of the NT and UNIX Data Gathering Service

On UNIX and NT, Oracle Enterprise Manager uses the vppcntl command to manage the data gathering service. The vppcntl executable is located in ORACLE_HOME/bin.

Commands to control Oracle Data Gatherer are listed in the table below:

If you want to...	Enter the command...
Start Oracle Data Gatherer	vppcntl -start
Stop Oracle Data Gatherer	vppcntl -stop
Verify that Oracle Data Gatherer is running	vppcntl -ping
Identify the version of Oracle Data Gatherer	vppcntl -version

 

Additional Methods for Controlling Operations on Windows NT

This section contains information on controlling Oracle Data Gatherer through Windows NT and the DOS prompt.

To start Oracle Data Gatherer through the Control Panel on Windows NT, perform the following steps:

1. Double-click the Services icon in the Control Panel folder.
2. Select the OracleDataGatherer service.

The Startup Type is set to Manual, which allows the data gathering service to be started by a user. If you want Oracle Data Gatherer to start automatically whenever you start the system, set the Startup Type for Automatic.

1. Click the Startup push-button. A Service Startup dialog box appears.
2. Choose Automatic under the Startup Type.
3. Click OK on the Service Startup dialog box.
3. Click the Start push-button to start the data gathering service.

To start Oracle Data Gatherer from the DOS command prompt, enter the following command:

net start oracledatagatherer

To stop Oracle Data Gatherer through the Control Panel on Windows NT, perform the following steps:

1. Double-click the Services icon in the Control Panel folder.
2. Select the OracleDataGatherer service.
3. Click the Stop push-button to stop the data gathering service.

To stop Oracle Data Gatherer from the DOS command prompt, enter the following command:

net stop oracledatagatherer

Verify Data Gathering Service is Running

On Windows NT, use vppcntl -ping to verify if Oracle Data Gatherer is running. Then, look for its status in the control panel services. You may also view the NT Task Manager to see the vppdc process information. The data gathering service's message log is ORACLE_HOME\odg\bin\alert_dg.log.

On UNIX, use vppcntl -ping to verify if Oracle Data Gatherer is running. The data gathering service's message log is $ORACLE_HOME/odg/bin/alert_dg.log.

Using vppcntl -ping or checking the status of the OracleDataGatherer service in the control panel are different ways of checking if Oracle Data Gatherer is running. vppcntl -ping is the preferred way of checking the status of Oracle Data Gatherer.

Oracle Intelligent Agent and Oracle Names

The Intelligent Agent 8.0.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 Oracle Enterprise Manager Console.

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.

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.
 

Note:  Please make sure that you are connected to this DBNAME and SID by testing the Net8 connections on that same server. Check the Net8 configuration for further information.

   

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".
 

Note:  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.

   

Roles and Users Required by the Agent

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).

For security reasons, the customer may need to change the user/password for the Intelligent Agent's database logon. The default account is dbsnmp and the default password is dbsnmp. To change the user name and password to something other than dbsnmp/dbsnmp, you need to open, edit, and rerun catsnmp.sql for your own user and password before you edit the snmp_rw.ora.

The following parameters (connect lines) are needed if you have modified the account and/or password for the agent. You may add them to the snmp_rw.ora file in the ORACLE_HOME/NET80/ADMIN when you run the catsnmp.sql script:

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 or INTERNAL.
 

Note:  The location of catsnmp.sql varies based on the database version you are running and the platform. For example, on NT for an Oracle 8.0.4 database, the script is located at ORACLE_HOME\rdbms73\admin. Please note that there is no harm in running the catsnmp.sql script more than once.

   

Creating Password Files for Oracle NT DB

Use the Password Utility ORAPWD80 to create password files. ORAPWD80 is automatically installed with the Oracle8 Utilities. Password files are located in the ORACLE_HOME\DATABASE directory and are named PWDSID.ORA, where SID identifies the Oracle8 database instance. Password files can be used for local or remote connections to an Oracle8database. The example below describes how to perform a local connection.

For example, to create a password file with ORAPWD80:

C:\> ORAPWD80 FILE=ORACLE_HOME\DATABASE\PWDSID.ORA PASSWORD=PASSWORD

---