How to Install Enterprise Manager Cloud Control 12.1.0.1 (12c) on Linux [ID 1359176.1]

 

In this Document
  Purpose
  Scope and Application
  How to Install Enterprise Manager Cloud Control 12.1.0.1 (12c) on Linux
      Before You Begin
     Prerequisites
     Installation Steps
     Advanced Installer Options
     @References
  References

Applies to: Enterprise Manager Base Platform - Version: 12.1.0.1.0 and later   [Release: 12.1 and later ]
Information in this document applies to any platform.
PurposeThis document describes in detail the Steps for Installing Enterprise Manager 12c in graphical mode.
It includes the following:

• Prerequisites

• Instalation Steps

• Advanced Installer Options

Scope and ApplicationThis document describes in detail the Steps for Installing Enterprise Manager Cloud Control in graphical mode. You can also refer to Enterprise Manager 12c Basic Installation Guide on OTN from the following link:
        

For installing Enterprise Manager 12c Agents, refer to Document 1360183.1

This document does NOT cover the procedure for Upgrading your existing Enterprise Manager system. To upgrade your system to Enterprise Manager 12c, refer to the following EM 12c Upgrade My Oracle Support notes and OTN documentation:

          
How to Install Enterprise Manager Cloud Control 12.1.0.1 (12c) on Linux Before You BeginYou need to be aware of the following key bits of information before you begin installation:

• Enterprise Manager Cloud Control can communicate only with Oracle Management Agent 12c and not with any other earlier release of the Management Agent. You can not configure your exising Agents to communicate with Enterprise Manager 12c OMS.
  

• If you are installing on a host that has multiple host names, you need to pass the fully qualified host name using ORACLE_HOSTNAME argument. Ensure that the host name does not contain an underscore "_"; otherwise the installation might fail.
  

runInstaller ORACLE_HOSTNAME=host.oracle.com

• Enterprise Manager Cloud Control Installation Wizard installs Java Development Kit (JDK) 1.6.v24 and a new Oracle Weblogic Server (WLS) 10.3.5. Tere is no need for you to have an existing Oracle WebLogic Server instance as it was the case with Enterprise Manager 11g. It is recommended to use this option rather than installing Enterprise Manager 12c on an existing WebLogic Server instance.
  

However, if you already have a WebLogic Server instance installed, please check that:

• JDK is higher than 1.6 v24 using "/bin/java -fullversion"

• 64-bit JDK is installed for 64-bit platform using "file java" from /bin

• WebLogic Server version is 10.3.5

• Oracle WebLogic Server installation is a typical installation, and even if you choose to perform a custom installation, ensure that the components chosen for custom installation are the same as the ones associated with a typical installation.

• You do not have any other Oracle Fusion Middleware product installed in that Middleware Home.

• You will install Enterprise Manager Cloud Control with the same OS User who installed the WebLogic Server.

• JRockit is not used for WebLogic Server; as this is not supported.

• You should not install OMS on a NFS mounted drive. However, if you are forced to install on such a shared drive, specify the Instance Base Directory (gc_inst) on a non-NFS mounted drive.

Prerequisites

You need to ensure the following mandatory pre-requisites are met before you begin the installation:

Hardware Requirements:

• Ensure that you meet the hard disk space and physical memory requirements as mentioned in Oracle Enterprise Manager Cloud Control Basic Installation Guide 12c Release 1 (12.1.0.1) Section Meeting Package, Kernel Parameter, and Library Requirements .

Operating System Requirements:

a.) Certified Operating System:

• Ensure that you install Enterprise Manger Cloud Control only on certified operating system as mentioned in the .

b.) OS Package Requirements:

• Ensure that you install all the operating system-specific packages as mentioned in Install Guide .

c.) File Descriptor Requirement:

• Ensure that you set the file descriptor to a minimum of 4096. Verify the current value for file descriptors using the command "ulimit -n"
  

• If the current value is less than 4096, then as root user, update the /etc/security/limits.conf file as shown below:

soft nofile 4096
hard nofile 4096

Unique Host Name and Static IP Address Requirements:

• Ensure that you check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that is visible to other hosts in the network.

• You must use a static IP address. If you use a dynamic IP address, the installation might fail.

• Ensure that the host name specified in /etc/hosts file is unique, and that it maps to the correct IP address. Following is the recommended format of the /etc/hosts file:
  

• If the DNS server is configured, then it should resolve the host name for the OMS machine correctly. For example, all these command must return the same output:
  

nslookup host1
nslookup host1.foo.com
nslookup 141.81.5.71

Existing Database Version Requirement:

• Ensure that the existing database is a certified database as mentioned in Enterprise Manager Certification Matrix.

• Ensure that the latest Patch Set Updates (PSU) or Critical Patch Updates (CPU) is applied to the database.

• DB Control SYSMAN schema is created in the database as part of the database install. You need to deconfigure it using the following command:
  

a.) Set the ORACLE_HOME and ORACLE_SID environment variable:

For example:-
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
export ORACLE_SID=orcl

b.) $ORACLE_HOME/bin/emca -deconfig dbcontrol db -repos drop

Internet Connection Requirement:

• Oracle recommends that the host from where you are running the installer has a connection to the Internet so that the configuration information can be automatically collected and uploaded to My Oracle Support.

Installation Steps

1. Invoke the Enterprise Manager Cloud Control Installation Wizard

/runInstaller

2. Enter My Oracle Support Details



(Optional) Enter your my Oracle Support credentials to enable Oracle Configuration Manager. If you do not want to enable OCM, untick the checkbox "I wish to receive security updates".
If the host from where you are running the installation wizard does not have a connection to Internet , then only enter the e-mail address. After completing the installation, manually collect the configuration information and upload it to My Oracle Support.

3. Install Software Updates



Select one of the following sources from where the software updates can be installed. If you do not want to apply them now, then select Skip.

(Recommended) Select Search for Updates, and then, select "Local Directory" if you have manually downloaded the software updates to an accessible location. Enter the location where the updates are available, and click Search for Updates.

Select Search for Updates, and then, select My Oracle Support if you want the installer to connect to My Oracle Support and automatically download the updates from there.
Enter the My Oracle Support account user name and password, and click Search for Updates.

4. Enter the Oracle Inventory Details

This screen will appear only if this is your first ever installation of an Oracle product on the host.
Enter the full path to a directory where the inventory files and directories can be placed.
Select the appropriate operating system group name that will own the Oracle inventory directories. This group must have write permissions on the Oracle Inventory directories.

Note: The central inventory location must not be on a shared file system. If it is already on a shared file system, then switch to a non-shared file system by following the instructions in My Oracle Support Document 1092645.1.

5. Check Prerequisites



Check the status of prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful installation.
The status of the prerequisite check can be either Warning, Failed or Succeeded.

If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the installation. After correcting the problems, click Rerun.

If you prefer to hide the successful checks and view only the Warning or Failed ones, then click Hide Successful Checks.

Although Oracle recommends you to investigate and correct the problems, if you are compelled to proceed without resolving them, then select Ignore to ignore the warnings and failures. However, all package requirements, Hostname requirements and File Descriptor requirements must be met before proceeding further; otherwise the installation might fail.

6. Select Installation Type



Select Create a New Enterprise Manager System and then, select Simple for a Simple installation. This option is for a typical, default configuration. This is simple and quick, prompts only to enter Administrator password and database connection details. While the database connection details are used for connecting to your existing, certified Oracle database.
The Administrator password is used as common password for SYSMAN, WebLogic user account, node manager user account, and also for authenticating new Management Agents that join the Enterprise Manager system.

Select Create a New Enterprise Manager System and then, select Advanced for an Advanced installation. This option is meant for Administrators who wants custom or advanced and more flexible configuration. It prompts you for WebLogic Server details, database connection details, data file locations for tablespaces, password for creating SYSMAN account and also customize ports.

Provide an empty Middleware Home location for the OUI to install Weblogic along with the Enterprise Manager Cloud Control installation. If you already have a 10.3.5 Oracle WebLogic Server installation which you want to use; provide that location as the Middleware Home location.

7. (Simple) Enter Configuration Details



Enter an administrator password, which can be used as a common password for SYSMAN, WebLogic user account, node manager user accound and for authenticating new Management Agents that join the Enterprise Manager system.

Enter the fully qualified host name where the existing database resides, the database's listener port, database service name or SID, and password for SYS user.

8. (Advanced) Select Plug-ins



Select the optional plug-ins you want to install from the software kit while installing the Enterprise Manager system. The above screen lists the mandatory plug-ins as well as the optional plug-ins. The grayed rows indicate the mandatory plug-ins that will be installed.

During installation, if you want to install a plug-in that is not available in the software kit, then refer to Advanced Installer Options which describes how you can install additional plug-ins.

9. (Advanced) WebLogic Server Configuration Details



Enter the credentials for the webLogic Server user account and the Node Manager user account, and validate the path to the Oracle Management Service instance base location.

OMS Instance Base location is populated as the gc_inst directory under the provided Middleware Home location.
You can optionally provide a different location of your choice.
This directory is used for storing all configuration details related to Oracle Management Service 12c.

10. (Advanced) Database Connection Details



Enter the fully qualified host name where the existing database resides, the database's listener port, database service name or SID, and password for SYS user.

You might get a message related to Prerequisite check for the below:
            Disable Stats Gathering job
            Set job_queue_processes parameter to 200

Click Yes to let the installer fix the issue automatically.

11. (Advanced) Repository Configuration Details



Enter a password for creating the SYSMAN account which is the super administrator for Enterprise Manager Cloud Control. It is used for creating the SYSMAN schema which holds most of the relational data used in managing Enterprise Manager Cloud Control.

Enter a password for registering the new Management Agents that join the Enterprise Manager system.

Enter the full path to the location where the data file for management tablespace (mgmt.dbf) can be stored.
For example, /u01/oracle/prod/oradata/mgmt.dbf

Enter the full path to the location where the data file for configuration data tablespace (mgmt_ecm_depot1.dbf) can be stored.
For example, /u01/oracle/prod/oradata/mgmt_ecm_depot1.dbf

Enter the full path to the location where the data file for JVM diagnostics data tablespace (mgmt_ad4j.dbf) can be stored.
For example, /u01/oracle/prod/oradata/mgmt_ad4j.dbf

If you are configuring the Management Repository on a database that uses Oracle Automatic Storage Management (ASM) for storage, then provide the data file location as the disk group name. For example, specify +DATA and not +DATA/a/dbf.

12. (Advanced) Port Configuration Details



This screen, list the ports that will be used for various components.
You can customize any of the port; by providing a free port greater than 1024 and lesser than 65535.
If you already have the ports predefined in a staticports.ini file, then click Import staticports.ini File and select the file.

13. Review and Install



On the Review screen, review the details you provided for the selected installation type.
If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.
After you verify the details, and you are satisfied, click Install to begin the installation process.

14. (Only Unix) Once the software binaries are copied and configured, you are prompted to run the allroot.sh sciprt, and the oraInstRoot.sh script if this is the first Oracle product installation on the host. Open a new terminal, and run the scripts as root user.

Advanced Installer Options

• By default, GCDomain is the default name used for creating the WebLogic Domain. To use a custom WebLogic Domain name, invoke the installer with WLS_DOMAIN_NAME option as below:

$ runInstaller WLS_DOMAIN_NAME=EMDomain

• By default, a Provisioning Advisor Framework (PAF) staging directory is created for copying the Software Library entities related to the deployment procedures under /tmp. To override this location, invoke installer with EM_STAGE_DIR option as below:

$ runInstaller EM_STAGE_DIR=/home/john/software/oracle/pafdir

• To install some plug-ins that are not in the software kit, follow the below steps:

a.) Manually download the plug-ins from OTN and store them in accessible location.

b.) Invoke the installer with following option and pass the above location:

$ runInstaller -pluginLocation

@References@To install and Additional OMS, follow the Steps in Note.xxxx
ReferencesNOTE:1363863.1 - FAQ: Enterprise Manager Cloud Control 12c Install / Upgrade Frequently Asked Questions