Issues Concerning Table and Column Names Containing Spaces, Hyphen ("-") or Other Special Characters in ODI
(Doc ID 424100.1)
Last updated on DECEMBER 12, 2023
Applies to:
Oracle Data Integrator - Version 10.1.3.2.0 and laterOracle Data Integrator on Marketplace - Version 1.0.2 and later
Information in this document applies to any platform.
Symptoms
NOTE: In this article, property values used in examples and commands represent a fictitious sample for clarity and should be replaced by the actual values for use in your environment. Any similarity to actual environments, past or present, or users, living or dead, is purely coincidental and not intended in any manner.
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:
The article applies to all releases of ODI like the current 12C as well as to previous releases.
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! |