SQL3125W  The character data in row "4" and column "2" was truncated because 

the data is longer than the target database column.

SQL3110N  The utility has completed processing.  "4" rows were read from the 

input file.

SQL3221W  ...Begin COMMIT WORK. Input Record Count = "4".

SQL3222W  ...COMMIT of any database changes was successful.

SQL3149N  "4" rows were processed from the input file.  "3" rows were 

successfully inserted into the table.  "1" rows were rejected.

Number of rows read         = 4

Number of rows skipped      = 0

Number of rows inserted     = 3

Number of rows updated      = 0

Number of rows rejected     = 1

Number of rows committed    = 4

As shown in the summary, during the import process one record from the input 

file was rejected, and three were inserted into the database. To understand the 

nature of the warnings, you should look into the data source file and the table 

definition (

db2look 

command). For Example 9 1, the table definition is presented 

in Figure 9 2, and the data file in Figure 9 3.

CREATE TABLE TABLE01 (

  C1 SMALLINT, 

  C2 CHAR(3), 

  C3 SMALLINT CHECK( C3 IN (1,2,3)))

Figure 9 2   Table definition for Example 9 1

1,"abc",1

2,"abc",4

32768,"abc",2

4,"abcd",3

Figure 9 3   Data file for Example 9 1

The first row from the input file (Figure 9 3) was inserted without any warnings. 

The second row was rejected because it violated check constraints (warnings 

SQL3148W, SQL0545N, SQL3185W

). A value of 

32768

 from the third row was 

 Chapter 9. Testing and tuning 

271