Using a Gateway with a Unicode Oracle Database Increases the Column Precision Three Times for Certain Data Types
(Doc ID 374744.1)
Last updated on FEBRUARY 01, 2019
Applies to:Oracle Database Gateway for DRDA - Version 188.8.131.52 to 184.108.40.206 [Release 9.2 to 11.1]
Oracle Database Gateway for DB2 - Version 10.2.0.2 to 10.2.0.3 [Release 10.2]
Information in this document applies to any platform.
***Checked for relevance on 02-Oct-2012***
Oracle Transparent Gateway for DB2 - Version: 10.2.0.2 to 10.2.0.3
All gateways called from an Oracle UTF-8/ unicode database.
Using any Oracle gateway up to release 220.127.116.11 with an Oracle unicode database character set will triple the varchar/char columns precision.
A normal select of this table might fail with an error when the precision of the data type exceeds the Oracle maximum length for this data type.
Also using procedures and trying to write information from a remote foreign database into an Oracle database with exactly the same precision as the foreign database column will fail with 'value too large' errors for these columns.
Upgrade Oracle RDBMS to a unicode based character set.
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
|CASE STUDY1 covering ORA-06502: PL/SQL: numeric or value error: character string buffer too small|
|CASE STUDY 2 ORA-12899 value too large for column|
|CASE STUDY 3 ORA-00910: specified length too long for its datatype|