DB2 - Problem description
Problem IT17147 | Status: Closed |
ACCIDENTAL REMOVAL OF DAT FILE FROM SMS TABLESPACE COULD RESULT IN DUPLICATE TABLE IDS IN CATALOGS | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
The following steps could reproduce this problem: db2 "create tablespace sms1 managed by system using ('/data2/bennyv/path1' ) " for i in 0 1 2 3 4 5 6 7 8 9 do db2 "create table tab$i ( col1 int ) in sms1 " done db2stop force $ ls /data2/bennyv/path1 SQL00002.DAT SQL00003.DAT SQL00004.DAT SQL00005.DAT SQL00006.DAT SQL00007.DAT SQL00008.DAT SQL00009.DAT SQL00010.DAT SQL00011.DAT SQLTAG.NAM $ rm /data2/bennyv/path1/SQL00004.DAT db2start db2 "create table tab11 ( col1 char, col2 int) in sms1 " $ db2 -tvf dup2.sql select ctime, substr(name,1,30) name, substr(creator,1,30) schema,fid,tid, colcount from sysibm.systables s1 where type = 'T' and (select count(*) from sysibm.systables s2 where s1.fid = s2.fid and s1.tid = s2.tid ) > 1 order by fid,tid, ctime desc CTIME NAME SCHEMA FID TID COLCOUNT -------------------------- -------------------- ---------------------- ------ ------ -------- 2015-03-05-06.34.09.907963 TAB11 BENNYV 4 5 2 2015-03-05-06.32.49.984790 TAB2 BENNYV 4 5 1 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 10.5 Fix Pack 9 or higher * **************************************************************** | |
Local Fix: | |
Don't remove DAT file manually from SMS tablespace or move data to DMS tablespace. | |
Solution | |
First fixed in Db2 10.5 Fix Pack 9 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.09.2016 29.09.2017 29.09.2017 |
Problem solved at the following versions (IBM BugInfos) | |
9.0. | |
Problem solved according to the fixlist(s) of the following version(s) |