ODI File to Database Mapping Successfully Completes Even Though Invalid Records Exist in the Source File
(Doc ID 2663544.1)
Last updated on MAY 01, 2020
Applies to:Oracle Data Integrator - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
When investigating a successful mapping execution loading from a CSV file to an Oracle table, it was discovered that ".bad" and ".error" files were created containing details of invalid records. It is expected that in the event of invalid records, the load would fail.
For example, if the source CSV file has a column with data type "Numeric" after the reverse engineer process, the executed mapping is not failing when it comes across data that does not match the datastore type, but instead creates .BAD and .ERROR files for those records. Rows with valid data are successfully loaded to the target.
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
|Setting the Mapping to Fail with Invalid Data|