DB2 - Problembeschreibung
Problem IC96693 | Status: Geschlossen |
SQL0104N IS RETURNED WHEN UPDATING SYSSTAT.COLDIST.COLVALUE VIA DB2LOOK MIMIC MODE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All users on db2 v101 FP3 and lower * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v101 FP4 or apply the temporary workaround * **************************************************************** | |
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 = | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
First Fixed in db2 v101 FP4 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 08.10.2013 04.06.2014 04.06.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.4 |