DB2 FOR LUW / DB2FORLUW / A10 - DB2

Remote column on MSSQL Server is nvarchar or nchar and the local 
column type used to update the corresponding nickname is 
vargraphic, when the local column length is over than 2000, 
update nickname failed with  SQL1822N with server error "HY104 
Invalid precision value". 
 
UPDATE NICK1 SET ( C1 ) = ( select C1 from LTAB) 
 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
SQL1822N  Unexpected error code "HY104" received from data 
source "MSSQL2008_SERV". Associated text and tokens are "Invalid 
precision value". SQLSTATE=560BD 
 
To reproduce the problem: 
 
set passthru mssql2008_serv; 
CREATE TABLE RTAB(C1 nvarchar(4000) COLLATE 
SQL_Latin1_General_CP1_CI_AS NULL); 
set passthru reset; 
 
CREATE NICKNAME NICK1 FOR <server_name>.<user_name>.RTAB; 
create LTAB (C1 vargraphic(2001)); 
insert into LTAB values ('the values is over 2000 characters '); 
 
UPDATE NICK1 SET ( C1 ) = ( select C1 from LTAB) 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
SQL1822N  Unexpected error code "HY104" received from data 
source "MSSQL2008_SERV". Associated text and tokens are "Invalid 
precision value". SQLSTATE=560BD 
 
The error happens because the local column precision is 
calculated as the physical buffer length. If the column is a 
double byte type with length 2001, the precision will be 4002 
which over the threshold of max permit value.

Define the local column with length no larger than 2000.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

02.09.2013
27.08.2014
27.08.2014