"No value specified for mrExtId parameter - cannot fetch the Master Repository Noun" Signalled In The ODI 11g Agent log
(Doc ID 2197201.1)
Last updated on MARCH 07, 2017
Applies to:
Oracle Data Integrator - Version 11.1.1.3.0 to 11.1.1.9.0 [Release 11gR1]Information in this document applies to any platform.
Symptoms
When using an Oracle Data Integrator (ODI) 11g Agent, following message is occasionally reported in the agent log file:
[2016-10-19T07:26:49.068-06:00] [odi_server1] [TRACE] [] [oracle.odi.dms.DMSSensorManager] [tid: 461240] [userId: <anonymous>] [ecid: 0000LVT7rE17U8E5v7WByX1O1Ja200052J,1:47741] [APP: oraclediagent] [SRC_CLASS: oracle.odi.dms.DMSSensorManager] [SRC_METHOD: startAgentPhaseEventSensor] No value specified for mrExtId parameter - cannot fetch the Master Repository Noun[[
java.lang.Exception: No value specified for mrExtId parameter - cannot fetch the Master Repository Noun
at oracle.odi.dms.DMSSensorManager.getMasterRepoNoun(DMSSensorManager.java:315)
at oracle.odi.dms.DMSSensorManager.getAgentNoun(DMSSensorManager.java:369)
at oracle.odi.dms.DMSSensorManager.getAgentPhaseEventSensor(DMSSensorManager.java:564)
at oracle.odi.dms.DMSSensorManager.startAgentPhaseEventSensor(DMSSensorManager.java:250)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1916)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1898)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:583)
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:514)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1074)
at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:133)
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:84)
at java.lang.Thread.run(Thread.java:745)
]]
The executions however complete, and do not seem affected in any ways.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |