|
Problem IT37956
|
Status: Closed |
ADMIN_MOVE_TABLE FAILS WITH SQL0104N WHEN MOVING TABLE WITH DOUBLE QUOTES IN NAME WHICH HAS A STATISTICS PROFILE
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
Steps to reproduce:
SET CURRENT SCHEMA OTMSPECIALCHARS
CREATE TABLE """TABLENAME_ENCLOSEDBY_DQ""" (I INT NOT NULL, VC
VARCHAR(30) NOT NULL) ORGANIZE BY ROW
CREATE UNIQUE INDEX """TABLENAME_ENCLOSEDBY_DQ""_INDX" ON
"""TABLENAME_ENCLOSEDBY_DQ""" (I)
RUNSTATS ON TABLE OTMSPECIALCHARS."""TABLENAME_ENCLOSEDBY_DQ"""
WITH DISTRIBUTION SET PROFILE ONLY
CALL
SYSPROC.ADMIN_MOVE_TABLE('OTMSPECIALCHARS','"TABLENAME_ENCLOSEDB
Y_DQ"','','','MOVE,TRACE')
SQL0104N An unexpected token ""TABLENAME_ENCLOSEDBY_DQ"""" was
found following "". Expected tokens may include:
"USE". SQLSTATE=42601 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Customers using double quotes in table names which have a *
* statistics profile. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 Version 11.5.7.0 (11.5 Mod 7 Fix Pack 0) *
**************************************************************** |
| Local Fix: |
Remove statistics profile before move and add it afterwards
again. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Customers using double quotes in table names which have a *
* statistics profile. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 Version 11.5.7.0 (11.5 Mod 7 Fix Pack 0) *
**************************************************************** |
| Comment |
Problem was first fixed in Db2 Version 11.5.7.0 (11.5 Mod 7 Fix
Pack 0) |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.08.2021
04.10.2021
04.10.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
