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

LIST INDOUBT TRANSACTIONS COMMAND DOES NOT SHOW COMMIT STATE INDOUBT
TRANSACTIONS

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Although database snapshot shows there are indoubt transactions, 
the db2 list indoubt transactions command does not show those 
commit state indoubt transactions which were caused by node 
failure. Therefore user can not manually resolve those indoubt 
transactions, but need to restart database. 
 
db2pd -dbp <dbpartition num> -db <dbname> -transactions would 
show this type of indoubt transactions has Tflag 0x00010002, 
e.g. 
 
Address            AppHandl [nod-index] TranHdl    Locks 
State   Tflag      Tflag2     Firstlsn           Lastlsn 
SpaceReserved   LogSpace        TID            AxRegCnt   GXID 
ClientUserID                   ClientWrkstnName 
ClientApplName                 ClientAccntng 
0x00002AAAD4549180 2098     [000-02098] 37         0 
COMMIT  0x00010002 0x00000000 0x000003BF0168E540 
0x000003BF0168F98C 32              18446744073709551507 
0x00026F430313 0                   n/a 
n/a                            n/a 
n/a
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 2                       * 
****************************************************************
Local-Fix:
Force off all applications, deactivate database, then 
db2_all "db2 restart database <database name>"
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in Version 10.1 Fix Pack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.11.2012
31.12.2012
31.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList