Invalid 'Count of Targets Not Uploading Exceeded the Critical Threshold' Alerts are Raised for Agent

Invalid 'Count of Targets Not Uploading Exceeded the Critical Threshold' Alerts are Raised for Agent Target [ID 1359328.1]

修改时间:2012-6-16类型:PROBLEM状态:PUBLISHED优先级:3 注释 (0)

In this Document

Symptoms

Cause

Solution

References

--------------------------------------------------------------------------------

Applies to:

Enterprise Manager Base Platform - Version 11.1.0.1 to 11.1.0.1 [Release 11.1]

Information in this document applies to any platform.

Symptoms

1) The 11g Grid Control Metric "Count of targets not uploading data" keeps alerting at 'critical' status, even though the agent is uploading data ok. The following are examples of the metric alert:-

"Count of targets not uploading exceeded the critical threshold (0). Current value: 1"

"Count of targets not uploading exceeds critical threshold"

2) The emdiag kit repvfy command "repvfy verify -level 9 -detail" returns "132. Targets not uploading any data"

3) Additionally: The result of the following query in the repository database (as user 'sysman') may return negative values:-

SELECT host_url, value

FROM mgmt_oms_parameters

WHERE name = 'loaderOldestFile';4) However, it can be seen in the Grid Control console, that the agent is uploading correctly. To check this:-

Click on host target home page <for host where agent which received the alert is running>/click "all metrics" from related links and look at "last upload"

Click on the host home page <for host where agent which received the alert is running>/click on "targets", view "last load time" for each target

Check the "last successful upload" time of the agent

To check the "last successful upload" time of the agent:

cd $ORACLE_HOME<ofagent>/bin

./emctl status agent

Cause

Unpublished Bug:12612391 "ALERTS FROM EMGC-COUNT OF TARGETS NOT UPLOADING EXCEEDED THE CRITICAL THRESHOLD". This bug can be encountered if the repository database is 11.2 or higher. It is caused by the fact that the database Advanced Queueing time zone was
changed to be UTC by default from 11.2 rdbms onwards.

Solution

Apply the relevant patch to the Grid Control OMS home. Note that these patches need to be applied ontop of the PSU patch

Patch:12868397 on OMS 11.1.0.1.4 see Note:1330064.1 for information on the 11.1.0.1.4 PSU patch

Patch:13094414 on OMS 11.1.0.1.5 see Note:1364215.1 for information on the 11.1.0.1.5 PSU patch

Patch:13589211 on OMS 11.1.0.1.6 see Note:1388812.1 for information on the 11.1.0.1.6 PSU patch

Patch:13957656 on OMS 11.1.0.1.7 see Note:1446550.1 for information on the 11.1.0.1.7 PSU patch

Alternatively the following workaround can be used if it is not feasible to apply the patch straight away:-

1. shutdown the repository database

2. shutdown the repository database listener

3. export TZ=UTC

4. start the repository database whilst the $TZ environmental variable is set to UTC

5. start the repository database listener whilst the $TZ environmental variable is set to UTC

References

NOTE:1364215.1 - 11.1.0.1.5 Enterprise Manager Base Platform Patch Set Update (PSU)

NOTE:1446550.1 - 11.1.0.1.7 Enterprise Manager Base Platform Patch Set Update (PSU)

NOTE:1388812.1 - 11.1.0.1.6 Enterprise Manager Base Platform Patch Set Update (PSU)

@ BUG:12612391 - ALERTS FROM EMGC-COUNT OF TARGETS NOT UPLOADING EXCEEDED THE CRITICAL THRESHOLD

NOTE:1330064.1 - 11.1.0.1.4 Grid Control Patch Set Update (PSU)