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

SQL2918N RECEIVED WHEN THE INGEST COMMAND SPECIFIES BOTH ONE OF THE
IMPLICITLYHIDDEN OPTIONS AND THE EXCEPTION TABLE CLAUSE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When the INGEST command specifies both one of the 
implicitlyhiddenxxx options and the exception table clause, it 
gets SQL2918N message, even though the command does not specify 
a column list 
 
Ex: 
create table t1(c1 int,c2 int,c3 TIMESTAMP NOT NULL IMPLICITLY 
HIDDEN GENERATED ALWAYS FOR EACH ROW ON UPDATE AS ROW CHANGE 
TIMESTAMP) 
DB20000I  The SQL command completed successfully. 
 
create table t2 like t1 
DB20000I  The SQL command completed successfully. 
 
create unique index ind1 on t1(c1,c2) 
DB20000I  The SQL command completed successfully. 
 
INGEST FROM FILE test1.del FORMAT DELIMITED by '|' 
IMPLICITLYHIDDENMISSING EXCEPTION TABLE T2 MESSAGES ingest.msg 
RESTART NEW 'm1' INSERT INTO T1 
SQL2901I  The ingest utility completed at timestamp "07/11/2013 
11:52:11.477788". Number of errors: "1". Number of warnings: 
"1".    Message 
file: "ingest.msg". 
 
In ingest.msg: 
 
SQL2918N  Invalid combination of keywords, 
"IMPLICITLYHIDDENMISSING" and 
"<column-list>", specified in the INGEST command.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of the DB2 LUW ingest utility                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 3.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.5 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.11.2013
14.04.2014
14.04.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 FixList
10.5.0.3 FixList
10.5.0.4 FixList