|
Problem IC96219
|
Status: Closed |
RENAME TABLESPACE NOT HANDLING ERROR DURING SYSTEM CATALOG UPDATE AND LEAVING ORPHAN ROW(S) |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - 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: *
* Update to 10.5.0.3 *
**************************************************************** |
| Local Fix: |
Contact IBM DB2 Service to assist with cleanup of the system
catalog. |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
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 Fixed In 10.5.0.3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.09.2013
28.02.2014
28.02.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
