oracle.odi.runtime.agent.invocation.InvocationException: ODI-1444: The master repository signature specified by the client does not match the master repository signature of the agent.
ODI-1444 errors as below seen when try to test ODi Agent from Topology Manager from ODI Studio and users cannot use ODi Java EE Agent.
oracle.odi.runtime.agent.invocation.InvocationException: ODI-1444: The master repository signature specified by the client 1374678394483|501 does not match the master repository signature of the agent 1374678394483|1.
at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invoke(RemoteRuntimeAgentInvoker.java:265)
at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invokeIsAlive(RemoteRuntimeAgentInvoker.java:428)
at oracle.odi.ui.action.SnpsPopupActionTestAgentHandler.actionPerformed(SnpsPopupActionTestAgentHandler.java:67)
Check below:
1) Compare ODI Master Repository connection detail between ODI Studio login and ODI Agent. They should be connecting as same DB username@the same database.
2) If they are using the same database connection detail but the same problem persists, it may be likely that ODI Repository might have just been renumbered, restored or cloned so the repository signature has been changed.
To overcome the issue, ODI Agent should be bounced so that you can logout and re-login to your ODI Studio and re-test the ODI Agent.
ODI-1444 errors as below seen when try to test ODi Agent from Topology Manager from ODI Studio and users cannot use ODi Java EE Agent.
at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invoke(RemoteRuntimeAgentInvoker.java:265)
at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invokeIsAlive(RemoteRuntimeAgentInvoker.java:428)
at oracle.odi.ui.action.SnpsPopupActionTestAgentHandler.actionPerformed(SnpsPopupActionTestAgentHandler.java:67)
Check below:
1) Compare ODI Master Repository connection detail between ODI Studio login and ODI Agent. They should be connecting as same DB username@the same database.
2) If they are using the same database connection detail but the same problem persists, it may be likely that ODI Repository might have just been renumbered, restored or cloned so the repository signature has been changed.
To overcome the issue, ODI Agent should be bounced so that you can logout and re-login to your ODI Studio and re-test the ODI Agent.
Simply wish to say your article is as astonishing. The clarity in your post is simply great, and I could assume you are an expert on this subject. Same as your blog i found another one Oracle ODI 12c .Actually I was looking for the same information on internet for Oracle ODI 11g and came across your blog. I am impressed by the information that you have on this blog. Thanks a million and please keep up the gratifying work.
ReplyDelete