How To Force Oracle Database NLS_LENGTH_SEMANTICS Within ODI
(Doc ID 1303649.1)
Last updated on MAY 27, 2020
Applies to:
Oracle Data Integrator - Version 10.1.3.4.5 and laterInformation in this document applies to any platform.
Goal
It may happens that NLS_LENGTH_SEMANTICS are not coherent between Data Sources and Targets.
As a result, the following alternative messages might be signaled at runtime of Oracle Data Integrator (ODI) Integration Interfaces:
ORA-01401: inserted value too large for column
or
ORA-01459: invalid length for variable character string
or
ORA-25137: Data value out of range
or
ORA-12899: value too large for column
or, if using ODBC:
8000 : S1090 : sun.jdbc.odbc.JdbcOdbcBatchUpdateException: [Oracle][ODBC]Invalid string or buffer length
If it is not desired to update NLS_LENGTH_SEMANTICS at the database level, and if ODI Integration Interfaces have already been developed... it is feasible to force it at ODI level.
Solution
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
| Goal |
| Solution |
| ODI 11g and higher |
| ODI 11g, ODI 10g and legacy Sunopsis V3, v4 |
| References |