This document describes in detail the Steps for Installing Enterprise Manager 12.1.0.2(12C Release 2) in graphical mode.

It includes the following:

Prerequisites
Installation Types
Advanced Installer Options
Post Installation Tasks
Installation log location

Scope

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

Oracle® Enterprise Manager Cloud Control Basic Installation Guide
This document does NOT cover the procedure for Upgrading your existing Enterprise Manager system. To upgrade your existing Enterprise Manager 12c R1(12.1.0.1) to 12c R2(12.1.0.2), refer to the following 12CR2 Upgrade My Oracle Support notes and OTN documentation:

Oracle® Enterprise Manager Cloud Control Upgrade Guide

Details

How to Install Enterprise Manager Cloud Control 12.1.0.2 (12c R2):

Before You Begin:

1. Oracle Management Service 12c Release 2 (12.1.0.2) can communicate with Oracle Management Agent 12c Release 1 (12.1.0.1) and Oracle Management Agent 12c Release 2 (12.1.0.2), and not with any earlier release of the Management Agent.

Where as, Oracle Management Service 12c Release 1 (12.1.0.1) can communicate only with Oracle Management Agent 12c Release 1 (12.1.0.1), and not with any earlier release or higher release of the Management Agent.

	Agent 12.1.0.1	Agent 12.1.0.2
OMS 12.1.0.1	YES	NO
OMS 12.1.0.2	YES	YES

2. 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 "<JAVA_HOME_PATH>/bin/java -fullversion"
64-bit JDK is installed for 64-bit platform using "file java" from <JAVA_HOME_PATH>/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.

3. Ensure that there are no white spaces in the name of the directory where you download and run the Enterprise Manager Cloud Control software from. For example, do not download and run the software from a directory titled "EM12C Software" because there
is a white space between the two words of the directory name.

4. You must not set the ORACLE_HOME and ORACLE_SID environment variables. You must ensure that the Oracle directories do NOT appear in the PATH.

Prerequisites:

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

1. 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 2 (12.1.0.2)here.

2. Operating System Requirements:

a) Certified Operating System:

Ensure that you install Enterprise Manger Cloud Control only on certified operating system as mentioned in theEnterprise Manager Certification
Matrix.

b) OS Package Requirements:

Ensure that you install all the operating system-specific packages as mentioned in Install Guide SectionMeeting
Package, Kernel Parameter, and Library Requirements

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: /bin/sh -c "ulimit -n"

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

<UID> soft nofile 4096

<UID> hard nofile 4096

Host File Requirements:

1. Ensure proper entries are there in etc/hosts file as shown below and also no duplicate entries for the same IP address:

127.0.0.1 localhost.localdomain localhost

<IP ADDRESS> <HOSTNAME.DOMAINNAME> <ALIAS/SHORT NAME>

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

3. Verify the Hostname resolution for OMS Server.

If the DNS is configured you can issue the following commands from any server in the network:

$ nslookup <IP adddress of the OMS machine>

$ nslookup <hostname.domain of the OMS machine>

$ nslookup <hostname of the OMS machine>

Existing Database Version Requirement:

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

2. Ensure that the database is patched with all the Patch Set Updates (PSU) or Critical Patch Updates (CPU) released for that release. Also ensure that you apply the patches.

3. If you use Oracle Database 11g Release 2 (11.2.0.1), then ensure that you apply the patches for bugs 10014178 and 8799099.

NOTE:

Bug 10014178 is closed as a duplicate of Bug 9260085.

Patch 9260085 is available for Oracle Solaris on SPARC (64-bit) , IBM AIX on Power systems (64-bit) and Linux x86-64 OS on top of 11.2.0.1 DB.

4. If you use Oracle Database 11g Release 1 (11.1.0.7), then ensure that you apply Patch Set Update 2 and the patches for bugs 8644757 and 7525072.

5. The database can also have the Automatic Memory Management (AMM) feature enabled.

6. Ensure that this database is dedicated to Enterprise Manager.

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

8. Ensure that pre-requisite DB parameters are set as mentioned in install guidehere.

Installing User Requirements:

1. (For UNIX only) The installation must NOT be run by a root user.

2. (For Microsoft Windows only) User must be part of the ORA-DBA group and have administrator permissions.

3. (For Microsoft Windows only) User must belong to the DBA group, and have permissions to perform the following: Act as part of the operating system, Create a token object, Log on as a batch job, and Adjust memory quotas for a process.

To verify whether the install user has these rights, 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 Policy. In the
Local Security Settings window, from the tree structure, expand Local Policies, and then expand User Rights Assignment.

Central Inventory Location Requirements:

Ensure that the Central 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 MOS document 1092645.1

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

1. Simple Installation

The simple installation type installs with default configuration settings and preferences that you need for a complete Enterprise Manager system. It does not offer too many options to customize your installation. This installation type is meant for demo or
evaluation purposes, and small deployments, and when you do not want to worry about the granular control of the installer and want to install the Enterprise Manager system quickly, with less memory, and for monitoring fewer targets in their environment.

2. Advanced Installation

The Advanced installation type 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.

Advanced installation type helps you with the EM planning:

Small
Medium
Large

Refer
Overview of the Installation Types

To install Enterprise Manager Cloud Control 12.1.0.2 with simple configuration:

1. Invoke the Enterprise Manager Cloud Control Installation Wizard:

Invoke the installation wizard as a user who belongs to the oinstall group you created.

<Software_Location>/runInstaller

In this command, <Software_Location> is either the DVD location or the location where you have downloaded the software kit.

NOTE:

To invoke the installation wizard on UNIX platforms, run runInstaller. To invoke on Microsoft Windows platforms, run setup.exe

When you invoke runInstaller or setup.exe, if the Enterprise Manager Cloud Control Installation Wizard does not appear, then it is possible that you do not have read and write access to the /stage subdirectory, which a subdirectory in the Disk1 directory of
the Enterprise Manager software.

There is a classpath variable that the installation wizard computes for OPatch as ../stage/Components/, and when the TEMP variable is set to /tmp, the installation wizard tries to look for the opatch JAR file in the /tmp/../stage directory, which is equivalent
to /stage. However, if you do not have read and write permission on /stage, then the installation wizard can hang. Under such circumstances, verify if you have read and write access to the /stage directory. If you do not have, then set the TEMP variable to
a location where the install user has access to, and then relaunch the installation wizard.

2. Enter My Oracle Support Details:

(Optional)On the My Oracle Support Details screen, enter your My Oracle Support credentials to enable Oracle Configuration Manager. If you do not want to enable Oracle Configuration Manager now, unselect the check box and click on next.

If the host from where you are running the installation wizard does not have a connection to the Internet, then enter only the e-mail address and leave the other fields blank. After you complete 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.

NOTE:

If you choose to skip installing the software updates during installation by not providing the My Oracle Support credentials, you can always register the credentials later using the Enterprise Manager Cloud Control console and view the recommended security
patches. To do so, log in to Enterprise Manager Cloud Control, and from the Setup menu, select My Oracle Support, then click Set Credentials. On the My Oracle Support Preferred Credentials page, enter the credentials and click Apply.

4. Enter Oracle Inventory Details:

If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on UNIX operating system, then the Oracle Inventory screen appears.

On the Oracle Inventory screen, do the following. You will see this screen only if this turns out to be 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. The group that you select must have write permissions on the Oracle Inventory directories.

NOTE:

If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on Microsoft Windows operating system, then the Oracle Inventory screen does not appear. On Microsoft Windows, the following is the default inventory
directory:

<system drive>\Program Files\Oracle\Inventory
5. Check Prerequisites:

check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful installation.

The installation wizard runs the prerequisite checks automatically when you come to this screen. It checks for the required operating system patches, operating system packages, and so on.

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. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems,
return to this screen and click Rerun to check the prerequisites again.

NOTE:

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 failuresHowever, all package requirements must be met or fixed before proceeding any
further. Otherwise, the installation might fail.
6. Select Installation Type:

Select Create a New Enterprise Manager System, then select Simple.

7. Enter Installation Details:

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.

What's new on this screen when compared to EM 12C release 1(12.1.0.1):

1. You will be asked to provide Agent Base Directory to allow consistent agent homes across the OMSes

Enter the absolute path to the agent base directory, a location outside the Oracle Middleware home where the Management Agent can be installed.

2. Host Name:

To validate the name of the host where you want to configure the OMS

The host name appears as a fully qualified name. The host name can also appear as a virtual host name if your host is configured with virtual machine.

You can choose to accept the default host name and proceed with the installation. Alternatively, you can change the name if it is incorrect, or enter another host name for this host. Ensure that the host name you enter is accessible from other hosts in the
network

8. Enter Configuration Details:

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.

The installer uses this information to connect to the existing database for creating the SYSMAN schema and plug-in schemas.

9. 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, if you are satisfied, click Install to begin the installation process.

10. Install Progress:

View the overall progress (in percentage) of the installation and the status of each of the configuration assistants. Configuration assistants are run for configuring the installed components of Enterprise Manager Cloud Control.

11. Execute Configuration Scripts:

Once the software binaries are copied and configured, you are prompted to run the allroot.sh script, and the oraInstRoot.sh script if this is the first Oracle product installation on the host. Open another window, log in as root, and manually run the scripts.

If you are installing on Microsoft Windows operating system, then you will NOT be prompted to run this script.

12. Finish (End the Installation)

You should see information pertaining to the installation of Enterprise Manager. Review the information and click Close to exit the installation wizard.

For more information about this installation, refer to the following file in the OMS home:

$<OMS_HOME>/install/setupinfo.txt

To install Enterprise Manager Cloud Control 12.1.0.2 with Advanced configuration:

The below series of screens remains same as in
Simple configuration installation type:

1. Invoke the Enterprise Manager Cloud Control Installation Wizard.

2. Enter My Oracle Support Details.

3. Install Software Updates.

4. Enter Oracle Inventory Details.

5. Check Prerequisites.

6. Select Installation Type - You should select 'Advanced'

7. Enter Installation Details.

8. Plug-in Deployment:

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 / pre-selected indicate the mandatory plug-ins
that will be installed.

NOTE:

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

By default, the WebLogic Domain name is GCDomain, and the Node Manager name is nodemanager. The installer uses this information for creating Oracle WebLogic Domain and other associated components such as the admin server, the managed server, and the node manager.

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

The installer uses this information to connect to the existing database for creating the SYSMAN schema and plug-in schemas. If you provide details of a database that already has a preconfigured Management Repository, then the installer only creates plug-in
schemas.

What's new on this screen when compared to EM 12C release 1(12.1.0.1):

Select the deployment size from the drop down next to 'Deployment Size' list to indicate the number of targets you plan to monitor, the number Management Agents you plan to have, and the number of concurrent user sessions you plan have.

Deployment Size	Targets Count	Management Agents Count	Concurrent User Session Count
Small	Up to 999	Up to 99	Up to 10
Medium	Between 1000 and 9999	Between 100 and 999	Between 10 and 24
Large	10,000 or more	1000 or more	Between 25 and 50

NOTE:

1. For more information on deployment sizes, the prerequisite checks that are run, the database parameters that are set, and how you can modify the deployment size after installation, refer toOracle
Enterprise Manager Cloud Control Advanced Installation and Configuration Guide

2. You might get a message related to Prerequisite check for the below:

Disable Stats Gathering job

Click Yes to let the installer fix the issue automatically.

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

The below series of screens remains same as in
Simple Configuration installation type:

13. Review and Install

14. Install Progress

15. Execute Configuration Scripts

16. Finish (End the Installation)

Advanced Installer Options:

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

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

To understand the limitations involved with this advanced option, see
Limitations.

Post Installation Tasks:

Verify the OMS status:

$<OMS_HOME>/bin/emctl status oms

Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.2.0

Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.

WebTier is Up

Oracle Management Server is Up
Verify the Agent status:

$<AGENT_HOME>/bin/emctl status agent
Verify the Agent upload:

$<AGENT_HOME>/bin/emctl upload

Installation Log location:

Installation logs:

oraInventory/logs/*.*

<ORACLE_HOME>/cfgtoollogs/oui/*.*

Configuration Logs:

<ORACLE_HOME>/cfgtoollogs/cfgfw/*

Specific Configuration logs:

Configuration Assistant	Log Location
Repository configuration logs	<OMS_ORACLE_HOME>/sysman/log/schemamanager/*
OMS configuration logs	<OMS_ORACLE_HOME>/cfgtoollogs/omsca/*
PluginCA configuration logs	<OMS_ORACLE_HOME>/cfgtoollogs/pluginca/*
Agent configuration logs	<AGENT_ORACLE_HOME>/cfgtoollogs/cfgfw/*

from:metalink

内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理

标签：

相关文章推荐

新的分享

章节导航