DB2 FOR LUW / DB2FORLUW / 970 - DB2

During the import with insert_update and usedefaults options, if 
a column is a part of the primary key and this corresponding 
column in the source file has no explicit column data, e.g NULL, 
the import command will complain as below: 
 
SQL3015N  An SQL error "-206" occurred during processing. 
 
SQL0206N  "DEFAULT" is not valid in the context where it is 
used. 
SQLSTATE=42703 
 
Below are the steps of problem reproduction: 
 
1. Create a table and primary key 
 
 
db2 "create table alantest (col1 varchar(10) NOT NULL, col2 
varchar(10) NOT NULL DEFAULT 'HJP',col3 varchar(5) NOT NULL)" 
 
 
 
db2 "alter table alantest add primary key(col1,col2)" 
 
2. Edit an import file named alantest.del which get the col2 had 
NULL value 
 
aaa,,ccc 
 
3. For table alantest run 
 
db2 import from alantest.del of del modified by usedefaults 
insert_update into alantest 
 
--This will succeed. 
 
db2 import from alantest.del of del modified by usedefaults 
insert_update into alantest 
 
 
--This time it will fail with SQL3015N

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL USERS                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.7 FP9 or use localfix as a workaround.         * 
****************************************************************

Modify the source file to replace the NULL to an explicit value. 
OR 
Redefine the primary key -- db2 "alter table alantest add 
primary key(col1)"

DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

This problem has been fixed in v9.7 FP9

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC91801 IC95216 
follow-up : 

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

03.03.2013
17.12.2013
17.12.2013

9.7.FP9