Skip Headers
Oracle® Enterprise Manager Cloud Control Basic Installation Guide
12c Release 1 (12.1.0.1)
Part Number E22624-12
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
PDF · Mobi · ePub

8 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 you to this wizard particularly for mass-deployment of Management Agents.

Figure 8-1 Add Host Targets Wizard

Add Host Targets Wizard

The Add Host Targets Wizard is an application that offers GUI-rich, interactive screens. The wizard enables you to do the following on multiple hosts across platforms with options to run preinstall and postinstall scripts:

Note:

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 the 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:

<agent_base_directory>
    |_____core
         |_____12.1.0.1.0
    |_____plugins
    |_____agent_inst
    |_____sbin
    |_____plugins.txt
    |_____plugins.txt.status
    |_____agentimage.properties

Note:

If you want to move your Management Agents from one Enterprise Manager Cloud Control to another, then you must first deinstall those Management Agents and plug-ins, and then redeploy those Management Agents and plug-ins using the new Enterprise Manager Cloud Control. This is typically done when you want to move from an Enterprise Manager Cloud Control in a test environment to an Enterprise Manager Cloud Control in a production environment.

Before You Begin

Before you begin installing an Oracle Management Agent, keep these points in mind:

Prerequisites

Table 8-1 lists the prerequisites you must meet before installing the Management Agent.

Table 8-1 Prerequisites for Installing Oracle Management Agent

Requirement Description

Hardware Requirements

Ensure that you meet the hard disk space and physical memory requirements as described in Chapter 2.

Software Requirements

(For Microsoft Windows) Ensure that you have installed Cygwin on the destination host as described in Chapter 5.

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 this matrix, follow these steps:

  1. Log in to My Oracle Support, and click the Certifications tab.

  2. On the Certifications page, in the Certification Search region, from the Product list, select Enterprise Manager Base Platform - OMS.

  3. From the Release list, select 12.1.0.1.0, and click Search.

    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:

    cat /etc/release

    You should see the output similar to the following. Here, s10s_u6 indicates that update 6 is already installed.

    Solaris 10 10/08 s10s_u6wos_07b SPARC

Package Requirements

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.

Permission Requirements

  • 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 <install_user> <destination_host_name> /bin/sh -c 'echo $TZ'

If the time zone displayed is incorrect, log in to the destination host, and follow these steps:

  1. Run the following commands to set the time zone on the destination host:

    • For Korn shell:

      TZ=<value>

      export TZ

    • For Bourne shell or Bash shell:

      export TZ=<value>

    • For C shell:

      setenv TZ <value>

    For example, in the Bash shell, run the following command to set the time zone to America/New_York:

    export TZ='America/New_York'

    The time zones you can use are listed in <AGENT_HOME>/sysman/admin/supportedtzs.lst.

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

  3. 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 <install_user> <destination_host_name> /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 Requirements

(Only for UNIX)

  • Ensure that the installing user has SUDO/PBRUN privileges to invoke /bin/sh as root.

  • Ensure that you have the following line in the /etc/sudoers file. This is required to allow remote command execution using sudo.

    Defaults visiblepw

  • Ensure that you comment out the following line in the /etc/sudoers file:

    Defaults requiretty

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

    (root)/oracle/product/oms12c/agent/agent_inst/bin/nmosudo

Locked Account Requirements

Ensure that the locked account user (oracle) has read permission on the home directory of the login user.

Ping Requirements

If a firewall configured in your environment does not allow any ping traffic, then ensure that you do the following:

  1. Take a backup of the following file from the OMS home:

    For Linux Platforms:

    $<OMS_HOME>/oui/prov/resources/sPaths.properties

    For Other Platforms:

    $<OMS_HOME>/oui/prov/resources/ssPaths_<platform>.properties

    For example, ssPaths_aix.properties if the OMS is on AIX platform.

  2. Edit the original properties file and change PING_PATH=/bin/ping to PING_PATH=/bin/true.

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 <port_no>

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:

$<OMS_HOME>/oui/prov/resources/Paths.properties

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) on both the hosts.

  • (For UNIX) On the destination host, ensure that the SCP binaries (for example, /usr/local/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 12c on an operating system that is the same as the one on which Oracle Management Service 12c 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 12c on an operating system that is different from the one on which Oracle Management Service 12c 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 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.

IPV 6 Requirements

If you are installing from an ipv6 OMS to a non-ipv6 host, then follow these step:

  1. Navigate to the following location on the OMS home:

    $<OMS_HOME>/oui/prov/resources/

  2. Check the property value of PING_PATH in the following files in this order:

    1. ssPaths_<plat>.properties

    2. sPaths.properties

    3. Paths.properties

  3. Change the property value of PING_PATH from /bin/ping to /bin/ping6

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.

    If a previously run deployment session had failed for some reason, then you might see an ADATMP_<timestamp> 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.

Read and Execute Permission Requirements

Ensure that you (in fact, all users accessing the agent base directory) have read and execute permission on all the directories that lead up to the agent base directory.

For example, if the agent base directory is /home/john/oracle/software/agent/, then you must have read and execute permissions on all the directories, mainly home, john, oracle, software, and agent.

Central Inventory (oraInventory) Requirements

  • Ensure that you allocate 100 MB of space for the Central Inventory.

  • Ensure that the Oracle Inventory (oraInventory) is not in a shared location. When you use the /etc/oraInst.loc file, ensure that the inventory location specified there is not pointing to a shared location. If it is, change it to a non-shared location by following the instructions outlined in My Oracle Support note 1092645.1.

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

    INVENTORY_LOCATION=<absolute_path_to_inventory_directory>

    -invPtrLoc <absolute_path_to_oraInst.loc>

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.

  • Increase quotas.

  • Replace process level token.

  • Log in as a batch job.

To verify whether the agent user has these rights, follow these steps:

  1. Launch the Local Security Settings.

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

  2. In the Local Security Settings 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:

http://support.microsoft.com/kb/867466/en-us

Preinstallation/Postinstallation Scripts Requirements

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.

Browser Requirements

  • Ensure that you use a certified browser as mentioned in the Enterprise Manager Certification Matrix available on My Oracle Support.

    To access this matrix, follow these steps:

    1. Log in to My Oracle Support, and click the Certifications tab.

    2. On the Certifications page, in the Certification Search region, from the Product list, select Enterprise Manager Base Platform - OMS.

    3. From the Release list, select 12.1.0.1.0, and click Search.

  • 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, follow these steps:

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

  2. On the Host and Platform page, do the following:

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

      Session Name

      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.

    2. Click Add to enter the fully qualified name and select the platform of the host on which you want to install the Management Agent.

      Add button to add hosts

      Note:

      • 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 it using the Self Update console. To do so, from the Setup menu, select Extensibility, and then, click Self Update.

      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.

      Load from File and Add from Discovered Hosts Options

      Note:

      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.

      Platform Information

      Note:

      • 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, and download the software. For more information, see the prerequisite about Software Availability in Table 8-1.

    3. Click Next.

  3. On the Installation Details page, do the following:

    1. In the Deployment Type section, select Fresh Agent Install.

      Install Type

      Note:

      If you have multiple hosts sharing a common mounted drive, then install the Management Agents in two different phases:

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

      2. 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.)

    2. From the table, select the first row that indicates the hosts grouped by their common platform name.

    3. 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 Management Agent to be copied.

      For example, /u01/app/Oracle/.

      Note:

      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_<timestamp> 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.

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

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

      Named Credentials

      Note:

      • 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 the SSH connectivity 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.

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

      If you leave this 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.

      Note:

      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.

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

    8. (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.

    9. (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 8-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.

    10. Repeat Step 3 (b) to Step 3 (i) for every other row you have in the table.

    11. Click Next.

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

Note:

  • If the installation fails for any reason, review the log files available in the following location of the OMS home.

    $<OMS_HOME>/sysman/prov/agentpush

    One log file is generated per host, so if you installed on multiple hosts, then review all the log files.

  • Despite a successful installation, if you see some exceptions in the prerequisite error file, you can ignore the exception trace. This issue might happen when an operation attempts to retrieve an element from a collection using a key that does not exist in that collection. You can ignore this exception.

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.

    For Example,

    host1.example.com

    host2.example.com

  • The host name followed by the platform name.

    For Example,

    host1.example.com linux

    host2.example.com aix

    The supported platform names are linux_x64, linux, solaris, hpunix, hpi, linux_zseries64, aix, linux_ppc64, windows_x64, solaris_x64, win32.

Supported Additional Parameters

Table 8-2 lists the additional parameters supported for installing a new Management Agent.

Table 8-2 Supported Additional Parameters

Parameter Description

INVENTORY_LOCATION

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.

-invPtrLoc

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.

s_agentServiceName

(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, DBAgent

After You Install

After you install the Management Agent, follow these steps:

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

    Note:

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

    Note:

    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.

  2. If required, manually verify the installation:

    1. 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:

      $<AGENT_HOME>/bin/emctl status agent

      Note:

      If the status of the Management Agent is down for some reason, then manually start the Management Agent:

      $<AGENT_HOME>/bin/emctl start agent

    2. Navigate to the Management Agent home and run the following command to see a message that confirms that EMD upload completed successfully:

      $<AGENT_HOME>/bin/emctl upload agent

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

    $<AGENT_HOME>/cfgtoollogs/cfgfw/CfmLogger-<timestamp>.log

    For example,

    $<MIDDLEWARE_HOME>/agent/core/12.1.0.1.0/cfgtoollogs/cfgfw/CfmLogger-<timestamp>.log

    If you find the sentence, resolve the issue by running the AgentPluginDeploy.pl script from the Management Agent home.

    $<MIDDLEWARE_HOME>/agent/core/12.1.0.1.0/perl/bin/perl <MIDDLEWARE_HOME>/agent/core/12.1.0.1.0/bin/AgentPluginDeploy.pl -oracleHome <MIDDLEWARE_HOME>/agent/core/12.1.0.1.0 -agentDir <AGENT_BASE_DIR> -pluginIdsInfoFile <AGENT_BASE_DIR>/plugins.txt -action configure -emStateDir <AGENT_INSTANCE_HOME>

    For example,

    /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/perl/bin/perl /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/bin/AgentPluginDeploy.pl -oracleHome /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/ -agentDir /u01/app/Oracle/Middleware/agent -pluginIdsInfoFile /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/sysman/install/plugins.txt -action configure -emStateDir /u01/app/Oracle/Middleware/agent/agent_inst

  4. (Only for UNIX Operating Systems) If you had ignored a 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:

      $HOME/oraInventory/oraInstRoot.sh

      Note:

      If you are not a root user, then use SUDO/PBRUN to change to a root user. For example, run the following command:

      /usr/local/bin/sudo $HOME/oraInventory/oraInstRoot.sh

    • Run the root.sh script from the Management Agent home:

      $<AGENT_HOME>/root.sh

      Note:

      If you are not a root user, then use SUDO/PBRUN to change to a root user. For example, run the following command:

      /usr/local/bin/sudo $<AGENT_HOME>/root.sh

  5. If you had ignored a prerequisite check warning about wrong time zone settings, follow these steps:

    1. 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 8-1.

    2. Deinstall the Management Agent present on the destination host.

      For information on how to deinstall a Management Agent, refer Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

    3. Install a Management Agent on the destination host.

  6. 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 the chapter on adding targets in the Oracle Enterprise Manager Cloud Control Administrator's Guide.

Note:

If you want to move your Management Agents from one Enterprise Manager Cloud Control to another, then you must first deinstall those Management Agents and plug-ins, and then redeploy those Management Agents and plug-ins using the new Enterprise Manager Cloud Control. This is typically done when you want to move from an Enterprise Manager Cloud Control in a test environment to an Enterprise Manager Cloud Control in a production environment.
Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us