|
Problem IT18900
|
Status: Closed |
RUNSTATS WITH UNQUALIFIED INDEX NAME CAN CAUSE TRAP IN ENGINE INCERTAIN CONDITION
|
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The conditions for this problem to happen are:
- The db2 server is older than the client AND does NOT support
'unqualified' index names in the 'runstats' statement.
- Client is newer than database server AND does support
'unqualified' index names in the 'runstats' statement.
- Client runs the 'runstats' with unqualified' index name(s) on
a cataloged database pointing to the database on the older
database server.
Example:
db2 server version: V97
db2 client version: V105 FIXPACK 7
runstats on table for indexes ' (without
schema in indexname) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* This is currently a limitation *
**************************************************************** |
| Local Fix: |
Prevent from running 'runstats' statement with unqualified'
index name(s) if the database server does NOT support
'unqualified' index names in the 'runstats' statement. |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner :
follow-up : IT19046 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.01.2017
08.05.2017
08.05.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
