Good Contents Are Everywhere, But Here, We Deliver The Best of The Best.Please Hold on!
Overview
To manage and monitor Exadata Database Machine you must discover it in Oracle Enterprise Manager. Before you discover Exadata DBM you first Install EM Agent on all Exadata Compute nodes. The Guided Discovery Process of OEM helps you discover all the Exadata Components easily.

The following Exadata components can be monitored and managed by OEM:
  • Compute Nodes
  • Storage Cells
  • Infiniband Switches
  • Cisco Switches
  • Power Distribution Units
  • KVM
In this article I will demonstrate how to discover an Exadata Database Machine in OEM 13c. Discover Exadata in OEM 13c is no different than OEM 12c except couple of changes. The graphics part of the OEM 13c looks very coolJ

Before we starting with the Discovery process make sure that OEM 13c Agent is installed on Compute nodes. You can find the article to install EM Agent at:


Before you start make sure
  • OEM 13c server is Installed and Configured
  • OEM 13c Agent is installed on all Exadata Compute Nodes
  • SYSMAN User password
  • Oracle user password
  • Root user password for Compute nodes, Storage Cells and Infiniband Switches

Procedure to Discover Exadata Database Machine in OEM 13c

Enter the OEM 13c address in the web browser

Enter the SYSMAN user and password or any other user with admin privileges.

This is our OEM 13c home page

From the home, click Setup –> Add Target –> Add Targets Manually

Click on “Add Using Guided Process”

Select “Oracle Exadata Database Machine” and click Add button.

Select “Discover a new Database Machine and its hardware components and targets”, “13c target type with enhanced hardware monitoring, requiring additional credentials” and Click “Discover Targets”

On this page, search or enter the EM agent URL for compute node 1 and, Click Add buton and add the compute node 1 and enter the oracle user credentials.
Note: Make databasemachine.xml exist and Oracle user have necessary permissions to read it.




Select Compute node 1 and click select.

Click Next

On this page, enter the first Infiniband Switch name and root credentials and test connection. Click Next


Click Next

All the Exadata Components are Discovered and shown on this page. Click Next



This Page shows the Exadata Components monitored by different Agents. Click Next





On this page Enter the Credentials for Agent Host, Compute Node ILOM, Storage Cell, IB Switch, PDU, Cisco Switch and test connection for each of them. Click Next











Review the Summary Page and Click Next 




The Target Promotion in progress 

Click Done on the final page (Not shown here). Make sure no errors are reported.

Click Launch Database Machine will bring you to the following page 

This is the Photo realistic image of Exadata Database machine.

We have discovered Exadata Database Machine successfully in OEM 13c

Conclusion
In this article we have seen how to discover an Exadata Database Machine in Oracle Enterprise Manager 13c using simple Guided discovery process. Oracle Enterprise manager 13c considered ideal for managing and monitoring Exadata Database Machine.


0

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


4