User`s guide

Running the Installation Script
14-2 Oracle Database Installation and Administration Guide
The following table describes the parameters in the format:
Parameter Description
ORACLE_SID system identifier of
the database
ORACLE_HOME Oracle home
directory under
POSIX
ORACLE_DATA user ID where the
database files are
stored
Each database that should be monitored needs an entry in the oratab file. An
example for a valid
oratab file is:
# oratab file
# valid entries are of the following form:
# OR
ACLE_SID:ORACLE_HOME:N|Y:ORACLE_DATA
orcl:/ora11202/oracle/product/10g:N:$ORACLE
Note: The DBA group should have read and write access to the
oratab file and the oracle directory in the /var/opt folder.
■ Check the Oracle Management Agent release number. Oracle Management Agent
that ships with release 11.2 can monitor releases 10.x and 11.x. Monitoring of a
Oracle9i is not supported.
■ Ensure that you copy the appropriate LISTENER.ORA file to the $ORACLE_
HOME/network/admin
directory to monitor a LISTENER.
■ Ensure that you grant access to the alert file to all users, if you want to monitor a
database under a user ID different from the user ID of the Enterprise Management
Agent.
14.2 Running the Installation Script
It is recommended to install the Oracle Management Agent under a separate Oracle
Home directory. All Oracle users should belong to the same group, for example,
oracle. To start the installation enter:
/CALL-PROCEDURE $ORACLE1120.INSTALL.P.AGENT
You are prompted for the following:
Parameter Description
EMDROOT
This is the
Management Agent’s
home directory.
EM-AGENT-PORT The port on which
the Management
Agent should listen.