Exadata X3-2 Hardware
 
Exalogic Elastic Cloud X3-2 Hardware
 
Enterprise Manager for Exadata
 
Exadata Database Machine X2-2 Hardware
 
Enterprise Manager Base Platform
 
Exadata Database Machine X2-8
 
Exadata X3-2 Hardware
 
Oracle Exadata Hardware
 
Exalytics In-Memory Machine X2-4
 
Exadata X3-8 Hardware
 
Exadata Database Machine X2-2 Hardware
 
Oracle Exalogic Elastic Cloud X2-2 Hardware
 
Exadata Database Machine V2
 
Exalytics In-Memory Machine X3-4
 

PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Exadata>DB: Exadata_EST
 

Various metrics in the 'Sensors' collection, for example the 'FanSpeedSensors' metric, do not have Execution descriptors defined when the
MetricSource dynamic property is 'direct'.
  - Targets with MetricSource 'direct' use PushDescriptors
  - Targets with MetricSource 'opscenter' use ExecutionDescriptors

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-7582031331>

Applies to:

Symptoms

You will see warning messages for the ibswitch in the Enterprise Manager under Monitoring ==>> Metrics Issues you will see the Oracle Infiniband Switch reporting errors on the Metrics for:

FanSpeedSensors
AggregateSensors
VoltageSensors
TemperatureSensors

If you check the gcagent.log, usually under <AGENT_INST>/sysman/log directory,  you will see messages as follows in the agent log gcagent.log:

 The switch name - dm01sw-iba0.oracle.com - will reflect your environment.

Cause

This is due to unpublished Bug 14362799 - SENSOR METRICS BEING COLLECTED IN DIRECT MODE LEADING TO ERROR.

Metrics can be collected in different ways, direct and opscenter, in some cases for the direct collection method, we do not find the execution descriptor triggering the error

"Can't get query descriptor or execution descriptor"

Solution

There is no known workaround for this issue.

The fix for this is included in the 12.1.0.4 Exadata Plugin. To get this latest Exadata Plugin the EM Base version (OMS) must be at least 12.1.0.3.

References

This solution has no attachment