|Oracle9i Installation and Database Administration Guide
Release 2 (18.104.22.168.10) for Fujitsu Siemens Computers BS2000/OSD
Part Number B12034-01
This chapter describes the Oracle Intelligent Agent for BS2000/OSD and provides configuration information. The reader is supposed to be familiar with Oracle Enterprise Manager (see Oracle9i Intelligent Agent User's Guide and Oracle9i Enterprise Manager, a set of documentation books).
The Oracle Intelligent Agent for BS2000/OSD is a component of the Oracle9i product set for BS2000/OSD. It runs jobs sent by the Oracle Enterprise Manager, handles events, can start up and shut down a database. Additionally, it can function regardless of the status of the network connection, and it can run even if the database is down.
The agent's primary function is to monitor an Oracle server or servers. However, an Oracle server is not required to run Oracle Intelligent Agent for BS2000/OSD.
A prerequisite for running the Oracle Intelligent Agent for BS2000/OSD is the BS2000/OSD POSIX subsystem.
If you want to use Oracle Intelligent Agent for BS2000/OSD the POSIX part of Oracle for BS2000/OSD has to be installed (see Chapter 3).
After the POSIX part of Oracle for BS2000/OSD is installed, you choose a userid where Oracle Intelligent Agent for BS2000/OSD should run.
The address space of this userid must be at least 256 MB.
This userid and all userid's where you want to run agent jobs needs to be fit for POSIX (/START-POSIX-SHELL should be possible) and in POSIX all of this userid's and the Oracle Installation userid must belong to the same POSIX group (/etc/group).
Then you can install the agents environment by:
The script prompts you for a SID (default: ADM) as a qualifier for the agents ORAENV file to be generated and a JOBCLASS (default: JCBATCH) which should be written to the ORAENV variable BGJPAR, which is used to run agent jobs if no special user_BGJPAR is defined.
The script also generates a POSIX file .profile.oracle that can be used to set all environment variables necessary for running the Intelligent Agent. You must ensure that the specified environment variables are set before you run the Intelligent Agent. To achieve this the follwing line is inserted in your POSIX .profile
After you have installed the POSIX part of Oracle for BS2000/OSD, you must configure Oracle Intelligent Agent for BS2000/OSD to access the databases you wish to manage. You do this by updating several parameter files influencing Net Services (see below). The contents of all of these files are documented in the Oracle9i Net Services Book Set.
The agent reads the parameter files as it starts up and in this way manages the specified databases. If you make any changes to the contents of these files, the agent will need to be stopped and restarted before the changes will take effect.
The location of the ORATAB file is determined through the shell variable ORATAB which is set in .profile.oracle (default: $ORACLE_HOME/network/admin/oratab). For every instance you want to manage you add a line to the ORATAB file. The syntax for this entry is:
Best practice is to have one LISTENER.ORA file with all listeners described and one TNSNAMES.ORA file with all service names described and to have these files located in $ORACLE_HOME/network/admin.
Please note the following:
Do not modify the TCL scripts (job and event scripts written in Tool Command Language) that come with the agent. If you want to submit a job different than the ones that are predefined with the agent, then use the TCL job where you are allowed to pass in arbitrary scripts and have the agent run them.
For every userid you want to run a job through the agent you have to add a line which determines the account of that userid because Oracle Enterprise Manager can only support userid and password as job credentials. The syntax is:
For every instance you want to manage you have to add a line to the ORAENV file describing the BS2000 userid where instances should run. As the agent tries to start a job under this userid to find out if the instance is up or down, you have to add lines for the job credentials of that userid.
Userids which are used as prefix for filenames like ORAUID have to be qualified with /BS2/, if they occur in an ORAENV file and are accessed from the POSIX subsystem. Since the start up of a Database invoked through the agent is performed in POSIX and the agent uses the ORAENV file with the sid of that database this is also true for these ORAENV files.
Every Instance you want to be managed from Oracle Intelligent Agent for BS2000/OSD must be configured for remote administration. Don't forget to qualify userids which are used as prefix for filenames like ORAUID with /BS2/ in the ORAENV file.
If you want to use events like oracle/rdbms/fault/alert with access to the alertfile of an instance you have to ensure that the alertfile of that instance is located in POSIX in the $ORACLE_HOME/bdump directory. You achieve this by adding the follwing line in the instance sid.p.oraenv file:
After the configuration files have been prepared, test the Agent. Be sure, the statements from .profile.oracle have already been executed. Then, test connectivity with the TNSPING command. Only when TNSPING is successful, you should attempt to use the Oracle Intelligent Agent for BS2000/OSD.
Use the Oracle Intelligent Agent for BS2000/OSD as described in Oracle9i Enterprise Manager Book Set.
Oracle Intelligent Agent for BS2000/OSD can monitor only servers that are running Oracle9i Release 2.
The collection of data about the host e.g. CPU or disk utilization or events related to them is not supported.
The Oracle Intelligent 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 Intelligent Agent for BS2000/OSD is not useable with third party SNMP management systems.