DB2 - Problem description
| Problem IC97541 | Status: Closed |
INGEST: RUN TIME IS 32X WORSE THAN IMPORT WHEN TABLE HAS MANY UDTS | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
Ingest can perform poorly when the INGEST command omits the field list and specifies a target table that has a lot of user-defined data types (UDTs). For example, ingesting 100K rows into a 300-column table that has 75 columns whose type is a UDT took 32 times as long as import (16 minutes vs. 30 seconds). | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Ingest users using UDTs on DB2 V10.1 Fixpack 2 or lower. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 for LUW Version 10.5 Fixpack 3 or higher. * **************************************************************** | |
| Local Fix: | |
There are two possible work arounds:
(1) Define an explicit field list on the INGEST command. For
example:
INGEST FROM FILE my_file.del FORMAT DELIMITED
(
$field1 INTEGER EXTERNAL,
$field2DECIMAL(5,2) EXTERNAL,
...
$fieldn CHAR(10)
)
INSERT INTO my_table_with_many_udts;
(2) Modify the table to use built-in types instead of
user-defined types. | |
| available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
First fixed in DB2 for LUW Version 10.5 Fixpack 3. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.11.2013 27.02.2014 27.02.2014 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.3 |
|
| 10.5.0.3 |
|