My Oracle Support Banner

Targets Metric Collection Evaluation Extending Beyond Interval and Collection due to run again but is still running from last schedule (Doc ID 1302873.1)

Last updated on FEBRUARY 21, 2020

Applies to:

Enterprise Manager Base Platform - Version to [Release 10.2 to 11.1]
Information in this document applies to any platform.
Checked for relevance on 01-Jul-2014


AGENT_HOME/sysman/log/emagent.trc file reports following errors:

2011-01-09 01:44:11,874 Thread-3870870416 WARN scheduler: host:<hostname>:Load is due to run again but is still running from last schedule
2011-01-09 01:44:11,874 Thread-3870870416 WARN collector: schedule host:<hostname>:Load with 300 nil frequency is skipped 51 time
2011-01-09 01:44:12,319 Thread-3849816976 WARN collector: Metric{} Evaluation completed at 15740 seconds, collection interval = 300


WARN TimeKeeper: nmestk_runTimeKeeper: Timekeeper spent too much time updating process activity: elapsed=239 csec, sleep=-1390000

or receiving this alert in Cloud Control Console:

Agent communication to the OMS is fine and also agent uploads the files successfully to OMS.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.