ODI does not Check SQL Code when Validating Filter Expressions
(Doc ID 2357965.1)
Last updated on JANUARY 30, 2019
Applies to:Oracle Data Integrator - Version 184.108.40.206.6 to 220.127.116.11.0 [Release 12c]
Information in this document applies to any platform.
An Oracle Data Integrator (ODI) 12c Mapping with a sub-query Filter has a SQL code error in the sub-query Filter condition - i.e. there is an additional close parenthesis which has no corresponding open parenthesis.
Even though this error exists, the Mapping validation completes successfully.
ODI documentation does recommend using Mapping validation to check the SQL code:
Home / Middleware / Oracle Data Integrator 18.104.22.168.0
> Fusion Middleware Developing Integration Projects with Oracle Data Integrator
> 8 Creating and Using Mappings
> 8.2 Creating a Mapping
> 8.2.3 Connecting and Configuring Components
> 22.214.171.124 Defining Expressions and Conditions
To define the mapping of a target attribute:
4. Optionally, after modifying an expression or condition, consider validating your mapping to check for errors in your SQL code.
Click the green check mark icon at the top of the logical diagram. Validation errors, if any, will be displayed in a panel.
In current case, the malformed SQL command is not detected during the Mapping validation.
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