My Oracle Support Banner

ODI Flow Control Check Fails Session after Passing Maximum Allowed Errors (Doc ID 2755035.1)

Last updated on FEBRUARY 26, 2021

Applies to:

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


After upgrading to Oracle Data Integrator (ODI) (or applying <Patch 28813200>), Flow Control stops checking further rows against the constraints after the maximum error threshold is marked with an error.

However, the behavior experienced in ODI and was to check the entire set of data and mark the session as failed if the max error threshold was met.

See the following examples for clarification.

Example One (behavior post upgrade): An ODI mapping is configured to use Flow Control, and a datastore is configured to error after a maximum of zero errors. When the mapping is executed and a row fails the check, the row is inserted into the E$ table, the session will stop and no further rows will be checked.

Example Two (behavior prior to upgrade): In ODI or, that same configuration will check all the rows and insert all failures into the E$ table before failing the session.




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.