home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC86340 Status: Closed

DRDA WRAPPER REPORTS -901 ERROR IF SOURCE TABLE/VIEW HAS COLUMN WITH
CHAR(0) DATA TYPE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
You will encountered -901 error when creating a nickname 
pointing to a table or a view that has a column with data type 
char(0): 
 
SQL0901N  The SQL statement failed because of a non-severe 
system error. Subsequent SQL statements can be processed. 
(Reason "Invalid nickname column length".)  SQLSTATE=58004 
 
The problem is easy to be reproduced: 
========================================================== 
db2 connect to <source dbname> 
db2 "create view test_view as select char('') as col1 from 
sysibm.sysdummy1" 
db2 connect to <fed dbname> 
db2 "create nickname nk_test for drdaserver.schema.test_view" 
==========================================================
Problem Summary:
User affected: 
  Users who use DRDA wrapper of  in InfoSphere Federation Server 
Problem description and summay: 
  See error description
Local Fix:
Cast the CHAR(0) column to a not null column as: 
 
cast('' as char(1)) as col1
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was fistly fixed in Version 10, FixPak 2. This 
fix should be applied on the federation Server.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.09.2012
04.01.2013
04.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList