How To Force the Failure of an ODI Mapping / Integration Interface if the Number of Records Written to the C$ Table Differs from the Number of Rows in a Flat File Source Datastore (Doc ID 1456094.1)

Last updated on NOVEMBER 02, 2023

Applies to:

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

Goal

Having an Oracle Data Integrator (ODI) Mapping / Integration Interface with as source, a flat file Datastore.

It may happen that the carriage return at the end of some records in the text file is missing, and hence Oracle Data Integrator (ODI), without any warning, doesn't write/update the expected number of records to the target Datastore...

How can this be workaround?

How to force the status of the Mapping / Integration Interface to "failure" whenever the number of rows in the source file does not match the number of records inserted by the ODI LKM into the C$ table?

The article applies to all releases of ODI like the current 12C as well as to previous releases.

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!

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

How To Force the Failure of an ODI Mapping / Integration Interface if the Number of Records Written to the C$ Table Differs from the Number of Rows in a Flat File Source Datastore (Doc ID 1456094.1)

Applies to:

Goal

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!