How To Modify ODI Timeout Values (Doc ID 423721.1)

Last updated on FEBRUARY 08, 2024

Applies to:

Oracle Data Integrator - Version 3.2.03.01 and later
Oracle Data Integrator on Marketplace - Version 1.0.2 and later
Data Integration Platform Cloud Classic - Version 17.3.5 and later
Oracle Data Integrator Cloud Service - Version 17.1.3 and later
Information in this document applies to any platform.

Goal

A timeout

is signaled when launching an Oracle Data Integrator (ODI) Scenario with either:

A call to the "startscen.bat/.sh" script
A standalone Agent, a J2EE Agent, or a scheduler Agent
An embedded Agent (Local/No Agent) in ODI Designer
The use of an Agent from ODI Console or Metadata Navigator

Where and how is it possible to increase the values of the appropriate Timeout settings?

Solution

	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

When is the Oracle Data Integrator Timeout used?

ODI 12c specific considerations

1 (12c). How to set up the Timeout for the graphical environment (ODI Studio)?

2 (12c). How to set up the Timeout for the standalone and colocated Agents?

3 (12c). How to set up the Timeout for the J2EE Agent?

ODI 11g specific considerations

1 (11g). How to set up the Timeout for the graphical environment (ODI Studio)?

Where and how is the Timeout stored?

2 (11g). "startscen.bat/.sh" Timeout

3 (11g). Standalone Agent Timeout

4 (11g). J2EE Agent Timeout

ODI 10g specific considerations

1 (10g). How to set up the Timeout for the graphical environment (ODI Designer, Operator...)?

2 (10g) Where and how is the Timeout stored?

3 (10g). How to set up the Timeout for the "startscen", "startcmd", Execution and Scheduler Agents?

4 (10g). How to set up the Timeout for Metadata Navigator?

Troubleshooting guide

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