|
Problem IC72734
|
Status: Closed |
ADDING DATABASE PARTITION CORRUPTS PARTITION MAP LEADING TO TABLES INCORRECTLY DEFINED ACROSS PARTITIONS |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
If you add a database partition to an existing database
partition group with the following conditions:
- Database partition group contains an empty, automatic storage
tablespace (no tables in it)
- The new database partition is added to the database partition
group using the WITHOUT TABLESPACES clause
then the partition map defined for the database partition group
is incorrectly updated.
For example, if your existing database partition group MYDBPG,
is defined across database partitions (0,1) the PARTITIONMAP
column in SYSCAT.PARTITIONMAPS will show database partition
numbers
0x0000 and 0x0001 over and over again. If you add the database
partition 2 to MYDBPG, then the PARTITIONMAP is corrupted where
it should read, 0x0000 followed by 0x0001 and 0x0002, it will
instead show 0x0000, 0x0001 and some unknown 0xXXXX value.
This leads to tables not being created on the newly added db
partition, and can further cause unknown abnormal termination or
other side effects in this tablespace. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 Version 9.5 GA through to Fix Pack 7 servers using *
* the Database Partitioning Feature (DPF) and adding new *
* database partitions to existing database partition groups. *
****************************************************************
* PROBLEM DESCRIPTION: *
* The PARTITIONMAP column is incorrectly being updated when *
* adding a new database partition leading to unexpected *
* behaviour when creating tables in these tablespaces. *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 Version 9.5 Fix Pack 8, or see "Local Fix" for *
* workarounds. *
**************************************************************** |
| Local Fix: |
Define at least one table in the tablespace before adding the
database partition to the database partition group. If your
partition map is already corrupted, it is best to contact DB2
Service to help cleanup your environment. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem is first fixed in DB2 Version 9.5 Fix Pack 8 and all
subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.11.2010
30.06.2011
30.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP8,
9.5.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
