Sunday 1 January 2017

Install EM Agent On Exadata Using Oracle Enterprise Manager 13c

Overview

Oracle Exadata Database Machine consists of several components such as Compute nodes, Storage Cells, ILOM, Infiniband Switches, Cisco Switch and PDUs. So we need a tool that can manage all these components from one single console. Oracle Enterprise manager Cloud Control is the recommended best practices for monitoring and managing Exadata Database machine. Once the Exadata database Machine is installed the next step is enable monitoring for it.

The following Exadata components can be monitored and managed by OEM:
  • Compute Nodes
  • Storage Cells
  • Infiniband Switches
  • Cisco Switches
  • Power Distribution Units
  • KVM

The first step in monitoring and managing Exadata using OEM is to install the EM Agent. You can install EM Agent in several ways, such as:
  • Using EM Kit Method
  • Using the Agent push method
  • Using an RPM file
  • Using the AgentPull script
  • Using the AgentDeploy script

In this article we will demonstrate how to Install EM Agent on Exadata using Agent Push method using OEM 13c. Agent Software is installed only on Compute nodes.

Environment Details

Here we will be installing EM Agent on a Exadata V2 Full Rack consists of:
  • 8 Compute Nodes
  • 14 Storage Cells
  • 3 Infiniband Switches
  • 1 Cisco Switches
  • 2 Power Distribution Units
  • 1 KVM

Procedure to Install EM Agent on Exadata Compute nodes

Enter the OEM 13c URL into the web browser and hit enter

Enter the SYSMAN Credentials or any other user that have necessary permissions to Install Agent software

We are on the OEM 13c Home page now

From the Home page, click on Setup à Add Target à Add Targets manually

Click on Install Agent on Host

On this page, click on the +Add button to add the Host targets

Enter all fully qualified Hostnames (8 compute nodes) and for Platform “Same for All Hosts” and click next

Enter the Installation Base Directory.
The instance base directory will be populated automatically for you.
Click on the + symbol on the Named credentials and enter oracle user and its password.
Click on the + symbol on the Root credentials line and enter root user and its password.




Click next

Click Deploy Agent

The Agent Installation process started

Initialization in progress

The Remote prerequisite check shows warning. This can be ignored as oracle user doesn’t have sudo permissions to run the root.sh script. The can be ran at the end.

Click Continue à Continue, All Hosts

Installation process completed. Click Done.

Connect to Exadata compute node 1 and run the root.sh script as follows:

[root@dm01db01 ~]# dcli -g dbs_group -l root '/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0/root.sh'
dm01db01: Finished product-specific root actions.
dm01db01: /etc exist
dm01db02: Finished product-specific root actions.
dm01db02: /etc exist
dm01db03: Finished product-specific root actions.
dm01db03: /etc exist
dm01db04: Finished product-specific root actions.
dm01db04: /etc exist
dm01db05: Finished product-specific root actions.
dm01db05: /etc exist
dm01db06: Finished product-specific root actions.
dm01db06: /etc exist
dm01db07: Finished product-specific root actions.
dm01db07: /etc exist
dm01db08: Finished product-specific root actions.
dm01db08: /etc exist

Verify Agent is running on Exadata compute nodes.

dm01db01-orcl1 {/home/oracle}:/u01/app/oracle/product/Agent13c/agent_inst/bin/emctl status agent
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version          : 13.2.0.0.0
OMS Version            : 13.2.0.0.0
Protocol Version       : 12.1.0.1.0
Agent Home             : /u01/app/oracle/product/Agent13c/agent_inst
Agent Log Directory    : /u01/app/oracle/product/Agent13c/agent_inst/sysman/log
Agent Binaries         : /u01/app/oracle/product/Agent13c/agent_13.2.0.0.0
Core JAR Location      : /u01/app/oracle/product/Agent13c/agent_13.2.0.0.0/jlib
Agent Process ID       : 4544
Parent Process ID      : 4424
Agent URL              : https://dm01db01.int.thomsonreuters.com:3872/emd/main/
Local Agent URL in NAT : https://dm01db01.int.thomsonreuters.com:3872/emd/main/
Repository URL         : https://oem13c.domain.com:1159/empbs/upload
Started at             : 2016-12-29 04:40:07
Started by user        : oracle
Operating System       : Linux version 2.6.39-400.248.3.el6uek.x86_64 (amd64)
Number of Targets      : 3
Last Reload            : (none)
Last successful upload                       : 2016-12-29 04:44:54
Last attempted upload                        : 2016-12-29 04:44:54
Total Megabytes of XML files uploaded so far : 0.33
Number of XML files pending upload           : 0
Size of XML files pending upload(MB)         : 0
Available disk space on upload filesystem    : 17.84%
Collection Status                            : Collections enabled
Heartbeat Status                             : Ok
Last attempted heartbeat to OMS              : 2016-12-29 04:47:11
Last successful heartbeat to OMS             : 2016-12-29 04:47:11
Next scheduled heartbeat to OMS              : 2016-12-29 04:48:12

---------------------------------------------------------------
Agent is Running and Ready

Verify that Exadata computes are visible in OEM 13c


Next we will discover Exadata Database Machine in OEM 13c


6 comments:

  1. Hi All article looks good. Is it possible to clear my doubts on exadata

    ReplyDelete
  2. Please write to me at abdul.mohammed@netsoftmate.com

    ReplyDelete
  3. Nice article. Am new in exadata stuff. How do we achieve the same thing where the compute nodes have been used as Virtual Hosts?

    ReplyDelete
  4. This is such a great resource that you are providing and you give it away for free. I love seeing blog that understand the value of providing a quality resource for free. EM 2021

    ReplyDelete
  5. For an EM agent to communicate with ILOM SP, there must be a user created on ILOM SP, on all the Compute Nodes.

    ReplyDelete
  6. For an EM agent to communicate with ILOM SP, there must be a user created on ILOM SP, on all the Compute Nodes.

    ReplyDelete

Comparing Oracle Database Appliance X8-2 Model Family

September 2019 Oracle announced Oracle Database Appliance X8-2 (Small, Medium and HA). ODA X8-2 comes with more computing resources com...