|
Problem IC97902
|
Status: Closed |
INGEST COMMAND NO LONGER RETURNS SQL3604N WHEN EXCEPTION TABLE HAS DB2SECURITYLABEL COLUMN |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When the INGEST command specifies an exception table and the
target table contains a DB2SECURITYLABEL column, the
corresponding column in the exception table must have type
VARCHAR(128) FOR BIT DATA, but not type DB2SECURITYLABEL. In
DB2 LUW Version 10.1 GA, FP1, and FP2, if the exception table
violated this requirement, you would get the following error:
SQL3604N The statement or command failed because the following
exception table is invalid: "exception-table-name". Table to
which the exception table corresponds: "table-name". Reason
code: "2".
But in Version 10.1 FP3, this error no longer occurs. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of the DB2 LUW ingest utility. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 LUW Version 10.1 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.11.2013
12.05.2014
12.05.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
