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 open Net Server v3.1 and open Net 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:
Create a file /var/opt/oracle/oratab with the following format:
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:
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 9 i database, you have to manually create a dbs directory in the ORACLE_HOME of your Oracle9 i 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.
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:
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:
Running the Agent
To run the agent, start a POSIX shell and type the following command:
To stop the agent, start a POSIX shell and type the following command:
To get the status of the agent, start a POSIX shell and type the following command:
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 9 i or Oracle Database 10 g .
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.
Oracle10 g 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 10 g 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:
This procedure produces an output similar to the following:
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, you can terminate all other PTHREADS tasks by using the BS2000 system command
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:
7 Installing Oracle Management Agent
This chapter describes how you can install Oracle Management Agent (Management Agent). In particular, this chapter covers the following:
Overview
Oracle Management Agent (Management Agent) is one of the core components of Enterprise Manager Cloud Control that enables you to convert an unmanaged host to a managed host in the Enterprise Manager system. The Management Agent works in conjunction with the plug-ins to monitor the targets running on that managed host.
Therefore, at any point in time, if you want to monitor a target running on a host, ensure that you first convert that unmanaged host to a managed host by installing a Management Agent, and then manually discover the targets running on it to start monitoring them.
To install a Management Agent, use the Add Host Targets Wizard that is accessible from within the Enterprise Manager Cloud Control console. Oracle recommends that you use this wizard for the mass-deployment of Management Agents.
Figure 7-1 describes a method to access the Add Host Targets Wizard.
Figure 7-1 Add Host Targets Wizard
The Add Host Targets Wizard is an application that offers GUI-rich, interactive screens. To access it, do one of the following:
From the Setup menu, select Add Target , then select Add Targets Manually . On the Add Targets Manually page, select Add Host Targets and click Add Host .
From the Setup menu, select Add Target , then select Auto Discovery Results . On the Auto Discovery Results page, select a host you want to monitor in Enterprise Manager Cloud Control, and click Promote .
The wizard enables you to do the following on multiple hosts across platforms with options to run preinstall and postinstall scripts:
Deploy a fresh Management Agent
Clone an existing well-tested and patched Management Agent
Install a Management Agent (called Shared Agent ) using an existing, centrally shared Management Agent (called Master Agent )
This chapter only describes how you can deploy a fresh Management Agent using the Add Host Targets Wizard. For information on cloning an existing instance and deploying a Management Agent using a shared instance, refer to Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide .
To monitor a target, you need to add the target to Enterprise Manager Cloud Control either using the Auto Discovery Results page, the Add Targets Manually page, or the discovery wizards offered for the targets you want to monitor.
For information about discovering targets in Enterprise Manager Cloud Control, refer to the chapter on adding targets in the Oracle Enterprise Manager Cloud Control Administrator’s Guide .
Once the installation is complete, you will see the following default contents in the agent base directory:
If you want to repoint your existing Management Agents to a new Oracle Management Service (OMS), then you must first deinstall those Management Agents and plug-ins, and then redeploy those Management Agents and plug-ins using the new OMS. This is typically done when you want to move from an Enterprise Manager Cloud Control system in a test environment to an Enterprise Manager Cloud Control system in a production environment.
When you repoint your existing Management Agents to a new OMS, you cannot move the targets monitored by the Management Agents, the target history, and the Management Agent history. The monitored targets and the history data is lost.
Before You Begin
Before you begin installing a Management Agent using the Add Host Targets Wizard, keep these points in mind:
The Add Host Targets Wizard converts an unmanaged host to a managed host in the Enterprise Manager system by installing a 12.1.0.2.0 Management Agent.
Oracle recommends you to use the Add Host Targets Wizard to mass-deploy Management Agents in your environment.
Oracle Management Agent 12 c communicates only with Oracle Management Service 12 c and not with any earlier release of Enterprise Manager.
A 12.1.0.1.0 Management Agent is compatible with a 12.1.0.2.0 OMS. However, using the Add Host Targets Wizard of a 12.1.0.2.0 OMS, you can install only the latest available Management Agent 12 c software. For example, if the 12.1.0.2.0 Management Agent software is available in Oracle Software Library, you cannot use the Add Host Targets Wizard of a 12.1.0.2.0 OMS to install a 12.1.0.1.0 Management Agent.
For information about the compatibility between 12 c releases of Management Agents and the OMS, see Table 1-1 present in the Introduction to Upgrade Approaches chapter in the Oracle Enterprise Manager Cloud Control Upgrade Guide.
If you have multiple hosts, sharing a common mounted drive, then install the Management Agents in two different phases:
In the Add Host Targets Wizard, select the deployment type Fresh Agent Install , and install a Management Agent on the host where the drive is shared. Alternatively, you can select the deployment type Clone Existing Agent , and clone the Management Agent to the host where the drive is shared.
For more information, refer to the chapter on cloning a Management Agent in the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide .
In the Add Host Targets Wizard, select the deployment type Add Host to Shared Agent , and install a Management Agent on all other hosts that access the shared, mounted drive. (Here, you will select the Management Agent you installed in the previous step as the master agent or shared agent.)
For more information, refer to the chapter on installing a Shared Agent in the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide .
If you have an Oracle RAC Cluster with multiple nodes, then you must install a Management Agent on each of the nodes separately. In other words, in the Add Host Targets Wizard, you must add each node explicitly as a destination host.
The Add Host Targets Wizard uses SSH to establish connectivity between Oracle Management Service (OMS) and the remote hosts where you want to install the Management Agents.
Only SSH1 (SSH version 1) and SSH2 (SSH version 2) protocols offered by OpenSSH are supported for deploying a Management Agent.
SSH public key authentication and password based authentication are supported. So you can use an existing SSH public key authentication without exposing your passwords. You can provide a dummy password in the wizard and bypass the validation.
To set up SSH public key authentication, follow these steps:
Navigate to the following location in the OMS home:
Run the following script on the OMS host as the OMS user, and pass the Management Agent install user name and the fully qualified name of the target hosts:
sshUserSetup.sh -setup -user -hosts
Access the Add Host Targets Wizard, and provide the dummy password and install the Management Agent.
The wizard ignores the dummy password, and honors the keys present in the following location on the OMS host to perform the installation. Here, $HOME refers to the home directory of the OMS install user.
If you want to provide additional keys, specify them as values for the oracle.sysman.prov.remoteinterfaces.identitylist property present in the $ /sysman/prov/agentpush/agentpush.properties file, using a comma separated list.
The Add Host Targets Wizard supports Named Credentials that enable you to use a set of credentials registered with a particular name specifically for this operation, by your administrator. This ensures an additional layer of security for your passwords because as an operator, you can only select the named credential, which is saved and stored by an administrator, and not know the actual user name and password associated with it.
In case the named credential you select does not have the privileges to perform the installation, then you can set the named credential to run as another user ( locked user account). In this case, the wizard logs in to the hosts using the named credential you select, but performs the installation using the locked user account you set.
For example, you can create a named credential titled User_A, and set it to run as User_X that has the required privileges. In this case, the wizard logs in to the hosts as User_A, but installs as User_X, using the privilege delegation setting (sudo or PowerBroker) specified in the named credential.
By default, the Add Host Targets Wizard configures only the following types of plug-ins:
All discovery plug-ins that were configured with the OMS from where the Management Agent software is being deployed.
Oracle Home discovery plug-in
Oracle Home monitoring plug-in
You must have read privileges on the Oracle WebLogic Server’s alert log directories for the Support Workbench (Incident) metrics to work properly. You must also ensure that the Management Agent that is monitoring this Oracle WebLogic Server target is running on the same host as the Oracle WebLogic Server.
If you have common mount point in your organization, then ensure that it is generic and ensure that you install the Management Agent in this generic mount points. This guideline helps when you upgrade your Management Agents to higher releases in the future within the same mount point, and not acquire new mount points each time.
For example, have a mount point such as /oracle/product/agent and install the Management Agent in there so that it appears as /oracle/product/agent/agent12c. Do not install the Management Agent directly in the mount point because it breaks the upgrade path and causes problems with cleanup operations.
Prerequisites
Table 7-1 lists the prerequisites you must meet before installing the Management Agent using the Add Host Targets Wizard.
Table 7-1 Prerequisites for Installing Oracle Management Agent
Requirement
Description
Ensure that you meet the hard disk space and physical memory requirements as described in Chapter 2.
(For Microsoft Windows) Ensure that you have installed Cygwin 1.7 on the destination host as described in Chapter 5.
Note: While running cygwin.bat in Microsoft Windows Server 2008 and Microsoft Windows Vista, ensure that you invoke it in administrator mode. To do this, right-click the cygwin.bat file and select Run as administrator.
Operating System Requirements
Ensure that you install the Management Agent only on certified operating systems as mentioned in the Enterprise Manager certification matrix available on My Oracle Support .
To access the Enterprise Manager certification matrix, follow the steps outlined in Appendix E.
For information about platforms receiving future support, refer to My Oracle Support note 793512.1.
Note: If you use Oracle Solaris 10, then ensure that you have update 9 or higher installed. To verify whether it is installed, run the following command:
You should see the output similar to the following. Here, s10s_u6 indicates that update 6, which is not a supported update level for installation, is installed.
Solaris 10 10/08 s10s_u6wos_07b SPARC
Ensure that you install all the operating system-specific packages as described in Chapter 3.
User and Operating System Group Requirement
Ensure that you create the required operating system groups and users as described in Chapter 4.
Destination Host Requirements
Ensure that the destination hosts are accessible from the host where the OMS is running.
If the destination host and the host on which OMS is running belong to different network domains, then ensure that you update the /etc/hosts file on the destination host to add a line with the IP address of that host, the fully qualified name of that host, and the short name of the host.
For example, if the fully-qualified host name is example.com and the short name is mypc , then add the following line in the /etc/hosts file:
172.16.0.0 example.com mypc
Destination Host Credential Requirements
Ensure that all the destination hosts running on the same operating system have the same set of credentials. For example, all the destination hosts running on Linux operating system must have the same set of credentials.
The wizard installs the Management Agent using the same user account. If you have hosts running on the same operating system but with different credentials, then have two different deployment sessions.
Ensure that the agent base directory you specify is empty and has write permission.
Ensure that the instance directory is empty and has write permission.
Destination Host Time Zone Requirements
Ensure that the time zones of the destination hosts have been set correctly. To verify the time zone of a destination host, log in to the OMS host, and run the following command:
ssh -l /bin/sh -c ‘echo $TZ’
If the time zone displayed is incorrect, log in to the destination host, and follow these steps:
Run the following commands to set the time zone on the destination host:
For Bourne shell or Bash shell:
For example, in the Bash shell, run the following command to set the time zone to America/New_York:
The time zones you can use are listed in /sysman/admin/supportedtzs.lst.
Restart the SSH daemon.
If the destination host runs on a UNIX based operating system, run the following command:
sudo /etc/init.d/sshd restart
If the destination host runs on a Microsoft Windows operating system, run the following commands:
cygrunsrv -E sshd
cygrunsrv -S sshd
Verify whether the SSH server can access the TZ environment variable by logging in to the OMS host, and running the following command:
ssh -l /bin/sh -c ‘echo $TZ’
Note: If you had ignored a prerequisite check warning about wrong time zone settings during the Management Agent install, you must set the correct time zone on the destination hosts after installing the Management Agents. For information on setting time zones post install, refer After You Install.
sudo/pbrun/sesu/su SSH Requirements
Ensure that you set the oracle.sysman.prov.agentpush.enablePty property to true in the $ /sysman/prov/agentpush/agentpush.properties file, if the privilege delegation tool you are using requires a pseudo terminal for remote command execution via SSH. Most privilege delegation tools such as pbrun, sesu, and su require a pseudo terminal for remote command execution, by default.
Note: If you are using sudo as your privilege delegation tool, and you do not want to set the oracle.sysman.prov.agentpush.enablePty property to true, do one of the following:
Include Defaults visiblepw in the /etc/sudoers file, or enter the sudo command with the -S option for Privileged Delegation Setting on the Installation Details page.
For information on how to access the Installation Details page, see Installation Procedure.
Comment out Defaults requiretty in the /etc/sudoers file.
sudo/pbrun/sesu/su Requirements (for Root User)
Ensure that the installing user has the privileges to invoke the id command and the agentdeployroot.sh script as root. Grant the privileges in the configuration file of your privilege delegation tool.
For example, if you are using sudo as your privilege delegation tool, include the following in the /etc/sudoers file to grant the required privileges:
Here, oracle is the installing user, and /home/oracle/agentibd is the agent base directory.
You do not require the following entry in the /etc/sudoers file for installing a Management Agent. However, the entry is required for performing provisioning and patching operations in Enterprise Manager. Therefore, if you are removing this entry before installing a Management Agent, then ensure that you bring back the entry after installing the Management Agent.
Ensure that the installing user has the privileges to invoke /bin/sh as the locked account user. Grant the privileges in the configuration file of your privilege delegation tool.
For example, if you are using sudo as your privilege delegation tool, include the following in the /etc/sudoers file to grant the required privileges:
login_user1 ALL=(oracle) /bin/sh
Here, login_user1 is the SSH log in user, and oracle is the locked account and install user.
If you do not want to grant privileges to the installing user to invoke /bin/sh as the locked account user, set the oracle.sysman.prov.agentpush.pdpShellOutEnabled property to false , and ensure that the installing user has the privileges to invoke id, chmod, cp, mkdir, rm, tar, emctl, agentDeploy.sh, runInstaller, and unzip as the locked account user. Grant the privileges in the configuration file of your privilege delegation tool.
For example, if you are using sudo as your privilege delegation tool, include the following in the /etc/sudoers file to grant the required privileges:
Here, login_user1 is the SSH log in user, oracle is the locked account and install user, and /home/oracle/agentibd is the agent base directory.
You do not require the following entry in the /etc/sudoers file for installing a Management Agent. However, the entry is required for performing provisioning and patching operations in Enterprise Manager. Therefore, if you are removing this entry before installing a Management Agent, then ensure that you bring back the entry after installing the Management Agent.
Locked Account Requirements
Ensure that the locked account user (oracle) has read permission on the home directory of the login user.
Default SSH Port Requirements
Ensure that the SSH daemon is running on the default port (that is, 22) on all the destination hosts. To verify the port, run the following command:
netstat -anp | grep
If the port is a non-default port, that is, any port other than 22, then update the SSH_PORT property in the following file that is present in the OMS home:
PATH Environment Variable Requirements
On the destination host, ensure the following:
(For Microsoft Windows) Ensure that the Cygwin software location appears before other software locations in the PATH environment variable. After making it the first entry, restart the SSH daemon (sshd).
( For UNIX ) On the destination host, ensure that the SCP binaries (for example, /usr/bin/scp) are in the PATH environment variable.
CLASSPATH Environment Variable Requirements
Unset the CLASSPATH environment variable. You can always reset the variable to the original value after the installation is complete.
Software Availability Requirements
Ensure that the software of the Management Agent you want to install is available in Oracle Software Library (Software Library).
If you want to install Oracle Management Agent 12 c on an operating system that is the same as the one on which Oracle Management Service 12 c is running, then the Management Agent software for that release and for that platform is available by default in the Software Library. Therefore, no action is required from your end.
If you want to install Oracle Management Agent 12 c on an operating system that is different from the one on which Oracle Management Service 12 c is running, then ensure that the Management Agent software for the intended platform is downloaded and stored in the Software Library using the Self Update console.
For information about how to download and apply software using the Self Update console, see the chapter on Self Update in the Oracle Enterprise Manager Cloud Control Administrator’s Guide .
Path Validation Requirements
Validate the path to all command locations as described in Appendix B.
Temporary Directory Space Requirements
Ensure that you allocate 400 MB of space for a temporary directory where the executables can be copied.
By default, the temporary directory location set to the environment variable TMP or TEMP is honored. If both are set, then TEMP is honored. If none of them are set, then the following default values are honored: /tmp on UNIX hosts and c:\Temp on Microsoft Windows hosts.
Agent Base Directory Requirements
Ensure that the agent base directory you provide is empty and has at least 1 GB of free space.
If a previously run deployment session had failed for some reason, then you might see an ADATMP_ subdirectory in the agent base directory. In this case, either delete the subdirectory and start a new deployment session, or retry the failed session from the Add Host Status page.
Ensure that the directory name does not contain any spaces.
Ensure that the installing user owns the agent base directory. Ensure that the installer user or the root user owns all the parent directories. Ensure that the root user owns the root directory.
For example, if the agent base directory is /scratch/OracleHomes/agent , and oracle is the installing user, then the /scratch/OracleHomes/agent directory must be owned by oracle , directories scratch and OracleHomes must be owned by either oracle or root user, and the root directory (/) must be owned by root user.
If the agent base directory is mounted, then ensure that it is mounted with the setuid turned on.
Central Inventory (oraInventory) Requirements
Ensure that you allocate 100 MB of space for the Central Inventory.
Ensure that the central inventory directory is not in a shared file system. If it is already in a shared file system, then create a new inventory in a non-shared file system. You can optionally migrate the products that were previously installed in the shared file system to this new inventory in the non-shared file system.
Ensure that you have read , write , and execute permissions on oraInventory on all remote hosts. If you do not have these permissions on the default inventory (typically at /etc/oraInst.loc ) on any remote host, then ensure that you specify the path to an alternative inventory location by using one of the following options in the Additional Parameters field of the Add Host Targets Wizard. However, note that these parameters are supported only on UNIX platforms, and not on Microsoft Windows platforms.
Installing User Requirements
If the central inventory owner and the user installing the Management Agent are different, then ensure that they are part of the same group.
Also ensure that the inventory owner and the group to which the owner belongs have read and write permissions on the inventory directory.
For example, if the inventory owner is abc and the user installing the Management Agent is xyz , then ensure that abc and xyz belong to the same group, and they have read and write access to the inventory.
Agent User Account Permissions and Rights (For Microsoft Windows)
( For Microsoft Windows ) If you are installing the Management Agent on a Microsoft Windows-based operating system, then ensure that the agent user account has permissions and rights to perform the following:
Act as part of the operating system.
Adjust memory quotas for a process.
Replace process level token.
Log in as a batch job.
To verify whether the agent user has these rights, follow these steps:
Launch the Local Security Policy.
From the Start menu, click Settings and then select Control Panel . From the Control Panel window, select Administrative Tools , and from the Administrative Tools window, select Local Security Policy .
In the Local Security Policy window, from the tree structure, expand Local Policies , and then expand User Rights Assignment .
Permissions for cmd.exe (For Microsoft Windows)
( For Microsoft Windows ) If you are installing the Management Agent on a Microsoft Windows-based operating system, then ensure that you grant the cmd.exe program Read and Execute permissions for the user account that the batch job runs under. This is a restriction from Microsoft.
For more information on this restriction and to understand how you can grant these permissions, access the following URL to Microsoft Web site:
Ensure that the preinstallation and postinstallation scripts that you want to run along with the installation are available either on the OMS host, destination hosts, or on a shared location accessible to the destination hosts.
Ensure that you use a certified browser as mentioned in the Enterprise Manager certification matrix available on My Oracle Support .
To access the Enterprise Manager certification matrix, follow the steps in Appendix E.
If you use Microsoft Internet Explorer 8 or 9, do the following:
Turn off the compatibility view mode. To do so, in Microsoft Internet Explorer, from the Tools menu, click Compatibility View to disable it if it is enabled. Also, click Compatibility View Settings and deregister the Enterprise Manager Cloud Control console URL.
Enable XMLHTTP. To do so, from the Tools menu, click Internet Options . Click the Advanced tab, and under the Security heading, select Enable native XMLHTTP support to enable it.
Installation Procedure
To install a fresh Management Agent using the Add Host Targets Wizard, follow these steps:
In Cloud Control, do one of the following:
From the Setup menu, select Add Target , then select Auto Discovery Results . On the Auto Discovery Results page, select a host you want to monitor in Enterprise Manager Cloud Control, and click Promote .
From the Setup menu, select Add Target , then select Add Targets Manually . On the Add Targets Manually page, select Add Host Targets and click Add Host .
On the Host and Platform page, do the following:
Accept the default name assigned for this session or enter a unique name of your choice. The custom name you enter can be any intuitive name, and need not necessarily be in the same format as the default name. For example, add_host_operation_1 .
A unique deployment activity name enables you to save the installation details specified in this deployment session and reuse them in the future without having to enter all the details all over again in the new session.
Click Add to enter the fully qualified name and select the platform of the host on which you want to install the Management Agent.
Oracle recommends you to enter the fully qualified domain name of the host. For monitoring purpose, Enterprise Manager Cloud Control adds that host and the Management Agent with the exact name you enter here.
You must enter only one host name per row. Entering multiple host names separated by a comma is not supported.
You must ensure that the host name does not contain underscores(«_»).
If the platform name is appended with Agent Software Unavailable , then it indicates that the software for that platform is not available on the OMS host, and that you must download and apply it using the Self Update console. To access the Self Update console, from the Setup menu, select Extensibility , then click Self Update .
For more information on using the Self Update Console to download and apply the latest software, refer to Oracle Enterprise Manager Cloud Control Administrator’s Guide.
Alternatively, you can click either Load from File to add host names stored in a file, or Add Discovered Hosts to add host names from a list of hosts discovered by Enterprise Manager. For information on how the host name entries must appear in the host file, see Format of Host List File.
When you click Add Discovered Hosts and add hosts from a list of discovered hosts, the host’s platform is automatically detected and displayed. The platform name is detected using a combination of factors, including hints received from automated discovery and the platform of the OMS host. This default platform name is a suggestion, so Oracle strongly recommends you to verify the platform details before proceeding to the next step.
If you are correcting the platform names, and if all the hosts run on the same platform, then set the platform for the first host in the table and from the Platform list, select Same for All Hosts . This will ensure that the platform name you selected for the first host is also set for the rest of the hosts in the table.
If you reach this page (Host and Platform page) from the Auto Discovery Results page, then the hosts you selected on that page automatically appear in the table. In this case, you need to only validate the host names and their platforms.
If you are installing a Management Agent on a platform that is different from the platform on which the OMS is running, then ensure that you have the software for that platform. If you do not have that software, then go to the Self Update console within Enterprise Manager Cloud Control, download the software, then apply it. For more information, see the prerequisite about Software Availability in Table 7-1.
On the Installation Details page, do the following:
In the Deployment Type section, select Fresh Agent Install .
If you have multiple hosts sharing a common mounted drive, then install the Management Agents in two different phases:
In the Add Host Targets Wizard, select the deployment type Fresh Agent Install , and install a Management Agent on the host where the drive is shared.
In the Add Host Targets Wizard, select the deployment type Add Host to Shared Agent , and install a Management Agent on all other hosts that access the shared, mounted drive. (Here, you will select the Management Agent you installed in the previous step as the master agent or shared agent.)
From the table, select the first row that indicates the hosts grouped by their common platform name.
In the Installation Details section, provide the installation details common to the hosts selected in Step 3 (b). For Installation Base Directory , enter the absolute path to the agent base directory where you want the software binaries, security files, and inventory files of the Management Agent to be copied.
For example, /u01/app/Oracle/
If the path you enter does not exist, the application creates a directory at the specified path, and copies the Management Agent software binaries, security files, and inventory files there.
The Installation Base Directory is essentially the agent base directory. Ensure that the directory you provide is empty. If a previously run deployment session had failed for some reason, then you might see an ADATMP_ subdirectory in the agent base directory. In this case, either delete the subdirectory and start a new deployment session, or retry the failed session from the Add Host Status page.
For Instance Directory , accept the default instance directory location or enter the absolute path to a directory of your choice where all Management Agent-related configuration files can be stored.
For example, /u01/app/Oracle/agent_inst
If you are entering a custom location, then ensure that the directory has write permission. Oracle recommends you to maintain the instance directory inside the agent base directory.
If the path you enter does not exist, the application creates a directory at the specified path, and stores all the Management Agent-related configuration files there.
From Named Credential list, select an appropriate profile whose credentials can be used for setting up the SSH connectivity between the OMS and the remote hosts, and for installing a Management Agent on each of the remote hosts.
If you do not have a credential profile, or if you have one but do not see it in the Named Credential list, then click the plus icon against this list. In the Create New Named Credential window, enter the credentials and store them with an appropriate profile name so that it can be selected and used for installing the Management Agents. Also set the run privilege if you want to switch over from the Named Credential you are creating, to another user who has the privileges to perform the installation.
If the plus icon is disabled against this list, then you do not have the privileges to create a profile with credentials. In this case, contact your administrator and either request him/her to grant you the privileges to create a new profile or request him/her to create a profile and grant you the access to view it in the Named Credential list.
If you have manually set up SSH public key authentication between the OMS and the remote hosts, then you may not have a password for your user account. In this case, create a named credential with a dummy password. Do NOT leave the password field blank.
For Privileged Delegation Setting , validate the Privilege Delegation setting to be used for running the root scripts. By default, it is set to the Privilege Delegation setting configured in Enterprise Manager Cloud Control.
For example, you can specify one of the following for the Privileged Delegation Setting field:
If you leave the Privileged Delegation Setting field blank, the root scripts will not be run by the wizard; you will have to run them manually after the installation. For information about running them manually, see After You Install.
This setting will also be used for performing the installation as the user set in the Run As attribute of the selected Named Credential if you had set the user while creating that Named Credential.
In the Privilege Delegation setting, the %RUNAS% is honored as the root user for running the root scripts and as the user set in the Run As attribute of the Named Credential for performing the installation.
For Port , accept the default port (3872) that is assigned for the Management Agent to communicate, or enter a port of your choice.
The custom port you enter must not be busy. If you are not sure, you can leave this field blank. Enterprise Manager Cloud Control automatically assigns the first available free port within the range of 1830 — 1849.
(Optional) In the Optional Details section, enter the absolute path to an accessible location where the preinstallation and postinstallation scripts you want to run are available. Note that only shell scripts are supported, and only one preinstallation or one postinstallation script can be specified.
If you want to run the script as root , then select Run as Root . If the script is on the host where OMS is running and is not on the host where you want to install the Management Agent, then select Script on OMS . In this case, the script will be copied from the OMS host to the destination hosts, and then run on the destination hosts.
(Optional) For Additional Parameters , enter a whitespace-separate list of additional parameters that you want to pass during the installation. For a complete list of supported additional parameters, see Table 7-2.
For example, if you want to provide the inventory pointer location file, then enter -invPtrLoc followed by the absolute path to the file location. However, note that this parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.
Repeat Step 3 (b) to Step 3 (i) for every other row you have in the table.
On the Review page, review the details you have provided for the installation and do one of the following:
If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes.
If you want to cancel the deployment session for some reason, click Cancel. You are automatically taken to the Add Targets Manually page.
If you are satisfied with the details, then click Deploy Agent to install the Management Agent. You are automatically taken to the Add Host Status page that enables you to monitor the progress of the deployment session.
If you want to cancel a running deployment session, then on the Add Host Targets page, click Cancel. Note that once you cancel the session, you cannot track or resume the session in any way. However, the currently launched commands on the remote hosts will continue to run until they are completed.
If the installation fails for any reason, review the log files. For information on how to access the log files, refer to Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
One log file is generated per host, so if you installed Management Agents on multiple hosts, then review all the log files.
Format of Host List File
In the Add Host Targets Wizard, you can click Load from File to add the hosts listed in a file. However, ensure that the file you select has one of the following formats:
Only the host name.
The host name followed by the platform name.
The supported platform names are linux_x64, linux, solaris, hpunix, hpi, linux64_zseries, aix, linux_ppc64, windows_x64, solaris_x64, win32.
Supported Additional Parameters
Table 7-2 lists the additional parameters supported for installing a new Management Agent using the Add Host Targets Wizard.
Table 7-2 Supported Additional Parameters
Parameter
Description
Enter the absolute path to the Central Inventory (oraInventory).
For example, INVENTORY_LOCATION=$HOME/oraInventory
Note: This parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.
This parameter will be used only when the Central Inventory pointer /etc/oraInst.loc (or /var/opt/oracle/oraInst.loc ) does not exist.
Enter the absolute path to the inventory file that has the location of the Central Inventory (oraInventory).
For example, -invPtrLoc /tmp/oraInst.loc
Note: This parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.
(Only for Microsoft Windows) Enter a custom name for the Management Agent service.
Every Management Agent appears as a service in Microsoft Windows, and every Management Agent has a default service name. If you want to assign a custom name to identify it, then use this parameter.
For example, s_agentSrvcName=agentsrvc1
Note: If you upgrade a 12 c Release 1 (12.1.0.1) Management Agent installed on a Microsoft Windows host to 12 c Release 2 (12.1.0.2), and you want to install another Management Agent on the same host, reporting to a different OMS, ensure that you specify the s_agentSrvcName parameter.
Specify this parameter if you do not want the Management Agent to start automatically once it is installed and configured.
If you do not specify this parameter, the Management Agent starts automatically once it is installed and configured.
Specify this parameter if you do not want the Management Agent to be secured after the install.
If you specify this parameter, ensure that you also specify the OMS HTTP port, using the EM_UPLOAD_PORT parameter.
For example, b_secureAgent=false EM_UPLOAD_PORT=4899
If you do not specify this parameter, the Management Agent is secured automatically after the install.
After You Install
After you install a Management Agent using the Add Host Targets Wizard, follow these steps:
Verify the installation on the Add Host Status page. Review the progress made on each of the phases of the deployment operation — Initialization , Remote Prerequisite Check , and Agent Deployment .
In the Add Host Targets Wizard, after you click Deploy Agent to install one or more Management Agents, you are automatically taken to the Add Host Status page.
If you want to view the details or track the progress of all the deployment sessions, then from the Setup menu, select Add Target , and then, click Add Targets Manually . On the Add Targets Manually page, select Add Host Targets and click Add Host Results .
If a particular phase fails or ends up with a warning, then review the details provided for each phase in the Agent Deployment Details section, and do one of the following:
Ignore the warning or failure, and continue with the session if you prefer.
You can choose to proceed with the deployment of Management Agents only on those remote hosts that have successfully cleared the checks, and you can ignore the ones that have Warning or Failed status. To do so, click Continue and select Continue, Ignoring Failed Hosts.
You can choose to proceed with the deployment of Management Agents on all the hosts, including the ones that have Warning or Failed status. To do so, click Continue and select Continue, All Hosts .
Fix the problem by reviewing the error description carefully, understanding its cause, and taking action as recommended by Oracle.
You can choose to retry the deployment of Management Agents with the same installation details. To do so, click Retry and select Retry Using Same Inputs.
You can retry the deployment of Management Agents with modified installation details. To do so, click Retry and select Update Inputs and Retry.
If you want to cancel a running deployment session, then click Cancel. Note that once you cancel the session, you cannot track or resume the session in any way. However, the currently launched commands on the remote hosts will continue to run until they are completed.
If required, manually verify the installation:
Navigate to the Management Agent home and run the following command to see a message that confirms that the Management Agent is up and running:
If the status of the Management Agent is down for some reason, then manually start the Management Agent:
Navigate to the Management Agent home and run the following command to see a message that confirms that EMD upload completed successfully:
Verify if all the plug-ins were installed successfully. To do so, access the following log file from the Management Agent home, and search for the sentence WARN:Plugin configuration has failed .
If you find the sentence, resolve the issue by running the AgentPluginDeploy.pl script from the Management Agent home.
If you have restrictive Privilege Delegation Provider (PDP) configuration settings, enter the location of nmosudo in your PDP configuration file.
Enterprise Manager supports PDPs such as SUDO and PowerBroker that enable administrators to restrict certain users from running certain commands.
Therefore, when you install an Enterprise Manager Cloud Control 12 c Release 2 (12.1.0.2) Management Agent, you must modify your PDP configuration file to update the new location of nmosudo.
For example, if you use SUDO as your PDP, the configuration file for SUDO is typically /etc/sudoers. In this file, update the following entry with the new location to nmosudo.
(Only for UNIX Operating Systems) If you had ignored the prerequisite check warning about not having root privileges, SUDO/PBRUN binaries, or SUDO/PBRUN privileges, then manually run the following scripts as a root user from each of the hosts where the installation was done. If you do not have SUDO/PBRUN privileges, then request your Administrator who has the privileges to run these scripts.
If this is the first Oracle product you just installed on the host, then run the oraInstroot.sh script from the inventory location specified in the oraInst.loc file that is available in the Management Agent home.
For example, if the inventory location specified in the oraInst.loc file is $HOME/oraInventory , then run the following command:
If you are not a root user, then use SUDO/PBRUN to change to a root user. For example, run the following command:
Run the root.sh script from the Management Agent home:
If you are not a root user, then use SUDO/PBRUN to change to a root user. For example, run the following command:
If you had ignored a prerequisite check warning about wrong time zone settings, follow these steps:
Set the correct time zone on the destination host.
For information on how to set the time zone on a destination host, refer Destination Host Time Zone Requirements in Table 7-1.
Deinstall the Management Agent present on the destination host.
Install a Management Agent on the destination host.
By default, the host and the Management Agent get automatically added to the Enterprise Manager Cloud Control console for monitoring. None of the targets running on that host get automatically discovered and monitored.
To monitor the other targets, you need to add them to Enterprise Manager Cloud Control either using the Auto Discovery Results page, the Add Targets Manually page, or the discovery wizards offered for the targets you want to monitor.
For information about discovering targets in Enterprise Manager Cloud Control, refer to Oracle Enterprise Manager Cloud Control Administrator’s Guide .
If you want to repoint your existing Management Agents to a new Oracle Management Service (OMS), then you must first deinstall those Management Agents and plug-ins, and then redeploy those Management Agents and plug-ins using the new OMS. This is typically done when you want to move from an Enterprise Manager Cloud Control system in a test environment to an Enterprise Manager Cloud Control system in a production environment.
When you repoint your existing Management Agents to a new OMS, you cannot move the targets monitored by the Management Agents, the target history, and the Management Agent history. The monitored targets and the history data is lost.
