Skip Headers
Oracle® Enterprise Manager Cloud Control Upgrade Guide
12c Release 1 (12.1.0.1)
E22625-09
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

11 Deploying and Configuring Oracle Management Agent

To deploy Oracle Management Agent 12c, follow these steps:


Note:

  • Perform these steps in the Enterprise Manager Grid Control console of the earlier release.

  • You cannot deploy and configure Oracle Management Agent 12c for problematic Management Agents. To identify the problematic Management Agents, see Identifying Problematic Oracle Management Agents.

  • Also, you must deploy and configure Oracle Management Agent 12c only on existing Management Agents that are completely upgradable. To identify whether the Management Agents are completely upgradable, see Checking the Upgradability Status of Oracle Management Agents.

  • For the 2-System upgrade, do NOT deploy Oracle Management Agent 12c on the remote host because the Enterprise Manager installer will take care of installing it while installing Oracle Management Service 12c.

  • To deploy and configure Oracle Management Agent 12c, the existing connectivity between the old Management Agent and the OMS is used; SSH is not used.

  • For 2-System upgrade, if your old Management Agent was running in secure (or unsecure) mode before backing up the Management Repository, then ensure that it continues to run in the same mode while you deploy and configure the new Management Agent for it. Do not resecure the Management Agents after backing up the Management Repository. If you do so, the ping test might fail while performing the healthcheck because of a mismatch between the configuration stored in the repository and the actual configuration of the Management Agent. You will see a KEY_MISMATCH error in gcagent.log. For information on this error and to know how to secure the Management Agents without facing this issue, see Appendix H.


  1. In Grid Control, click Deployments.

  2. On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.

  3. On the Upgrade Console page, in the Select Upgrade Type section, select one of the following. For information about these upgrade approaches, see "Understanding Upgrade Approaches".

    • To upgrade your Enterprise Manager system with downtime (even if you manually install Management Agents), select 1-System.

    • To upgrade your Enterprise Manager system with "near zero" downtime (even if you manually install Management Agents), select 2-System.

    • To upgrade your Enterprise Manager system with downtime on a different host, select 1-System on a Different Host.

    Enterprise Manager Grid Control refreshes the page and displays a table with a list of tasks you need to perform for the upgrade approach you selected.

  4. In the Preupgrade Steps section, from the table, click Deploy and Configure Agents.

  5. On the Deploy and Configure Agents page, for Operation Name, enter a unique name for the deployment operation you are about to perform. 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, Deploy_Agents_Phase1_2010_12_23.


    Note:

    The operation name you enter here is only a logical name and will be used for saving the details of the operation you are about to perform. After deploying the software binaries of Oracle Management Agent 12c, at a later point in time, if you want to check the health of the deployed Management Agents or switch over from old to newly deployed and configured Management Agents, then you can use the operation name to identify and track the Management Agents selected as part of this operation.

  6. In the Select Operation Type section, select Deploy Agent and Plug-In Software and Configure Agent and Plug-In Software.


    Note:

    If you had already deployed the software binaries of the Management Agent, then you can choose to only configure them now. In this case, select only Configure Agent and Plug-In Software.

  7. In the Search Agents section, search and add the existing, old Management Agents for which you want to deploy the software. To understand how to search and add Management Agents, see Appendix G.


    Note:

    • If you had already deployed the software binaries of the Management Agent, and if you are only configuring them at this point, then search (or add) and select the Management Agents for which you had already manually deployed the software.

    • If you are adding a Shared Agent, then ensure that you add the Master Agent to which it communicates, and all the Shared Agents that communicate with this Master Agent.

    • When you return to this screen to retry the deploy operation, you will see the Management Agents selected as part of the previous deploy operation. This is an expected behavior. You can choose to redeploy the software binaries for them, or remove them from the list and add a fresh set of Management Agents.


  8. In the table that lists the Management Agents, enter an installation base directory and an instance home directory for each of the Management Agents.


    Note:

    • Ensure that the installation base directory you enter here is NOT inside the middleware home.

    • Ensure that the installation base directory has at least 110 MB of free disk space.

    • If you had already deployed the software binaries of the Management Agent, and if you are only configuring them at this point, then enter the same installation base directory and the instance home directory where you had deployed the software binaries.

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


    If you want the paths to the installation base directory and the instance home directory to be the same across Management Agents, then select Use Same Paths for All Agents, and enter the absolute path for installation base directory and instance home directory, just once, for the first Management Agent listed in the table. Enterprise Manager Grid Control will consider the same paths for other Management Agents listed in the table.


    Note:

    You cannot select Use Same Paths for All Agents with the installation base directory mentioned for one Management Agent and the instance home directory mentioned for another Management Agent in the table. Only the paths specified for the first Management Agent will be considered as the same paths for other Management Agents in the table.

    If the agent base directory or the agent instance home directory specified by you already exists, and if you want to overwrite them, then select Overwrite Any Existing Directories. Typically, you will select this option when you choose to redeploy the software binaries in the same base directory.

  9. After you add the Management Agents, select each of them from the Select column.

  10. In the Agent Credentials section, retain the default selection, that is, Use Oracle Home Preferred Credentials, so that the preferred credentials stored in the Management Repository can be used for this job.


    Note:

    Ensure that the preferred credentials were registered with the Enterprise Manager system using the Enterprise Manager Command Line Interface (EM CLI). For more information, see Setting Preferred Credentials Using EMCLI.

    You can optionally override these preferred credentials. To do so, select Override Oracle Home Preferred Credentials and enter one set of credentials that can be used for all Oracle homes.


    Note:

    Ensure that you use the same credentials that you used for the existing, earlier release of the Management Agent

  11. In the Run Privilege section, by default, None is selected assuming that the credentials you have provided in the previous step have the privileges to run this job.

    However, if those credentials do not have the privileges to run this job, and if you want to switch over as another user for this purpose, then select either SUDO or Power Broker, depending on the authentication utility you want to use, and provide the user account name and profile.

  12. In the OMS Host and Port section, validate the name and the secure port of the host where you plan to install Oracle Management Service 12c. To change the values, click Edit.


    Note:

    If you had already upgraded your existing OMS to Oracle Management Service 12c, then ensure that the port you enter here matches with the Enterprise Manager Upload HTTP SSL Port you selected or specified in the installer while upgrading the OMS.

  13. Click Next.

  14. On the Optional Details page, in the Pre-Deploy Options section, select Run Pre-Command/Script if you want to run any script before deploying the software binaries of the Management Agents.

    Enter the absolute path to a location on the destination host where the script is available. The script can also be in a shared location, but you must have execute privileges on it to run the script.


    Note:

    By default, the credentials provided in Step (10) are used for running the script. And by default, None is selected assuming that the credentials have the privileges to run the script.

    However, if those credentials do not have the privileges to run the script, and if you want to switch over as another user for this purpose, then select either SUDO or Power Broker, depending on the authentication utility you want to use, and provide the user account name and profile.


  15. In the Post-Config Options section, select Run Post-Command/Script if you want to run any script after configuring the deployed Management Agents.

    Enter the absolute path to a location on the destination host where the script is available. The script can also be in a shared location, but you must have execute privileges on it to run the script.


    Note:

    By default, the credentials provided in Step (10) are used for running the script. And by default, None is selected assuming that the credentials have the privileges to run the script.

    However, if those credentials do not have the privileges to run the script, and if you want to switch over as another user for this purpose, then select either SUDO or Power Broker, depending on the authentication utility you want to use, and provide the user account name and profile.


  16. (Only for UNIX) In the Root Credentials section, enter the credentials of a user account to run the root.sh script.


    Note:

    By default, None is selected assuming that the credentials have the privileges to run the script. However, if those credentials do not have the privileges to run the script, and if you want to switch over as another user for this purpose, then select either SUDO or Power Broker, depending on the authentication utility you have, and provide the user account name and profile.

    If you do not have root credentials, then enter the agent credentials. In this case, the root.sh script is not run, but the deployment succeeds. Ensure that you manually run this script after Management Agent deployment, before using the new Enterprise Manager Cloud Control 12c system. Otherwise, you will not be able to run jobs on the Management Agent. If the root.sh script is not executed, Management Agent switchover will not be affected.


  17. Click Submit.


Note:

  • After you submit the operation, if you see the following error, then first run root.sh from the old Management Agent home, and then, resubmit this operation.

    ERROR: NMO not setuid-root (Unix-only) 
    
  • If you see the following error, then verify the credentials entered in Step (10).

    Local Authentication Failed...Attempt PAM authentication...PAM failed . . .
    
  • If the deployment operation fails at some point, you can choose to only reconfigure the Management Agents, and not copy the software binaries all over again. To only reconfigure the Management Agents, repeat the instructions outlined in this procedure, but for Step (6) ensure that you select only Configure Agent and Plug-In Software.

  • When the operation is in progress, if a Management Agent being deployed and configured becomes unavailable for some reason, you may see the status Suspended on Event. Once the Management Agent becomes available, the status automatically changes to show the current state. This is an expected behavior.

  • If the credentials entered in Step (10) are incorrect, then the step for running the root.sh script fails in the predeployment job, but the job as such shows that it is successful. In this case, manually run the root.sh script using the correct root credentials. Otherwise, the Management Agent will result in NMO errors.