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 IT04529 Status: Geschlossen

THE MONITOR INFORMATION IN TCB IS WRONG WHICH CAUSES INCORRECT
REORG_LONG_TBSPC_ID VALUE

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When reorg LOB data, if longtbspace-name and tbspace-name are 
same, the REORG_LONG_TBSPC_ID will show a wrong value, here is 
an example: 
 
[db2v101@IM002_redhat db2dump]$ db2pd -d test -tablespaces 
 
Database Member 0 -- Database TEST -- Active -- Up 0 days 
00:34:41 -- Date 2014-09-18-05.50.56.257317 
 
Tablespace Configuration: 
Address            Id    Type Content PageSz ExtentSz Auto 
Prefetch BufID BufIDDisk FSC NumCntrs MaxStripe  LastConsecPg 
Name 
0x00002AAADE22BC60 0     DMS  Regular 4096   4        Yes  4 
1     1         Off 1        0          3            SYSCATSPACE 
0x00002AAADE234480 1     SMS  SysTmp  4096   32       Yes  32 
1     1         On  1        0          31           TEMPSPACE1 
0x00002AAADE23CCA0 2     DMS  Large   4096   32       Yes  32 
1     1         Off 1        0          31           USERSPACE1 
0x00002AAADE2454C0 3     SMS  Regular 4096   32       Yes  32 
1     1         Off 1        0          31           TSUNWEI 
0x00002AAADE24DCE0 4     DMS  Large   4096   4        Yes  4 
1     1         Off 1        0          3 
SYSTOOLSPACE 
0x00002AAADE256500 5     SMS  UsrTmp  4096   4        Yes  4 
1     1         On  1        0          3 
SYSTOOLSTMPSPACE 
0x00002AAADFBD0C40 6     DMS  Large   4096   32       Yes  32 
1     1         Off 1        0          31 
BIG_DATA_TBSP 
0x00002AAADFBD9460 7     DMS  Large   4096   32       Yes  32 
1     1         Off 1        0          31 
BIG_LOB_TBS1 
0x00002AAADFBF6C80 8     DMS  SysTmp  4096   32       Yes  32 
1     1         Off 1        0          31           TEST 
0x00002AAADFC01940 9     SMS  SysTmp  4096   32       Yes  32 
1     1         On  1        0          31           TEST2 
 
 
[db2v101@IM002_redhat ~]$ db2 reorg table big use TEMPSPACE1 
longlobdata use TEMPSPACE1 
DB20000I  The REORG command completed successfully. 
 
[db2v101@IM002_redhat ~]$ db2 "SELECT SUBSTR(TABNAME, 1, 15) AS 
TAB_NAME, SUBSTR(TABSCHEMA, 1,15) AS TAB_SCHEMA, REORG_PHASE, 
SUBSTR(REORG_TYPE, 1, 20) AS 
REORG_TYPE,REORG_TBSPC_ID,REORG_LONG_TBSPC_ID, 
REORG_STATUS,REORG_COMPLETION, DBPARTITIONNUM FROM TABLE( 
SNAP_GET_TAB_REORG('')) AS T" 
 
TAB_NAME        TAB_SCHEMA      REORG_PHASE      REORG_TYPE 
REORG_TBSPC_ID       REORG_LONG_TBSPC_ID  REORG_STATUS 
REORG_COMPLETION DBPARTITIONNUM 
--------------- --------------- ---------------- 
-------------------- -------------------- -------------------- 
------------ ---------------- -------------- 
BIG             DB2V101         REPLACE 
RECLAIM+OFFLINE+ALLO                    1                    7 
COMPLETED    SUCCESS                       0 
BIG             DB2V101         REPLACE 
RECLAIM+OFFLINE+ALLO                    1                    7 
COMPLETED    SUCCESS                       1 
 
  2 record(s) selected. 
 
 
 
We can see REORG_LONG_TBSPC_ID is 7, it should be 1.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use db2 v10.1                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 v10.1 fixpack 5 or above                      * 
****************************************************************
Local-Fix:
Lösung
The problem is first fixed in db2 v10.1 fixpack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.09.2014
15.07.2015
15.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList