'Field too large in ...' Message Signaling Incorrect Encoding Of Temporary Flat Files In An ODI Integration Interface Using "LKM Jco Bapi to Teradata (FastLoad)" On Linux Servers
(Doc ID 453080.1)
Last updated on OCTOBER 04, 2022
Applies to:Oracle Data Integrator - Version 10.1.3.2.0 and later
Information in this document applies to any platform.
When launching an Integration Interface on an ODI Agent running on a Linux server which extracts data from SAP with a JCO Interface to a temporary flat file, any accentuated characters are incorrectly inserted into the file.
More precisely, when using the "LKM Jco Bapi to Teradata (FastLoad)" Knowledge Module any accentuated characters are inserted into the flat file as double-byte data. This results in the signaling of error messages in the "Load to staging area" step of the following type indicating that the Source string is too long for the Target column:
However, when the same Integration Interface is run directly on a Microsoft Windows server no problem is detected and the temporary flat file is correctly coded.
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