FDMEE: ODI Agent Not Working After SSO (OAM) Configured
(Doc ID 2202050.1)
Last updated on NOVEMBER 02, 2022
Applies to:
Hyperion Financial Data Quality Management, Enterprise Edition - Version 11.1.2.4.000 to 11.1.2.4.200 [Release 11.1]Information in this document applies to any platform.
Symptoms
ODI agent (FDMEE) not working due to OAM redirect
Errors similar:
[2016-08-10T05:39:20.015-05:00] [ErpIntegrator0] [WARNING] [] [oracle.odi.agent.scheduler] [tid: 16] [userId: <anonymous>] [ecid: bd0de272630c49c7:70062928:15668b07e20:-8000-0000000000000002,1:24657] [APP: oraclediagent] Agent is not reachable. Going to retry after inteval :30000
[2016-08-10T05:39:50.023-05:00] [ErpIntegrator0] [WARNING] [] [oracle.odi.agent.scheduler] [tid: 16] [userId: <anonymous>] [ecid: bd0de272630c49c7:70062928:15668b07e20:-8000-0000000000000002,1:24657] [APP: oraclediagent] agent.scheduler.pingAgent.failed[[
oracle.odi.runtime.agent.invocation.InvocationException: HTTP/1.1 302 Found
at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invoke(RemoteRuntimeAgentInvoker.java:253)
at oracle.odi.runtime.agent.scheduler.AgentScheduleManager.pingAgent(AgentScheduleManager.java:198)
at oracle.odi.runtime.agent.scheduler.AgentScheduleManager.access$4(AgentScheduleManager.java:193)
at oracle.odi.runtime.agent.scheduler.AgentScheduleManager$1.run(AgentScheduleManager.java:120)
at java.lang.Thread.run(Thread.java:662)
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 |
| References |