home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC72734 Status: Geschlossen

ADDING DATABASE PARTITION CORRUPTS PARTITION MAP LEADING TO TABLES
INCORRECTLY DEFINED ACROSS PARTITIONS

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
verfügbare FixPacks:
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

Lösung
Problem is first fixed in DB2 Version 9.5 Fix Pack 8 and all 
subsequent Fix Packs.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.11.2010
30.06.2011
30.06.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP8,
9.5.FP8
Problem behoben lt. FixList in der Version
9.5.0.8 FixList