Unexpected Mix Of Both ANSI And Standard SQL When Generating CROSS And OUTER Joins In ODI 12c Mapping
(Doc ID 1918450.1)
Last updated on JUNE 16, 2022
Applies to:
Oracle Data Integrator - Version 12.1.2.0.0 to 12.1.3.0.1 [Release 12c]Information in this document applies to any platform.
Symptoms
NOTE: In the example below any information such as schema and table names represent a fictitious sample (based upon made up data used in an Oracle Demo instance). Any similarity to actual data or persons, living or dead, is purely coincidental and not intended in any manner.
When working with ODI version 12.1.2 to create a Mapping which uses both a cross and an outer join, the cross join is always generated as ANSI SQL, even if the check box called Generate ANSI Syntax is unchecked.
This results in conflicts with other joins (outer join) at runtime.
For example, when generating the mapping, the following mix of SQL syntaxes will fail at runtime :
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |