My Oracle Support Banner

ODI Sessions Enter Queued Status and never Execute (Doc ID 2519068.1)

Last updated on OCTOBER 22, 2019

Applies to:

Oracle Data Integrator - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

All Oracle Data Integrator (ODI) sessions are in a queued state after initiating execution and do not start. The Agent logs show the following message at the time when the sessions are going to the queued state.

[2019-02-28T20:56:52.649-08:00] [<ODI_SERVER>] [WARNING] [ODI-1011] [oracle.odi.agent] [tid: <TID>] [userId: <USERID> ] [ecid: <ECID>] [APP: <APP>] [partition-name: <NAME>] [tenant-name: <NAME>] [oracle.odi.runtime.MrepExtId: 1532647573422] [oracle.odi.runtime.AgentName: <AGENT_NAME>] [oracle.odi.runtime.ExecPhase: ExecuteSession] [oracle.odi.runtime.OdiUser: <ODI_USER>] [oracle.odi.runtime.WrepName: <WORK_REPOSITORY>] [oracle.odi.runtime.ScenarioName: <SCENARIONAME>] [oracle.odi.runtime.ScenarioVer: <VERSION>] [oracle.odi.runtime.LoadPlanName:<LOAD_PLAN>] [oracle.odi.runtime.EntityGuid: <ENTITY_GUID>] [oracle.odi.runtime.SessName: <SESS_NAME>>] [oracle.odi.runtime.SessId: <SESSION_ID>] [oracle.odi.runtime.LoadPlanExec: <EX>] [oracle.odi.runtime.LoadPlanStep: <LOAD_PLAN_STEP>] [oracle.odi.runtime.ExecHierarchy: <EX>] Max session count is 0 for agent <OracleDIAgent>, but an asynchronous scenario has been started. The agent will queue a session for the scenario. If no other agent is available to dequeue and execute the session, it will not be executed.

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
Solution


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