LOAD_PLAN_REALTIME_PROJECT Does Not Restart Itself From Error "ODI-1266: Agent OracleDIAGent detected Session as stale session and set to error status" (Doc ID 2369825.1)

Last updated on APRIL 28, 2021

Applies to:

Symptoms

ACTUAL BEHAVIOR

When there is a network connection problem or an agent gets disconnected from master and work repository momentarily, ODI can end up with stale sessions for the three load plans which show be indefinitely running (LOAD_PLAN_ON_DEMAND, LOAD_PLAN_REALTIME_PROJECT, LOAD_PLAN_REALTIME_GLOBAL).

This will result in a Load Plan, which was in a running state before the agent momentarily disconnects from master and work repository, to fail with the following error: "ODI-1266: Agent OracleDIAGent detected Session as stale session and set to error status."

The three load plans are designed to restart themselves by calling LOAD_PLAN_RETRIES_INCREMENT.

However, LOAD_PLAN_REALTIME_PROJECT is not restarting itself when this condition occurs.

Note:

• LOAD_PLAN_REALTIME_GLOBAL does successfully restart
• LOAD_PLAN_ON_DEMAND does successfully restart

EXPECTED BEHAVIOR

The LOAD_PLAN_REALTIME_PROJECT should properly restart itself after failing with ODI-1266 when there is a network connection problem or an agent gets disconnected from master and work repository momentarily.

STEPS
Starting with a running environment (as well as having all three load plans in a running state), complete the following steps:

1. Forcefully close the ODI Managed Server
2. Restart the ODI Managed Server
3. Start the ODI Studio
4. From the Operator tab, note:
   
   • the failure with the LOAD_PLAN_REALTIME_PROJECT
   • the load plan not restarting
     
     

Changes

Cause

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