Master Note for the Configuration and Use of OPMN to Start, Stop and Monitor ODI 11g Standalone Agents
(Doc ID 1274484.1)
Last updated on OCTOBER 10, 2019
Applies to:
Oracle Data Integrator - Version 11.1.1.3.0 to 11.1.1.9.99 [Release 11gR1]Information in this document applies to any platform.
Purpose
This document is intended to show Oracle Data Integrator users:
- How to add an ODI 11g standalone Agent to Oracle Process Management Notification (OPMN),
- What are the prerequisites
- What are the issues that might occur, and how to resolve them.
Questions and Answers
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
| Purpose |
| Questions and Answers |
| Scope and Application |
| Prerequisites |
| 1. OPMN... |
| 3. ODI 11g standalone Agent |
| 4. Java considerations |
| 5. The "agentcreate.properties", and "odi_opmn_addagent.bat(.sh)" files |
| How to add ODI 11g standalone Agent to OPMN? |
| How to stop ODI standalone Agent using OPMN? |
| How to delete ODI standalone Agent from OPMN? |
| Troubleshooting |
| 1. As stated above, if the ODI Agent fails to start, you may consult its log file located at C:\WEBTIER_HOME\Oracle_WT1\instances\instance1\diagnostics\logs\OPMN\console~<AGENT_NAME>~odiagent~1.log |
| 2. Hints for setting up the Agent using OPMN |
| 3. How to activate the trace in OPMN |
| 4. Unable to start the Agent using OPMN when the JDBC Url to ODI Repositories contains "//" |
| 5. Unable to start the ODI Agent using OPMN when the JDBC Url to ODI Repositories contains spaces |
| 6. OPMN shows the ODI Agent is alive but testing the Agent gives "ODI-1424: Agent host or port cannot be reached" error |
| 7. Time out message when stopping the ODI Agent through OPMNCTL STOPPROC |
| 8. java.lang.UnsatisfiedLinkError: oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I... |
| 9. For connecing to Oracle, we recommended to use a thin jdbc driver connection |
| 10. 'java.library.pathcom.hyperion.odi.hfm.wrapper.HFMException: no HFMDriver in java.library.path' error when running HFM jobs using ODI Standalone Agent started by OPMN |
| 11. 'com.hyperion.odi.common.ODIHAppException: com.hyperion.odi.common.ODIHAppException: Error loading resource string for code '120'. Error code: 1813 (x715)' error . |
| 12. Jobs fail with errors such as "driver not found", "'xxxxx' is not recognized as an internal or external command" etc when run by the ODI Agent started by OPMN |
| 13. For SQL*Loader/SQL*Plus, please see the following Note specifically for how to configure OPMN such that the ODI Agent can execute SQL*Loader/SQL*Plus |
| 14. Agent startup failure "ERROR ODI-1131 Agent ODI_AGENT encountered an error: ODI-1400: Agent ODI_AGENT start failure" |
| References |