EM: Database Target Is Showing Metric Collection Error Target Is Skipping Collections Because Host Is Unreachable
(Doc ID 3076863.1)
Last updated on MARCH 14, 2025
Applies to:
Enterprise Manager Base Platform - Version 13.4.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
Database target is UP and Running but showing the following metric collection error in the EM console
oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: Skipping collections because host is unreachable
oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: Skipping collections because host is unreachable
at oracle.sysman.gcagent.metadata.impl.collection.CollectionItem$CollectionItemTask.preExecuteCheck(CollectionItem.java:2648)
at oracle.sysman.gcagent.task.AbstractTemplateTask.call(AbstractTemplateTask.java:269)
at oracle.sysman.gcagent.task.AbstractTemplateTask.call(AbstractTemplateTask.java:56)
at oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler$ReschedulingHelper$ReschedulingTask.call(DispatchingTaskScheduler.java:668)
at oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler$ReschedulingHelper$ReschedulingTask.call(DispatchingTaskScheduler.java:609)
at oracle.sysman.gcagent.task.executor.DiagWrappedTask.call(DiagWrappedTask.java:60)
at oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.accountedCall(TaskFutureImpl.java:600)
at oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.call(TaskFutureImpl.java:644)
Getmetric shows database target as UP
Host target is showing UP only the database target is showing metric collection errors.
Cause
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
Symptoms |
Cause |
Solution |