My Oracle Support Banner

ODI Error "IllegalArgumentException: pSecurityConn doesn't refer to any Master repository" Received when Attempting to Run Job (Doc ID 2448360.1)

Last updated on FEBRUARY 20, 2019

Applies to:

Oracle Data Integrator - Version 11.1.1.6.0 to 12.1.3.0.1 [Release 11gR1 to 12c]
Information in this document applies to any platform.

Symptoms

When attempting to run jobs with the standalone agent in Oracle Data Integrator (ODI), the following error occurs:

ODI-1217: Session <SESSION_NAME> (<ID>) fails with return code 7000.
Caused By: java.lang.IllegalArgumentException: pSecurityConn doesn't refer to any Master repository
   at com.sunopsis.security.DefaultDwgSecurityManager.getDefaultSecurityManager(DefaultDwgSecurityManager.java:241)
   at oracle.odi.core.security.SecurityManager.createDwgSecurityManager(SecurityManager.java:282)
   at oracle.odi.core.security.SecurityManager.createAuthentication(SecurityManager.java:1692)
   at oracle.odi.core.security.SecurityManager.createAuthentication(SecurityManager.java:1600)
   at oracle.odi.runtime.agent.execution.SessionExecutor.createAuthentication(SessionExecutor.java:4626)
   at oracle.odi.runtime.agent.execution.SessionExecutor.executeSession(SessionExecutor.java:552)
   at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor$1.doAction(TaskExecutorAgentRequestProcessor.java:718)
   at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor$1.doAction(TaskExecutorAgentRequestProcessor.java:611)
   at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:203)
   at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doProcessStartAgentTask(TaskExecutorAgentRequestProcessor.java:800)
   at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.access$2700(StartScenRequestProcessor.java:85)
   at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:917)
   at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:180)
   at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$1.run(DefaultAgentTaskExecutor.java:66)
   at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:48)
   at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor.executeAgentTask(DefaultAgentTaskExecutor.java:76)
   at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doExecuteAgentTask(TaskExecutorAgentRequestProcessor.java:146)
   at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.process(TaskExecutorAgentRequestProcessor.java:137)
   at oracle.odi.runtime.agent.support.DefaultRuntimeAgent.execute(DefaultRuntimeAgent.java:79)
   at oracle.odi.pubws.jaxws.service.OdiInvokeServiceImpl.doInvokeStartScen(OdiInvokeServiceImpl.java:420)
   at oracle.odi.pubws.jaxws.service.OdiInvokeServiceImpl.invokeStartScen(OdiInvokeServiceImpl.java:366)
   at sun.reflect.GeneratedMethodAccessor274.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
   at java.lang.reflect.Method.invoke(Method.java:508)
   ...

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
 A. Apply Patch
 B. Enable Keep-Alive
References


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