My Oracle Support Banner

The MAX_CHILD_ERROR Parameter Of OdiWaitForChildSession Is Not Taken Into Account (Doc ID 424031.1)

Last updated on JUNE 16, 2022

Applies to:

Oracle Data Integrator - Version to [Release 3.2.03 to 10gR3]
Information in this document applies to any platform.
This problem can occur on any platform.


When launching child scenarios from a parent scenario, I would like to use the MAX_CHILD_ERROR parameter to signal to the parent that certain child scenarios have aborted.
However, it appears that this parameter is not taken into account :

When launching 3 child scenarios from a parent, 2 of them result into an error.

The API command is set as follows:

but the parent scenario does not signal an error with a "Failed" execution status.


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

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