Skip Headers
Oracle® Enterprise Manager Cloud Control Upgrade Guide
12c Release 2 (12.1.0.2)
E22625-16
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

E Meeting Prerequisites for Installing Oracle Management Agent

Table E-1 lists the prerequisites you must meet before installing Oracle Management Agent (Management Agent).

Table E-1 Prerequisites for Upgrading Oracle Management 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.

Operating System Requirements

Ensure that you install Enterprise Manager Cloud Control 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.2.0, and click Search.

Package Requirements

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.

User and Operating System Group Requirement

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.

Destination Host Requirements

Ensure that the destination hosts are accessible from the host where the Preupgrade Console is being used.

Permission Requirements

  • Ensure that the installation base directory you specify is empty and has write permission.

  • Ensure that the instance directory is empty and has write permission.

  • Ensure that the installing user owns the agent base directory. Ensure that the installing user or the root user owns all the parent directories. Ensure that the root user owns the root directory. And ensure that all of these directories have read and execute permissions for group and other users.

    For example, if the agent base directory is /scratch/OracleHomes/agent, and if 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. And directories /, scratch, and OracleHomes have read and execute permissions.

Path Validation Requirements

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.

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.

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.

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:

    INVENTORY_LOCATION=<absolute_path_to_inventory_directory>

    -invPtrLoc <absolute_path_to_oraInst.loc>

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

Ping Requirements

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

  1. Access 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. Change PING_PATH=/bin/ping to PING_PATH=/bin/true.

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) Ensure that the SCP binaries (for example, /usr/local/bin/scp) are in the PATH environment variable.