My Oracle Support Banner

"Unable to retrieve agent's schedule, Unable to Connect To Agent" Messages, Or No Schedule Displays, Or Update/View Schedule Hangs When Viewing Schedules in ODI (Doc ID 458756.1)

Last updated on NOVEMBER 10, 2018

Applies to:

Oracle Data Integrator - Version 10.1.3.2.0 and later
Information in this document applies to any platform.
***Checked for relevance on 15-11-2013***

Symptoms

When attempting to view the scheduling information of an Oracle Data Integrator (ODI) 10g Scheduler Agent Or ODI 11g Standalone Agent in Topology Manager or Operator, the following warning message is displayed:

Unable to retrieve agent's schedule
Or:  
Or: sometimes the screen simply hangs. 
Or: Same job scheduled for Standalone Agent also appears when viewing the J2EE Agent's Schedule and the job gets executed twice.
Or Agent tests successful but the schedules simply will not show up.

Changes

 

Cause

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
Symptoms
Changes
Cause
 Case 1. There is nothing scheduled in the time frame for that ODI Agent
 Case 2. The ODI Agent is not able to connect to Master Repository or not connected to the right Work Repository.
 Case 3. Scenarios or Load Plans have been renamed or have invalid schedules.           
 Case 4.  May be an issue with the Java version used by the Agent.
 Case 5. Agent is having trouble to connect to the Work Repository. In this case, the Update Schedule or View schedule Window usually hangs.
 Case 6. The Standalone Agent's Physical Agent name is the default name, OracleDIAgent for J2EE Agent and the J2EE Agent is deployed using the default template. 
Solution
 Case 1. There is nothing scheduled in the time frame for that ODI Agent
 Case 2. The ODI Agent is not able to connect to Master Repository or not connected to the right Work Repository.
 Case 3. The Scenarios or Load Plans have been renamed or have invalid schedules.           
 Case 4. May be an issue with the Java version used by the Agent.
 Case 5. Agent is having trouble to connect to the Work Repository. In this case, the Update Schedule or View schedule Window usually hangs.
 Case 6. The Standalone Agent's Physical Agent name is the default name, OracleDIAgent for J2EE Agent and the J2EE Agent is deployed using the default template. 
 Note:
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.