15 Oracle Management Agent

This chapter describes the Oracle Management Agent for BS2000/OSD and provides installation and configuration information. The reader is supposed to be familiar with Oracle Enterprise Manager.

The Oracle Management Agent for BS2000/OSD is responsible for monitoring all components on the host computer. Once installed, the Oracle Management Agent knows how to monitor default target types, such as the Oracle Database. For more information, refer to Oracle Enterprise Manager Concepts.

Preinstallation Issues

The following is a list of preinstallation issues:

The Management Agent requires the correction package 2/2007 of openNet Server v3.1 and openNet Server v3.2, respectively, in particular of the appropriate component Sockets v2.2 and Sockets v2.3, respectively.
Check if the BS2000/OSD POSIX subsystem is started
Check if the openNet Server tool netstat is installed under POSIX.
Check if jenv v5.0 is installed
Check if perl v5.8 is installed

If one of the required software packages is not installed, install the software package first before installing Oracle Management Agent.
The user address space should be 1GB
There should be at least 750MB disc space available on the POSIX file system
Make sure that the file /etc/hosts includes an entry with a loopback address for the localhost similar to the following example:
```
127.0.0.1 localhost local # loopback
```
Create a file /var/opt/oracle/oratab with the following format:
```
<ORACLE_SID>:<ORACLE_HOME>:<N|Y>:<ORACLE_DATA>
```
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 userid 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:
# <ORACLE_SID>:<ORACLE_HOME>:<N|Y>:<ORACLE_DATA>
orcl:/ora10202/oracle/product/10g:N:$ORACLE
```
Note:
The dba group should have read and write access on the oratab file. Oracle recommends that the DBA group should have read and write access to the oracle directory in the /var/opt/ folder.
If you want to monitor a 9i database, you have to manually create a dbs directory in the ORACLE_HOME of your Oracle9i installation.
For monitoring a LISTENER you have to copy the appropriate LISTENER.ORA file to the $ORACLE_HOME/network/admin directory.
If you want to monitor a database under a user-id different from the user-id of the Enterprise Management Agent, you have to make the alert file accessible to all users.

Parameter	Description
ORACLE_SID	system identifier of the database
ORACLE_HOME	Oracle home directory under POSIX
ORACLE_DATA	userid where the database files are stored

Running the Installation Script

It is recommended to install the Oracle Management Agent under a separate Oracle Home directory. All Oracle user should belong to the same group, e.g. dba. To start the installation enter:

/CALL-PROCEDURE $ORACLE1020.INSTALL.P.AGENT

You will be 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.
`EM-OMS-HOST`	The host name of the Oracle Management Server
`EM-OMS-HTTP-PORT`	The port of the Oracle Management Server
`EM-OMS-HTTPS-PORT`	The SSL port of the Oracle Management Server

To finalize the EM Agent installation login as root and execute the following script:

$EMDROOT/root.sh

Running the Agent

To run the agent, start a POSIX shell and type the following command:
```
emctl start agent
```
To stop the agent, start a POSIX shell and type the following command:
```
emctl stop agent
```
To get the status of the agent, start a POSIX shell and type the following command:
```
emctl status agent
```

Use the Oracle Management Agent for BS2000/OSD as described in the Oracle Database 10g Enterprise Manager book set.

Restrictions

The following is a list of issues that might affect Oracle Enterprise Manager Agent

Oracle Management Agent for BS2000/OSD can monitor servers that are running Oracle Database 9i or Oracle Database 10g.
The Oracle Management Agent for BS2000/OSD does not support the SNMP framework. That means, the agent is not integrated within the EMANATE master agent for BS2000/OSD. The agent does not accept any SNMP requests and does not send any SNMP trap. Therefore, the Oracle Management Agent for BS2000/OSD is not usable with third party SNMP management systems.
Oracle10g Database for BS2000/OSD supports only a minimal set of system statistics and these may not reflect the actual performance of the system.
Currently, Oracle Database 10g for BS2000/OSD only ships with the Oracle Enterprise Manager Agent. Oracle Enterprise Manager Grid Control Console is not supported, though this release does support a remote Oracle Enterprise Manager Grid Control Console.
Currently, the Management Agent supports only a minimal set of host metrics and these may not reflect the actual performance and only a part of the configuration of the system.

Troubleshooting

Typically, the Oracle Management Agent is monitored by an internal watchdog process and will be restarted in case of an error. This method does not prevent from any crashes where at least one task of the thread application is kept alive and might inhibit a proper restart of the Management Agent. If the Oracle Management Agent cannot be started or restarted, use the following instructions to resolve the issue:

CALL-PROCEDURE $TSOS.SYSPRC.PTHREADS.010(ITH-SHOW)

This procedure produces an output similar to the following:

%  BLS0523 ELEMENT 'ITHSHOW', VERSION 'V01.0C05', 
TYPE 'L' FROM LIBRARY ':OCT3:$TSOS.SYSLNK.PTHREADS.010' IN PROCESS%  BLS0524 LLM 'ITHSHOW', VERSION 'V01.0C05' OF '2006-10-18 16:40:35' LOADED
%  BLS0551 COPYRIGHT (C) Fujitsu Siemens Computers GmbH 2006. ALL RIGHTS RESERVED
LLM     = EMAGENT
MAIN    = IC@#MAIN    
LIBRARY = :ORA1:$ORA10202.ORALOAD.LIB
STARTED AT 2007-07-06-114314 FROM POSIX
TYPE  TSN   PID              JOB-TYPE   PRI      CPU-USED CPU-MAX ACCOUNT#
ORIG  987Y  1151  (X'047F')  3 DIALOG  *0 240     53.9535   32767 FSC
RESO  9877  1163  (X'048B')  3 DIALOG  *0 240     87.4625   32767 FSC
THRE  9878  1164  (X'048C')  3 DIALOG  *0 240    121.7945   32767 FSC

Here you find the TSNs of the tasks involved in the PTHREADS application. You can connect to the PTHREADS application when you choose the TSN of the ORIG task as the input for the parameter TSN of the ITH-START procedure in the following format:

/CALL-PROCEDURE $TSOS.SYSPRC.PTHREADS.010(ITH-START),(TSN=987Y)

When you see the double slash prompt you can type CANCEL-THREADED-PROGRAM to cancel the PTHREADS application. If the ORIG task is already terminated, you can terminate all other PTHREADS tasks by using the BS2000 system command

/CANCEL_JOB JOB-IDENTIFICATION=tsn

If the Management Agent is running on a SX machine in SPARC mode, then you must define the proper load library in the procedure parameters as follows:

/CALL-PROCEDURE $TSOS.SYSPRC.PTHREADS.010(ITH-START),(START-LIBRARY=$TSOS.SPULNK.PTHREADS.010,TSN=987Y)