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 IC91275 Status: Closed

SQL3119W THROWN DURING LOAD/IMPORT USING DB2AUDIT DEL FILE DUE TO COLUMN
TYPE MISMATCH

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When archiving and extracting a delimited ASCII file using the 
'DB2AUDIT EXTRACT DELASC' command, the CONTRSTTYPE column is 
extracted as a string. However, the db2audit.ddl script creates 
the column as an integer. This results in a column type mismatch 
which throws an SQL3119W when executing a LOAD/IMPORT operation 
using the delimited files.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 FP3.                                    * 
****************************************************************
Local Fix:
Create the audit table with CONTRSTTYPE column as CHAR(1)
available fix packs:
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
Fixed in DB2 v10.1 FP3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.04.2013
02.10.2013
02.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList