My Oracle Support Banner

Odi Standalone Agent Fails To Start (Doc ID 1591240.1)

Last updated on NOVEMBER 24, 2020

Applies to:

Oracle Knowledge - Version 8.5.1 and later
Information in this document applies to any platform.
There are several reasons why the ODI standalone agent might not start.
The first step is to check the agent properties in the ODI adminstrator.
Next is to check that the ODIparams file and the information in the ODI client are consistent.

Symptoms

When executing "agent.sh -port=20910"  the following exception is thrown:

[2013-09-30T10:02:33.978-04:00] [] [NOTIFICATION] [ODI-1128] [] [tid: 10] [ecid: 0000K5jBNd4AlJd_xd0FyW1IIOHs000001,0] Agent OracleDIAgent is starting. Application Server: STANDALONE. Agent Version: 11.1.1.6.0 - 19/12/2011. Port: 20910. JMX Port: 21910.
[2013-09-30T10:02:37.843-04:00] [] [ERROR] [ODI-1131] [] [tid: 10] [ecid: 0000K5jBNd4AlJd_xd0FyW1IIOHs000001,0] Agent OracleDIAgent encountered an error: ODI-1405: Agent OracleDIAgent start failure: the agent is not defined in the topology for master repository.[[
ODI-1405: Agent OracleDIAgent start failure: the agent is not defined in the topology for master repository.
       at oracle.odi.runtime.agent.servlet.AgentServlet$1.doAction(AgentServlet.java:828)
       at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:186)
       at oracle.odi.runtime.agent.servlet.AgentServlet.getSnpAgentForAgentInstance(AgentServlet.java:820)
       at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:350)
       at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:239)
       at javax.servlet.GenericServlet.init(GenericServlet.java:241)
       at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431)
       at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
       at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
       at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:676)
       at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
       at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1239)
       at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
       at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:46

If the database connection string is missing then you will get

[2015-07-09T12:24:03.364-04:00] [] [ERROR] [ODI-1131] [] [tid: 10] [ecid: 0000KtncOelA1VVMy2U^MG1Lbe0Z000001,0] Agent OracleDIAgent encountered an error: ODI-1400: Agent OracleDIAgent start failure: JDBC connection error occurs while connecting to the master repository. Caused by: ODI-1441: Unable to connect to the master repository at JBDC URL=jdbc:weblogic:sqlserver://<host>:<port> with USER=DEV_ODI_REPO.[[
ODI-1400: Agent OracleDIAgent start failure: JDBC connection error occurs while connecting to the master repository.
ODI-1441: Unable to connect to the master repository at JBDC URL=jdbc:weblogic:sqlserver://<host>:<port> with USER=DEV_ODI_REPO.
Caused By: java.sql.SQLException: Exception occurred while getting connection: oracle.ucp.UniversalConnectionPoolException: Cannot get Connection from Datasource: java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]Error establishing socket to host and port: <host>:<port>. Reason: Connection refused: connect
at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:488)
at oracle.ucp.util.UCPErrorHandler.throwSQLException(UCPErrorHandler.java:163)
at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:943)

If the agent physical to logical mapping is not correct you will see this errror.

oracle.odi.runtime.agent.invocation.InvocationException: ODI-1424: Agent host or port cannot be reached using http://localhost:20910/oraclediagent

If the ODIparams file has not been updated to reflect the correct database or user information then this error can happen.

[2018-01-29T02:42:22.063-05:00] [] [ERROR] [ODI-1444] [] [tid: 11] [ecid: 0000M4azT0B3f5zFk33V831QQ32N000001,0:112] The master repository signature specified by the client 1461068612022|1 does not match the master repository signature of the agent 1417216262794|711.
[2018-01-29T02:42:22.066-05:00] [odi] [ERROR] [] [oracle.odi.agent] [tid: 11] [ecid: 0000M4azT0B3f5zFk33V831QQ32N000001,0:112] ODI-1444: The master repository signature specified by the client 1461068612022|1 does not match the master repository signature of the agent 1417216262794|711.[[
at oracle.odi.runtime.agent.servlet.AgentServlet.processRequest(AgentServlet.java:557)
at oracle.odi.runtime.agent.servlet.AgentServlet.doPost(AgentServlet.java:516)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

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


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