Issues Concerning ODI 11g Standalone Agent, the startscen Script and the J2EE Agent
(Doc ID 1288663.1)
Last updated on NOVEMBER 13, 2023
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
In Oracle Data Integrator (ODI) 11g, jobs can be launched with either:
- The Standalone Agent,
- startscen, and
- A new type of Agent called ODI 11g Java EE Agent, JEE Agent or J2EE Agent.
All of the above need to be able to connect to the ODI Repositories to retrieve code/jobs to run.
Freezing that occurs when viewing Agent schedule, testing Agent, or launching jobs with the Agent is usually due to the Agent can not connect to the Repositories.
Freezing that occurs when viewing Agent schedule, testing Agent, or launching jobs with the Agent is usually due to the Agent can not connect to the Repositories.
- If startscen and a Standalone Agent, check the odiparams file to make sure the connection information is all accurate.
- If J2EE Agent check the Data Sources on WLS.
This document will answer some of the common questions and describe some issues end users may experienced when using these tools in ODI 11g.
Detailed information about managing ODI Agent is available from ODI Studio Help > Managing Agents.
NOTE: Please consult Document 423746.1 for the command and parameters required for starting the Standalone Agent and startscen scipt.
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 |
| Standalone Agent |
| 2. 'ODI-1424: Agent host or port cannot be reached' error when testing a Agent. |
| 3. ODI standalone Agent starts successfully but when testing connection or stopping the Agent... |
| 4. After creating a schedule for a scenario and run Update Schedule in the Agent, the View Schedule screen in the Agent is empty and the scheduled scenario never runs. |
| 5. New ODI standalone Agent starts successfully but Interfaces are aborting |
| 6. An existent Standalone Agent is running for DEV env, now need to create an Agent for a PROD Master Repository. |
| 7. After starting a Standalone Agent, it can be accessed by the URLhttp://<HOSTNAME>:<PORT>/oraclediagent , but can not be accessed (HTTP 404 error) with the URL http://<HOSTNAME>:<PORT>/dev_agent (Note: This example assumes the standalone agent name is dev_agent). |
| 8. 'java.net.MalformedURLException: Bad host' when starting the Standalone Agent. |
| 10. After having upgraded Oracle Data Integrator (ODI) from version 11.1.1.3 .0 to 11.1.1.5.0, the ODI Standalone Agent fails starting, and following message is signaled: |
| 11. The following error occurs when trying to start a Standalone Agent configured with external authentication (cwallet.sso and jps-config.xml): |
| 12. ODI-1266: Agent <AGENT_NAME> detected Session as Stale session and set to error status. |
| 13 How to enable and configure ODI 11g (11.1.1.5.0) Standalone agent with SSL (HTTPS)? |
| 14. The following error occurs when trying to send HTTPS to an external webservice through a proxy using the OdiInvokeWebSerice tool with a Standalone Agent. |
| 15 . <Note: 1608859.1> Setting Up External Authentication For ODI Standalone Agent. |
| Startscen |
| 16. Agent is running, but scenario is not getting executed using startscen tool: |
| 18. Launching ODI Scenarios from the startscen, startcmd scripts or OdiStartScen step |
| ODI J2EE Agent |
| 19. Configuring Datasources related to third-party JDBC Drivers |
| 20. Deploying and Configuring the ODI 11g Agent as a Java EE Application |
| 21. Executing an ODI Scenario on a J2EE Agent, ODI Operator always indicates that the Scenario is running on another J2EEAgent. |
| 22. Cohabiting ODI JEE Agents with OSB and SOA Suite Servers. Are there any issues cohabiting ODI, OSB and SOA under the same Weblogic Domain ? |
| 23. Can ODI Share the Weblogic Binaries Laid down by Hyperion Installer or we have to install separate Weblogic home for ODI? Environment: 11.1.2.2 and ODI console web 11.1.1.6 |
| 26. "Can't connect to agent" error when retrieving schedule for a Work Repository. |
| 27. <Note: 1488883.1> How To Launch An ODI 11g Scenario On An ODI JEE Agent Using Web Service Protocols |
| 28. <Note: 1479801.1> How To Update The ODI 11g JEE Agent When The Password Of The ODI Repositories Has Been Modified ? |
| 29. <Note: 1495715.1> 'java.net.SocketException: No buffer space available' Message Signalled When Attempting To Launch ODI 11g JEE Agent |
| 30. <Note: 1475337.1> ODI 11g Repository Connections Accumulate When Using JEE Agent And Pooled Connections Set Up With Oracle OCI Drivers |
| 31. <Note: 1458542.1> ODI-3276: No valid repository alias is found' Signaled When Connecting To a Repository From ODI Console After Launching The Weblogic ODI JEE Agent As a Windows Service |
| 32. Jobs run with ODI JEE Agent fails finding Data Source with javax.naming.NameNotFoundException. |
| 33. ODI-1425: Agent application cannot be reached using http://<HOSTNAME>:<PORT>/oraclediagent. |
| 34. ODI-1400: Agent OracleDIAgent start failure: JDBC connection error occurs while connecting to the master repository. Caused by: access denied....... |
| ODI Agents On High Availability Configurations |
| Please see: |
| <Note: 424105.1> Setting Up ODI Agents On High Availability Configurations |
| <Note: 1487102.1> How To Create And Deploy a High Availability ODI 11g Java EE Agent To a Cluster on WebLogic Server |
| <Note: 1460643.1> Is It Necessary To Define Multiple Distinct ODI JEE Physical Agent Entries In ODI Studio > Topology Navigator When Using WebLogic Server Load Balancing ? |
| References |