I've encountered this this problem which is a consequence of using
UTF-8. UTF-8 stores "standard" ascii using one byte per character. When
characters outside of the standard ascii set appear, they are stored as
16 bit unicode, occupying two character spaces. This requires that the
character (preferably varchar) columns be, worst case, defined twice as
large as the number of characters they will contain. Characters in some
languages will occupy more than 16 bits per character, requiring the
column definitions to be larger than two bytes/character.
UTF-8 data in columns also had interesting effects when using db2look to
transfer statistics data to another instance. The high2key and low2key
columns would not correctly transfer if the data values included UTF-8
16 bit characters.
Philip Sherman
pramod wrote:
Hi
I am facing the problem while inserting the spanish characters in the
DB2 UDB v8.2 database. We are pulling the data from SQL server through
informatica and then pushing the same in the DB2 database. Codepage for
DB2 database is UTF-8, which is Unicode. Whenever it is encountering
any spanish charater it is giving the following error:
SQL0302N The value of a host variable in the execute or open statement
is too large for its corresponding use.
SQLSTATE=22001
Please help me.
