Monitoring the System Using EM Exadata Plug-in
System Requirements
Only systems with software Version 1.1 (or later) with Database Domain on Control LDOM-
only environments are supported. Earlier versions of the system can be made compatible if you
update to the October 2012 QMU release. You can confirm this requirement by looking at the
version of the
compmon pkg
installed on the system (using either
pkg info compmon
or
pkg
list compmon
commands to check). You must have the following minimum version of
compmon
installed:
pkg://exa-family/system/platform/exadata/compmon@0.5.11,5.11-0.1.0.11:
20120726T024158Z
Note -
With the Oracle SuperCluster software version 2.x, the
compmon
command name changed
to
osc-compmon
. Use the new name if SuperCluster is installed with the Oracle SuperCluster
v2.x release bundle. See
“Identify the Version of SuperCluster Software” on page 145
.
Known Issues With EM Exadata Plug-in
■
The pre-requisite check script
exadataDiscoveryPreCheck.pl
that is bundled in
Exadata plug-in 12.1.0.3 does not support the
catalog.xml
file. Download the latest
exadataDiscoveryPreCheck.pl
file from My Oracle Support as described in the
“Discovery Precheck Script” section of the
Oracle Enterprise Manager Exadata Management Getting Started Guide (
oracle.com/cd/E24628_01/doc.121/e27442/title.htm
■
If multiple database clusters share the same Exadata Storage server, in one Enterprise
Manager management server environment, you can discover and monitor the first DB
Machine target and all its components. However, for additional DB Machine targets sharing
the same Exadata Storage server, the Oracle Exadata Storage Server Grid system and the
Oracle Database Exadata Storage Server System will have no Exadata Storage server
members because they are already monitored.
■
If the
perfquery
command installed in the system has version 1.5.8 or later, you will
encounter a bug (ID 15919339) where most columns in the HCA Port Errors metric in the
host targets for the compute nodes will be blank. If there are errors occurring on the HCA
ports, it will not be reported in Enterprise Manager.
To check your version, run the following command:
perfquery -V
Monitoring the System
227
Summary of Contents for SuperCluster T5-8
Page 1: ...Oracle SuperCluster T5 8 Owner s Guide Part No E40167 17 May 2016 ...
Page 2: ......
Page 11: ...Contents Index 353 11 ...
Page 12: ...12 Oracle SuperCluster T5 8 Owner s Guide May 2016 ...
Page 14: ...14 Oracle SuperCluster T5 8 Owner s Guide May 2016 ...
Page 116: ...116 Oracle SuperCluster T5 8 Owner s Guide May 2016 ...
Page 204: ...204 Oracle SuperCluster T5 8 Owner s Guide May 2016 ...
Page 228: ...228 Oracle SuperCluster T5 8 Owner s Guide May 2016 ...
Page 244: ...244 Oracle SuperCluster T5 8 Owner s Guide May 2016 ...