Installing EM on ODA Cluster

Scope and Application

This document presents a step-by-step procedure on how to install EM Cloud Control 12c to monitor an Oracle Database Appliance (ODA) cluster. In this document, EM will be installed on the same ODA appliance. It is highly recommended to install EM on a different system than ODA for continuous monitoring during maintenance periods.

Overview
The installation and deployment of EM on ODA is comprised of three major sections: Repository Database Creation Management Server installation Management Agent Deployment Cluster Discovery and configuration

The Repository Database creation is done via DBCA on the ODA cluster. Database creation is covered in the ODA basic Installation and Administration Guide. In this document, our repository database name will be emdb

Install EM 12c Cloud Control System

EM 12c Software is available on OTN. To install EM 12c Cloud Control System, download the software from OTN onto the ODA cluster, or stage it on a shared volume. Install the Oracle Management Server first, then install the agents from the EM Console to each ODA node.

Stage EM Software
Navigate to the following URL on OTN and select EM 12c for Linux X86_64 platform. There are two disk archives: http://www.oracle.com/technetwork/oem/grid-control/downloads/index.html

-rw-r--r-- 1 oracle dba 2561176217 Nov 24 02:15 em12_linux64_disk1of2.zip -rw-r--r-- 1 oracle dba 3057842914 Nov 24 02:15 em12_linux64_disk2of2.zip Stage the disk archives on one of the ODA nodes and unzip the above packages. For example, copy the archives to /home/oracle/CC12c for the staging directory.

As the oracle user, run: $ $ unzip em12_linux64_disk1of2.zip unzip em12_linux64_disk2of2.zip

Run native VNC Server on the first node so that you can launch the installer GUI. As the oracle user, execute: $ vncserver From your VNC Client, access this node using the first display ID. For example:

Remove any non-system environment settings from the session where you will launch the installer. Unset any variables such as: JAVA_PATH, JAVA_HOME, ORACLE_HOME, LD_LIBRARY_PATH, or any other specific environment variables. Create a directory that will contain the EM 12c installation. For example, execute the following as the root user: # mkdir /u02; chmod 777 /u02

Now, you are ready to launch the installer.

Install EM 12c Oracle Management Server

Launch the installer from the staging directory where you unzipped the two disk archives. $ $ cd /home/oracle/CC12c/install ./runInstaller

The following screen shots are presented. My Oracle Support Details. Please select the appropriate response for My Oracle Support Details.

Software Updates. You can search for the latest EM 12c updates from OTN if your server can access the internet. Otherwise, select Skip and continue installation. You can check for updates after the software is installed and stage any patches on the server manually.

Prerequisite Checks

Install Types.

Specify /u02/Middleware as the middleware home location

Configuration Details. Provide an Admin Server password and database connection details. Remember this password. In our example welcome123

Deconfigure dbconsole from the newly created repository database emdb

Set your environment to the emdb repository database home and ORACLE_SID. Then, run following command as the oracle user on the cluster node: $ORACLE_HOME/bin/emca -deconfig dbcontrol db -repos drop -cluster -SYS_PWD welcome1 -SYSMAN_PWD welcome1 eg:
[oracle@slcac452-x0 ~]$ echo $ORACLE_HOME /u01/app/oracle/product/11.2.0/dbhome_1 [oracle@slcac452-x0 ~]$ $ORACLE_HOME/bin/emca -deconfig dbcontrol db -repos drop -cluster -SYS_PWD welcome1 -SYSMAN_PWD welcome1

STARTED EMCA at Nov 29, 2011 2:40:00 PM EM Configuration Assistant, Version 11.2.0.0.2 Production Copyright (c) 2003, 2005, Oracle. All rights reserved.

Enter the following information: Database unique name: emdb Service name: emdb Listener ORACLE_HOME [ /u01/app/11.2.0/grid ]: ---------------------------------------------------------------------WARNING : While repository is dropped the database will be put in quiesce mode. ---------------------------------------------------------------------Do you wish to continue? [yes(Y)/no(N)]: y Nov 29, 2011 2:40:16 PM oracle.sysman.emcp.EMConfig perform INFO: This operation is being logged at /u01/app/oracle/cfgtoollogs/emca/emdb/emca_2011_11_29_14_39_59.log. Nov 29, 2011 2:40:22 PM oracle.sysman.emcp.util.DBControlUtil stopOMS INFO: Stopping Database Control (this may take a while) ... Nov 29, 2011 2:40:53 PM oracle.sysman.emcp.EMReposConfig invoke INFO: Dropping the EM repository (this may take a while) ... Nov 29, 2011 2:47:31 PM oracle.sysman.emcp.EMReposConfig invoke INFO: Repository successfully dropped Enterprise Manager configuration completed successfully FINISHED EMCA at Nov 29, 2011 2:47:37 PM

Click 'Ok' after deconfiguration Click 'Test Connection'

Click 'Ok' after deconfiguration

A Configuration Details-Error pops-up.

Click Yes' to meet the requirement.

Configuration Details. You can click 'OK' now to ignore the warnings, and remember to make the change, or login to the database and make the changes then retry this step again.

Review. Click 'Install' to start the installation. This will run for a few minutes, and then you will be prompted to run root.sh

Execute root.sh

Create the localbin directory under the Middleware home. binaries cd /u02/Middleware; mkdir localbin

Run following command as the root user to create a dir for

[root@slcac452-x0 Middleware]# /u02/Middleware/oms/allroot.sh

Starting to execute allroot.sh ......... Starting to execute /u02/Middleware/oms/root.sh ...... Running Oracle 11g root.sh script... The following environment variables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /u02/Middleware/oms

Enter the full pathname of the local bin directory: [/usr/local/bin]: /u02/Middleware/localbin Copying dbhome to /u02/Middleware/localbin ... Copying oraenv to /u02/Middleware/localbin ... Copying coraenv to /u02/Middleware/localbin ...

Entries will be added to the /etc/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root.sh script. Now product-specific root actions will be performed. /etc exist Creating /etc/oragchomelist file... /u02/Middleware/oms Finished execution of /u02/Middleware/oms/root.sh ...... Starting to execute /u02/Middleware/agent/core/12.1.0.1.0/root.sh ...... Finished product-specific root actions. /etc exist Finished execution of /u02/Middleware/agent/core/12.1.0.1.0/root.sh ......

Finish the installation

Login to Enterprise Manager Cloud Control

Management Agent Deployment

A management agent will be installed by default on the first ODA node, where the OMS was installed. If the OMS was installed on another machine, then we must install an agent on each of the ODA cluster nodes. The following slides illustrate how to install a Management Agent on the second cluster node. 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: a. Accept the default name assigned for this session or enter a unique name of your choice.
b. Click Add to enter the fully qualified name of another ODA node(eg: slcac453-x0) and select the platform of the host on which

you want to install the Management Agent. following screen).

(If the OMS was installed on a different machine, provide both ODA hosts in the

c. Click Next. On the ODA cluster node, create the agent home directory and configure sudo related files. [root@slcac453-x0 /]#

mkdir -p /u02/agenthome chmod -R 777 /u02 chown -R oracle:oinstall /u02/agenthome cd /usr/local/bin ln -s /usr/bin/sudo sudo echo "oracle ALL=(ALL) ALL" >> /etc/sudoers requiretty echo "Defaults visiblepw" >> /etc/sudoers Uncomment this line in /etc/sudoers #Defaults
agent installation completes. Note: If you dont want to configure sudo for the oracle user, then remember to run root.sh manually immediately after

3. On the Installation Details page, do the following: a. In the Deployment Type section, select Fresh Agent Install. b. From the table, select the first row that indicates the hosts grouped by their common platform name. c. In the Installation Details section, provide the installation details common to the hosts selected in Step 3 (b). For Installation

Base Directory, enter the absolute path to the base directory where you want the software binaries, security files, and inventory files of Management Agent to be copied. eg: /u02/agenthome
d. For Instance Directory, accept the default instance directory location or enter the absolute path to a directory of your choice

where all Management Agent-related configuration files can be stored. eg: /u02/agenthome/agent_inst
e. 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.

f. For Privileged Delegation Setting, we leave this field blank, the root scripts will not be run by the wizard; you will have to run

them manually after the installation.

g. 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 be free. If you are not sure, you can leave this field blank. Enterprise Manager Cloud Control automatically assigns the first available free port within the range of 1830 - 1849.

h. Click Next. On the Review page, review then start the deployment Please review the details you have provided for the installation and if you are satisfied with the details, then click Deploy Agent to install the Management Agent.

Click Deploy Agent and wait for the OMA deployment to finish.

You are now ready for cluster-wide discovery of targets. Continue with the next section.

Cluster Discovery and configuration

Once the agent is deployed on both ODA cluster nodes, we need to deploy the target specific Plug-Ins from the console to each agent so that we can discover the various ODA targets. The following screen shots illustrate how to perform Plug-In deployment and target discovery. Navigate to the Setup link: Setup Extensibility Plug-ins Databases Oracle Database Deploy On

Management Agent

Add Select ODA nodes: slcac452-x0 & slcac453-x0

Select

Continue

Next

Deploy

Show Status

Note: Ensure that the Plug-In is deployed to both nodes successfully. Otherwise, perform the above steps for the second node.

Next, add Oracle Clusterware and HA Service. Navigate to: SetupAdd targetsAdd target manually

Add using Guided Discovery

Continue

Add

At this point, EM has created the top level target Cluster that will be used to discover associated cluster services. Next, we will add these targets (Oracle Database, Listener and Automatic Storage Management) to the ODA cluster the same way we added the cluster above.

Add using Guided Discovery

Continue

Continue

Cluster Database Configure

Provide the dbsnmp password Test Connection Next

OK Cluster ASM Configure

Test Connection OK

Next

Next

Save

OK This concludes the installation and configuration of Oracle Enterprise Manager Cloud Control 12c on ODA. For more information on EM, please refer to the EM Documentation on OTN.

Complete Documentation for Oracle Enterprise Manager

EM 10g 12c Documentation: http://www.oracle.com/technetwork/oem/grid-control/documentation/index.html EM 12c Installation Guide: http://download.oracle.com/docs/cd/E24628_01/install.121/e22624/toc.htm