Changing SUPERVISOR user password in Oracle Data Integrator

Changing SUPERVISOR user password in Oracle Data Integrator

Below are the high level steps to change SUPERVISOR user password in Oracle Data Integrator.

- On the server running the ODI client, navigate to start -> All Programs -> Oracle -> Oracle Data Integrator -> ODI Studio

- Navigate on ODI Studio

Click on left pane ->   Connect to Repository -> pop up the Master Repository with 
Supervisor -> click on OK and go to

View -> ODI Security Navigator ->  click on users -> click on "Supervisor " -> on right pane click on "change password"


- On the server running the agent, browse to cd $ODI_HOME/oracledi/agent/bin

- Take the backup of the file odiparams.sh

- Run the command

./encode.sh  

- Copy the encoded password to odiparams.sh in the following location


 ODI_SUPERVISOR=SUPERVISOR
 ODI_SUPERVISOR_ENCODED_PASS=

- Restart services.

- Try logging in as SUPERISOR / new_password

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.

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.