EM 13C ERROR: Invalid username and/or <**> for Odba_Power_Metric - Could not extract PID from NMO
(Doc ID 3023516.1)
Last updated on JUNE 10, 2024
Applies to:
Enterprise Manager for Oracle Database - Version 13.1.0.0.0 and laterInformation in this document applies to any platform.
Goal
Following message is being recorded over and over again in the EM agent log file <AGENT_INST>/sysman/log/gcagent.log in the ODA systems:
------------------
2024-05-08 10:43:45,977 [21:B6EB453F] WARN - (2 occurrences)selectDispatchCoordinator selected : oracle.sysman.gcagent.dispatch.InlineDispatchCoordinator
2024-05-08 10:43:46,884 [288:DAFF52B0:GC.Executor.4 (<**>:<server>Odba_Power_Metric) (<**>:<server>:Odba_Power_Metric:Odba_Power_Metric)] INFO - PatternDetector filter scan disabled: reason=PATTERN_FOUND
2024-05-08 10:43:46,884 [288:DAFF52B0] WARN - Could not extract PID from NMO
2024-05-08 10:43:46,884 [288:DAFF52B0] INFO - PatternDetector filter scan disabled: reason=REQUEST
2024-05-08 10:43:46,889 [288:DAFF52B0] WARN - In ResponseHandler.reportError, see ERROR: Invalid username and/or <**> for Odba_Power_Metric
oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: ERROR: Invalid username and/or <**>
at oracle.sysman.gcagent.addon.fetchlet.osfetchlet.BaseOSFetchlet.getOSMetric(BaseOSFetchlet.java:1078)
at oracle.sysman.gcagent.addon.fetchlet.osfetchlet.BaseOSFetchlet.getMetric(BaseOSFetchlet.java:478)
.
Solution
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
Goal |
Solution |
References |