ODI Does Not Check SQL Code when Validating Filter Expressions (Doc ID 2357965.1)

Last updated on DECEMBER 13, 2024

Applies to:

Symptoms

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:

https://docs.oracle.com/middleware/12213/odi/develop/creating-and-using-mappings.htm#ODIDG1560

Home / Middleware / Oracle Data Integrator 12.2.1.3.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
            > 8.2.3.4 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.

Cause