Skip Headers
Oracle® Database Installation and Administration Guide
11g Release 2 (11.2) for Fujitsu BS2000/OSD

Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

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

This chapter describes the following sections:

14.1 Preinstallation Issues

The following is a list of preinstallation issues:

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:


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.
EM-OMS-HOST The host name of the Oracle Management Server
EM-OMS-HTTP-PORT The port of the Oracle Management Server

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


The installation of the Management Agent, can also be operated by a background process. In this case, the parameters EMDROOT, EM-AGENT-PORT, EM-OMS-HOST and EM-OMS-HTTP-PORT are mandatory parameters and must be specified with the following procedure call:

/ENTER-PROCEDURE $ORAC1120.INSTALL.P.AGENT,(EMDROOT='/u01/app/orac1120/product/emagent',EM-AGENT-PORT='1813',EM-OMS-HOST='',EM-OMS-HTTP-PORT='1159'), CPU-LIMIT=300


  • The installation is logged to the INSTALL.EMAGENT.LST file.

  • It is recommended to use a CPU-LIMIT greater than 200.

14.3 Running the Agent

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


Oracle recommends to use the start procedure in the BS2000 environment to start the Management Agent.

14.4 Restrictions

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

14.5 Troubleshooting

Typically, the Oracle Management Agent is monitored by an internal watchdog process and is 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, then use the following instructions to resolve the issue:


Login to the POSIX shell, set your environment and run the utility ithshow, for example:

$ . /u01/app/orac1120/agent11g/
$ ithshow

This utility produces an output similar to the following:

STARTED AT 2012-06-12-135624 BY POSIX (running) 
LLM = EMAGENT (prelinked)
PTHvers = 01.3A10 2011-04-14 09:19:23
FDs = 8 (8 ORIG FDs)
Threads = 10 (6 user threads, 4 system threads)
ORIG 1MYQ 3942 (X'0F66') 3 DIALOG *0 240 16.7989 32767 FSC
executing request
THRE 1MYW 3948 (X'0F6C') 3 DIALOG *0 240 21.7415 32767 FSC
executing user thread

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:


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, then you can terminate all other PTHREADS tasks by using the BS2000 system command


If the Management Agent is running on a SQ system in x86-64 mode, then you must define the proper load library in the procedure parameters as follows:


If the Management Agent terminates abnormally, then it might be possible that a process with the name dbluuser_number stays alive. This process is a program cache and cannot be canceled with the BS2000 CANCEL-JOB command. This process can only be stopped using the POSIX command posdbl. For example, the following shows you how you can identify and stop a pending program cache in the POSIX shell:

$ ps -fu emuser
EMUSER 2178 2175 0 07:48:08 pts/0 0:01 [sh]
EMUSER 4179 2178 2 14:05:16 pts/0 0:00 [ps]
EMUSER 4168 1 0 14:05:06 ? 0:00 dblu511

In this example, the process dblu511 with the pid 4168 is still alive. To stop this process enter the following command:

$ pdbl -uD