|
Problem IT21931
|
Status: Closed |
SPATIAL EXTENDERS DATA TYPES NOT CLEARED AFTER DB2SE DISABLE_DB <DATABASE> AND CANNOT BE DROPPED |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
When performing the command "db2se disable_db <database>".
DB2 shows that the operation was successful --> GSE0000I The
operation was completed successfully.
However when performing a db2look or investigating the
SYSCAT.DATATYPES
or SYSIBM.SYSDATATYPES catalog tables, db2 shows that there are
still 7 datatypes related to the db2se functionality remaining.
>> db2 "select typename from syscat.datatypes where typeschema =
'DB2GSE'"
ST_GEOMCOLLECTION
ST_LINESTRING
ST_MULTILINESTRING
ST_MULTIPOINT
ST_MULTIPOLYGON
ST_POINT
ST_POLYGON
Then tried to drop these datatypes manually but this instructs
that the corresponding datatype does not exist.
>> db2 drop type DB2GSE.ST_POINT
DB21034E The command was processed as an SQL statement because
it was not a valid Command Line Processor command. During SQL
processing it returned: SQL0204N "DB2GSE.ST_POINT" is an
undefined name. SQLSTATE=42704 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Db2 11.1 Mod 3 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.08.2017
19.03.2018
19.03.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
