Last updated on JUNE 28, 2016
Applies to:Oracle Data Integrator - Version 10.1.3.2.0 and later
Information in this document applies to any platform.
The following issues occur with Oracle Data Integrator (ODI) 10g/11g Integration Interfaces or 12c Mappings:
- An Integration Interface / Mapping fails at Insert FK errors step with "invalid character" or "invalid syntax" error messages due to the incorrect name of the primary key column.
- The Integration Interface / Mapping fails at Create target table step with " invalid character " message due to the incorrect name specified for the target table.
- The Integration Interface / Mapping fails at Load Data step with " invalid character " message due to the incorrect name specified for the table alias.
- The 11g mappings / 12c column attributes are not valid: If you click on the target column, the source column is not highlighted, and the SQL code is incorrectly generated for the Integration Interface / Mapping.
Having for example in ODI 11g:
Physical Office --> PHY.Physical Office
Parent --> PHY.Parent executed
Alias: Default --> PHY.Alias: Default
In this case, the Integration Interface fails at "Load data" step:
java.sql.SQLException: Unexpected token: Physical Office in statement [select PHY.Physical Office "Physical Office"]
... the error arising while executing the following SQL command:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms