DB2 - Problem description
Problem IC96196 | Status: Closed |
RENAME TABLESPACE NOT HANDLING ERROR DURING SYSTEM CATALOG UPDATE AND LEAVING ORPHAN ROW(S) | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
A RENAME TABLESPACE operation may leave orphan row(s) in SYSIBM.SYSTBSPACEAUTH after successful execution. The db2diag.log file will show following message written during the RENAME TABLESPACE operation: 2013-09-23-17.52.01.110415+120 I505925A579 LEVEL: Error PID : 19005606 TID : 9235 PROC : db2sysc 0 INSTANCE: db2inst NODE : 000 DB : SAMPLE APPHDL : 0-34197 APPID: *LOCAL.db2inst.130923154754 AUTHID : DB2INST EDUID : 9235 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, catalog services, sqlrlCatalogScan::update, probe:60 RETCODE : ZRC=0x80090005=-2146893819=SQLI_DUPKEY "Duplicate key violation" DIA8005C Duplicate key encountered, file token "" index token "" record id "". This causes subsequent CREATE TABLESPACE operations to fail with error SQL0803N when trying to create the a new tablespace using the same name as the pre RENAME TABLESPACE name. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7 Fix Pack 9 * **************************************************************** | |
Local Fix: | |
Contact IBM DB2 Service to assist with cleanup of the system catalog. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 version 9.7 Fix Pack 9 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC96217 IC96218 IC96219 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.09.2013 23.12.2013 23.12.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.9 | |
9.7.0.9 |