1 person found this helpful
No, you would not need to create a separate agent for each work repository, as long as they are both attached to the same master repository. The agent is defined under the topology, which is stored in the master repository. Both repositories will be available to use the agent when started.
Thanks for your reply. Both WORKREP1 and WORKREP2 are under the same Master Repository, but there's a catch. When WORKREP2 was created, it was created in the Master schema, not a new Work Schema. Would that make a difference? Also, when we look at the odiparams.sh file, there is only one entry:
With the current configuration, we are able to:
1) Test agent - PASS
2) Run load plan manually - PASS
3) View Schedule (for WORKREP2) - FAILS (Error - Unable to connect to agent)
Please let me know if I am missing anything. Thanks,
So your repository architecture is something like this:
Schema Repository Master Master and WORKREP2 WORKREP1 WORKREP1
With WORKREP1 and WORKREP2 both available in the Topology under Repositories->Work Repositories?
When you start the agent, you should see something similar to the following, indicating that both repositories are available for use with the agent.
2014-05-21 17:22:49.583 NOTIFICATION ODI-1137 Scheduler started for work repository WORKREP1 on Agent ODI_AGENT.
2014-05-21 17:22:49.692 NOTIFICATION ODI-1137 Scheduler started for work repository WORKREP2 on Agent ODI_AGENT.
Also, when you update the schedule on the Agent, can you select both work repositories?
Yes, the table looks correct.
Yes, WORKREP1 and WORKREP2 are both available under Topology -> Work Repositories.
Unfortunately, we havent restarted the agent after the creation of WORKREP2, because of dependencies on other Projects. Do you think a restart of the agent might fix this issue?
Yes, when we update the schedule, we are able to select both repositories and update schedule.
Yes, I think a restart of the Agent would help, and may resolve the issue.
If you are using WORKREP2 in ODI then make sure that WORKREP2 should present in odiparams.sh as told by "Anirban Roy" once you done the changes in odiparams.sh run the agent and test the agent is up and running and my advice it is not necessory to create agent for each an every repository.
Changes steps: in odiparams
now you can change as below
Hope this may resolve your issue ?
I dont want to replace the WORKREP1 entry with WORKREP2 in the odiparams.sh. That will make WORKREP1 non-functional. I want both work reps to be available. Is there a way to assign both repositories (e.g. semi-colon or comma separated) to ODI_SECU_WORK_REP parameter in odiparams.sh file?
Thanks Michael, the restart seems to have resolved the issue. We are able to view the schedule now. Thanks for your help!