home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC97341 Status: Closed

INCORRECT TABLE TYPE IN THE OUTPUT FROM MON_GET_TABLE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
MON_GET_TABLE table function might return wrong table type for 
newly created tables. 
 
Instead of the type - 'USER TABLE',  the type 'SYNOPSIS TABLE' 
might be seen. 
 
To reproduce this issue: 
 
db2set DB2_WORKLOAD=ANALYTICS 
db2 "CREATE DATABASE <DB_NAME>" 
db2 "CONNECT TO <DB_NAME>" 
db2 "CREATE TABLE <SCHEMA_NAME>.<TABLE_NAME> (a int)" 
db2 "SELECT tab_type FROM TABLE(MON_GET_TABLE('<SCHEMA_NAME>', 
'', -2))" 
 
===> 
 
TAB_TYPE 
--------------------- 
SYNOPSIS_TABLE
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 fix pack 4 (Cancun release)              * 
****************************************************************
Local Fix:
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem is fixed in DB2 10.5 fix pack 4 (Cancun release)
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
31.10.2013
05.03.2015
05.03.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList