DB2 - Problem description
| Problem IC95867 | Status: Closed |
SQL0104N IS RETURNED WHEN UPDATING SYSSTAT.COLDIST.COLVALUE VIA DB2LOOK MIMIC MODE | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
The update of statistics of SYSSTAT.COLDIST.COLVALUE generated
via db2look -m (mimic mode) may fail with SQL0104N error.
The same output looks as follows:
UPDATE SYSSTAT.COLDIST
SET COLVALUE=''<value> '',
VALCOUNT=<value>
WHERE COLNAME = '<value>' AND TABNAME =
'<value>' AND TABSCHEMA = '<SCHEMA> ' AND TYPE =
'<value>' AND SEQNO = <value>
DB21034E The command was processed as an SQL statement because
it was not a valid Command Line Processor command. During SQL
processing it
returned:
SQL0104N An unexpected token "<value>" was found following
"DIST SET
COLVALUE=''". Expected tokens may include: "CONCAT".
SQLSTATE=42601
This occurs because of character wrapping for COLVALUE: db2look
-m adds
two single quotes instead of one single quote. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Users on DB2 V10.5 FP2 and lower * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to 10.5.0.3 * **************************************************************** | |
| Local Fix: | |
As a temporary workaround: Remove one single quote for the COLVALUE literal in the update statement, then run the statement again: UPDATE SYSSTAT.COLDIST SET COLVALUE='<value> ', VALCOUNT=<value> WHERE COLNAME = '<value>' AND TABNAME = | |
| available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
Problem Fixed In 10.5.0.3 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.09.2013 03.03.2014 03.03.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 |
|