| Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide 12c Release 2 (12.1.0.2) Part Number E24089-16 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide 12c Release 2 (12.1.0.2) Part Number E24089-16 |
|
|
PDF · Mobi · ePub |
This chapter describes how you can install a Shared Agent with the help of a central, shared Oracle home location of an existing Oracle Management Agent (Management Agent) that is installed on an NFS-mounted drive.
If you want to install additional Management Agents on hosts that share a mounted drive where a Management Agent is already installed, then the best option is to use the software binaries of the shared Oracle home from the mounted drive and configure the remote hosts to be managed by that Management Agent, thus capitalizing on the NFS visibility and saving hard disk space on the remote hosts.
The Management Agent that shares its software binaries, in this context, is called the Master Agent, and the one that is configured with an instance directory on the remote host is called the Shared Agents or NFS Agents.
You can install a Shared Agent in graphical or silent mode. In graphical mode, you use the Add Host Targets Wizard that is accessible from within the Enterprise Manager Cloud Control console. In silent mode, you use the AgentNFS.pl script.
The wizard and the script use the software binaries from the shared Oracle home and configure an instance directory on each of the destination hosts for storing configuration files such as emd.properties, targets.xml, log files, and so on.
Note:
Installing a Shared Agent on a host running on Microsoft Windows is not supported.
Unlike the Add Host Target Wizard, the AgentNFS.pl script must be run only from a destination host, and at a given time, only one Management Agent can be installed at a given time. Therefore, if you want to install only a few Management Agents, then use the AgentNFS.pl script.
Before you begin, keep these points in mind:
When you install a Shared Agent, you only configure an instance directory on the destination host to store configuration files; you do not actually install a Management Agent.
The Shared Agent can communicate only with Oracle Management Service 12c and not with any earlier release of Enterprise Manager.
Only the destination host and the Shared Agent installed on it get automatically discovered and monitored in the Enterprise Manager system. The targets running on that destination host do not get automatically discovered and added to the Enterprise Manager system.
The source host (where the Master Agent is running) and the destination host must be running on the same operating system. Therefore, if you have hosts running on different platforms, then you must have one deployment session per platform.
The Master Agent and the Shared Agent must be installed with the same user account.
(Only for Graphical Mode) 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 for Graphical Mode) Only SSH1 (SSH version 1) and SSH2 (SSH version 2) protocols offered by OpenSSH are supported for deploying a Management Agent.
(Only for Graphical Mode) 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 the wizard will internally use the underlying public key infrastructure to perform the installation.
To set up SSH public key authentication, follow these steps:
Navigate to the following location in the OMS home:
$<OMS_HOME>/oui/prov/resources/scripts
For example,
/home/software/em/middleware/oms/oui/prov/resources/scripts
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 <agent_install_1user_name> -hosts <target_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.
$HOME/.ssh/id_rsa
$HOME/.ssh/id_dsa
$HOME/.ssh/identity
If you want to provide additional keys, specify them as values for the oracle.sysman.prov.remoteinterfaces.identitylist property present in the $<OMS_HOME>/sysman/prov/agentpush/agentpush.properties file, using a comma separated list.
(Only for Graphical Mode) 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
Before installing a Shared Agent, ensure that you meet the following prerequisites:
Table 8-1 Prerequisites for Installing Shared Agent
| Requirement | Description |
|---|---|
|
Hardware Requirements |
Ensure that you meet the hard disk space and physical memory requirements. For more information, see the chapter on hardware requirements in the Oracle Enterprise Manager Cloud Control Basic Installation Guide. |
|
Destination Host Disk Space Requirements |
Ensure that the Master Agent host has a minimum of 1 GB free hard disk space, and the Shared Agent host has a minimum of 1 MB free hard disk space. |
|
Software Requirements (Only for Graphical Mode) |
(For Microsoft Windows) Ensure that you have installed Cygwin 1.7 on the destination host. For more information, see the chapter on installing Cygwin in the Oracle Enterprise Manager Cloud Control Basic Installation Guide. Note: While running |
|
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 Oracle Enterprise Manager Cloud Control Basic Installation Guide. 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,
|
|
|
Ensure that you install all the operating system-specific packages. For more information, see the chapter on package requirements in the Oracle Enterprise Manager Cloud Control Basic Installation Guide. |
|
|
Ensure that the destination host where you want to install the Management Agent has the appropriate users and operating system groups created. For more information, see the chapter on creating operating system groups and users in the Oracle Enterprise Manager Cloud Control Basic Installation Guide. |
|
|
Software Availability Requirements |
Ensure that you already have Oracle Management Agent 12c installed as a Master Agent in a shared, mounted location. |
|
Software Mount Requirements |
Ensure that you mount the Master Agent software by running the following command on the Shared Agent host:
For example, run the following command:
Also, ensure that the Management Agent user has only read permissions on the mount location, that is, the agent base directory of the Master Agent. |
|
/etc/hosts File Requirements |
Ensure that the
|
|
Destination Host Access Requirements |
Ensure that the destination hosts are accessible from the host where the OMS is running. Ensure that the destination host has read-only access to the software binaries of this Master Agent. If the destination host and the host on which OMS is running belong to different network domains, then ensure that you update the For example, if the fully-qualified host name is
|
|
Destination Host Credential Requirements (Only for Graphical Mode) |
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. |
|
Destination Host Time Zone Requirements (Only for Graphical Mode) |
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:
If the time zone displayed is incorrect, log in to the destination host, and follow these steps:
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. |
|
Time Zone Requirements (Only for Silent Mode) |
Ensure that the host time zone has been set correctly. To verify the host time zone, run the following command:
If the time zone displayed is incorrect, run the following commands, before running the
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 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 host after installing the Management Agent. For information on setting time zones post install, refer After You Install. |
|
sudo/pbrun/sesu/su SSH Requirements (Only for Graphical Mode) |
(Only for UNIX) Ensure that you set the Note: If you are using sudo as your privilege delegation tool, and you do not want to set the
|
|
sudo/pbrun/sesu/su Requirements (for Root User) (Only for Graphical Mode) |
(Only for UNIX)
|
|
sudo/pbrun/sesu/su Requirements (for Locked Account User) (Only for Graphical Mode) |
(Only for UNIX)
|
|
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 |
|
|
Instance Directory Requirements |
Ensure that the instance directory you enter is empty and has write permission. |
|
Ensure that the Master Agent home is accessible from the destination host where you want to install the Shared Agent. Ensure that the Master Agent home is mounted with the Ensure that the Shared Agent has read-only access to the software binaries of this Master Agent. |
|
|
PATH Environment Variable Requirements (Only for Graphical Mode) |
On the destination host, ensure the following:
|
|
Path Validation Requirements (Only for Graphical Mode) |
Validate the path to all command locations. For more information, see the appendix on validating command locations in the Oracle Enterprise Manager Cloud Control Basic Installation Guide. |
|
|
If the value assigned to the CLASSPATH environment variable has white spaces in it, then ensure that you unset it. You can always reset the environment variable to the original value after the installation is complete. |
|
(Only for Graphical Mode) |
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:
If the port is a non-default port, that is, any port other than 22, then update the
|
|
Port Requirements |
Ensure that the default ports described in What Default Ports Are Used? are free. |
|
Installing User Requirements |
|
|
Central Inventory (oraInventory) Requirements |
|
|
Agent User Account Permissions and Rights (Only 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:
To verify whether the agent user has these rights, follow these steps:
|
|
Permissions for cmd.exe (Only 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 For more information on this restriction and to understand how you can grant these permissions, access the following URL to Microsoft Web site: |
|
Preinstallation/Postinstallation Scripts Requirements (Only for Graphical Mode) |
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 (Only for Graphical Mode) |
|
This section describes the following:
To install a Shared Agent in graphical mode, follow these steps:
In Cloud Control, do one of the following:
From the Setup menu, select Add Targets, and then, click 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, and then, click 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.
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 you enter does not have underscores.
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
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.As the Shared Agent can be installed only if the source host and the destination host are running on the same platform, set the platform for the first host in the first row of 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.
Note:
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 access the Self Update Console within Enterprise Manager Cloud Control, download the software, then apply it.To access the Self Update Console, from the Setup menu, select Extensibility, then select Self Update. To download the latest Management Agent software, click Agent Software, select the required software, then click Download.
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.
Click Next.
On the Installation Details page, do the following:
In the Deployment Type section, select Add Host to Shared Agent. Then, for Select Target, click the torch icon and select the Management Agent that is shared and mounted. This location must be visible on all remote hosts.
Figure 8-1 describes this step.
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 Oracle Home, validate or enter the location of the shared Management Agent home. Ensure that this location is accessible from all the destination hosts.
For Instance Directory, enter the absolute path to a directory where all Management Agent-related configuration files can be stored. Ensure that the directory has write permission.
For example, /usr/home/software/oracle/agentHome/agent_inst
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.
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 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:
/usr/bin/sudo -u %RUNAS% %COMMAND% /usr/bin/sesu - %RUNAS% -c "%COMMAND%" /usr/bin/pbrun %PROFILE% -u %RUNAS% %COMMAND% /usr/bin/su - %RUNAS% -c "%COMMAND%"
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.
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.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 it 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 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 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, this parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.
Repeat Step 3 (b) to Step 3 (h) for every other row you have in the table.
Click Next.
On the Review page, review the details you have provided and if you are satisfied with the details, then click Deploy Agent to install the Management Agent.
If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes.
When you click Deploy Agent and submit the deployment session, you are automatically taken to the Add Host Status page that enables you to monitor the progress of the deployment session.
Note:
If you restart the destination host after installing a Shared Agent, and the Shared Agent does not start up automatically, restore the mount, and start the Shared Agent manually by running the following commands on the host:mount -t nfs -o ro <master_agent_host_name>:<agent_base_dir_of_master_agent> <agent_base_dir_of_shared_agent> $<INSTANCE_HOME>/bin/emctl start agent
Table 8-2 lists the additional parameters supported for installing a Shared Agent in graphical mode.
Table 8-2 Supported Additional Parameters
| Parameter | Description |
|---|---|
|
EM_STAGE_DIR |
Enter the absolute path to a custom location that can be created as a temporary Provisioning Advisor Framework (PAF) staging directory. By default, every time you install a Management Agent, a PAF staging directory is created for copying the Software Library entities related to the deployment procedures. By default, this location is the scratch path location ( If you want to override this location with a custom location, you can pass this option and enter a custom location. For example,
|
|
b_startAgent=false |
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. |
|
b_secureAgent=false |
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 For example, If you do not specify this parameter, the Management Agent is secured automatically after the install. |
To install a Shared Agent in silent mode, follow these steps:
Create a response file titled AgentNFS.rsp as described in Table 8-3.
Note:
The response file you create can have any name, and not necessarilyAgentNFS.rsp. For easy understanding, this chapter uses the name AgentNFS.rsp. Also, instead of creating a response file, you can choose to pass the arguments explicitly while invoking the script. However, Oracle recommends that you create a response file and capture the information there.Invoke the script from the Master Agent home, which is visible as a shared location, and pass the response file.
$<AGENT_HOME>/perl/bin/perl <AGENT_HOME>/sysman/install/AgentNFS.pl -responseFile=<absolute_path_to_response_file>
For example,
/scratch/agent_base_dir/core/12.1.0.2.0/perl/bin/perl /scratch/agent_base_dir/core/12.1.0.2.0/sysman/install/AgentNFS.pl -responseFile=/home/john/AgentNFS.rsp
Note:
Instead of creating a response file, you can choose to pass all the arguments explicitly while invoking the script. In this case, invoke the script in the following way:
$<AGENT_HOME>/perl/bin/perl <AGENT_HOME>/sysman/install/AgentNFS.pl AGENT_INSTANCE_HOME=<absolute_path_to_instance_dir> ORACLE_HOME=<absolute_path_to_master_agent_oracle_home> <parameter1>=<value1> <parameter2>=<value2> <parameter3>=<value3>...
For example,
/scratch/agent_base_dir/core/12.1.0.2.0/perl/bin/perl /scratch/agent_base_dir/core/12.1.0.2.0/sysman/install/AgentNFS.pl AGENT_INSTANCE_HOME=/home/john/agent_inst ORACLE_HOME=/scratch/agent_base_dir/core/12.1.0.2.0 AGENT_PORT=1832 AGENT_REGISTRATION_PASSWORD=welcome b_startAgent=TRUE
If the Master Agent was installed using the Add Host Targets Wizard, then ensure that you pass the following arguments with these values:
AGENT_REGISTRATION_PASSWORD=<password>
b_startAgent=TRUE
Do NOT pass the -invPtrLoc argument because, by default, the location <AGENT_HOME>/oraInst.loc is honored, where <AGENT_HOME> is the Master Agent. Also ensure that the Oracle Inventory directory, to which the inventory file points, is not in a shared location.
If you restart the destination host after installing a Shared Agent, and the Shared Agent does not start up automatically, restore the mount, and start the Shared Agent manually by running the following commands:
mount -t nfs -o ro <master_agent_host_name>:<master_agent_base_dir> <shared_agent_base_dir> $<INSTANCE_HOME>/bin/emctl start agent
When prompted to run the root.sh script, run it from the instance directory of the Management Agent:
<AGENT_INSTANCE_HOME>/root.sh
If you are not a root user, then use SUDO to change to a root user. For example, run the following command:
/usr/local/bin/sudo /scratch/OracleHomes/agent_inst/root.sh
Repeat Step (1) to Step (3) on the remaining hosts where you want to install the Shared Agent.
For silently installing a Shared Agent, you must invoke the AgentNFS.pl script and pass a response file that captures all the required information. Table 8-3 describes the various parameters you must include in the response file.
Table 8-3 Creating a Response File for Installing Oracle Management Agent Using the AgentNFS.pl Script
| Parameter | Description |
|---|---|
|
ORACLE_HOME |
Specify the absolute path to the Master Agent home, which is shared and visible on the destination host. For example, |
|
AGENT_PORT |
(Optional) Enter the port on which the Shared Agent process should be started. You can enter any free port between 1830 and 1849. The same port is used for both HTTP and HTTPS. For example, |
|
AGENT_INSTANCE_HOME |
Specify the absolute path to a location on the destination host where you want to store all Management Agent-related configuration files. For example, |
|
b_startAgent |
Set it to Note: If the Master Agent was installed using the Add Host Targets Wizard, then you must pass this parameter. |
|
ORACLE_HOSTNAME |
(Optional) (Only for Installation on Virtual Hosts) Specify the virtual host name where you are installing the Shared Agent. |
|
AGENT_REGISTRATION_PASSWORD |
Enter a password for registering new Management Agents that join the Enterprise Manager system. By default, the communication between the OMS and the Management Agents is secured and locked. Any new Management Agents that join the Enterprise Manager system must be authenticated before they become part of the system. The password you enter here will be used for authenticating those new Management Agents. For example, Note: If the Master Agent was installed using the Add Host Targets Wizard, then you must pass this parameter. |
After you install a Shared Agent, follow these steps:
(Only for Graphical Mode) 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 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.
Navigate to the Shared Agent instance home and run the following command to see a message that confirms that the Management Agent is up and running:
$<AGENT_INSTANCE_HOME>/bin/emctl status agent
Note:
If the status of the Management Agent is down for some reason, then manually start the Management Agent by running the following command from its Oracle home:$<AGENT_INSTANCE_HOME>/bin/emctl start agent
Navigate to the Shared Agent home and run the following command to see a message that confirms that EMD upload completed successfully:
$<AGENT_INSTANCE_HOME>/bin/emctl upload
(Only for Graphical Mode) 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.
In Enterprise Manager Cloud Control 12c Release 2 (12.1.0.2), nmosudo is located in the sbin directory, which is in the agent base directory. For example, <AGENT_BASE_DIRECTORY>/sbin/nmosudo. In Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) [with or without Bundle Patch 1], nmosudo is located in the agent instance directory. For example, <AGENT_INSTANCE_DIRECTORY>/bin/nmosudo.
Therefore, when you install an Enterprise Manager Cloud Control 12c 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.
sudouser ALL : oracle /eminstall/basedir/sbin/nmosudo *
(Only for UNIX Operating Systems) If you had ignored the prerequisite check warning about not having root privileges, SUDO binaries, or SUDO privileges, then manually run the following scripts as a root user from each of the hosts where the cloning was done. If you do not have SUDO privileges, then request your Administrator who has the privileges to run these scripts.
If this is the first Oracle product you just cloned 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 to change to a root user. For example, run the following command:/usr/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 to change to a root user. For example, run the following command:/usr/bin/sudo $<AGENT_HOME>/root.sh
If you had ignored a prerequisite check warning about wrong time zone settings, follow these steps:
Set the correct time zone on the required host.
For information on how to set the time zone on a host, refer Time Zone Requirements in Table 8-1.
Deinstall the Management Agent present on the host.
For information on how to deinstall a Management Agent, refer to Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
Install a Management Agent on the host.
By default, the host and the Shared 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.
|
 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|