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

X LOCKS LEFT ON CATALOG CACHE AFTER EXECUTION OF REORGCHK COMMAND

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
Some locks are still held on table after execution of reorgchk 
command. So, query executed on the table from other shell may 
wait for the locks to be released. 
 
Execute following commands to see the locks : 
 
$ db2 create db TESTDB 
$ db2 connect to TESTDB 
$ db2 "create table TEST.TAB1 ( ID int )" 
$ db2 reorgchk on table TEST.TAB1 
$ db2pd -locks -db TESTDB 
 
Locks: 
Address            TranHdl    Lockname                   Type 
   Mode Sts Owner      Dur HoldCount  Att  ReleaseFlg 
0x07000000404F18C0 2          53514C4445464C540763DD2841 
Internal P ..S  G   2          1   0          0x00 0x40000000 
0x07000000404F0C80 2          00000005000000000D6D000752 Row 
   ..X  G   2          2   0          0x00 0x40001DE0 
0x07000000404F07C0 2          53514C4332473135AAEB550641 
Internal P ..S  G   2          1   0          0x00 0x40000000 
0x07000000404F0D00 2          00000005000D6D07437817A043 
CatCache   ..X  G   2          255 0          0x00 0x40000000 
0x07000000404F1540 2          0001000007000000437817A043 
CatCache   ..X  G   2          255 0          0x00 0x40000000 
0x07000000404F06C0 2          0000000600000000124B001252 Row 
   ..X  G   2          1   0          0x10 0x40000000 
0x07000000404F0640 2          00000108000000000000000054 Table 
   .IX  G   2          1   0          0x00 0x40000000 
0x07000000404F0B00 2          00000006000000000000000054 Table 
   .IX  G   2          1   0          0x10 0x40000008 
0x07000000404F0840 2          00000005000000000000000054 Table 
   .IX  G   2          7   0          0x00 0xC0001DEE 
 
Now, from another shell/session, execute below commands, the 
second command will hang, until "db2 commit" is executed on 
previous shell. 
< another session > 
 
$ db2 connect to TESTDB 
$ db2 "select * TEST.TAB1 with ur " 
... hold on until commit after reorgchk ...
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* APAR IC65204 fix user                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Some locks are still held on table after execution           * 
* ofreorgchk command on APAR IC65204 fix included system.      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 9.5 FixPak 6                          * 
****************************************************************
Local-Fix:
Execute "db2 commit" after reorgchk command.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
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 was first fixed in Version 9.5 FixPak 6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC67538 IC67539 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
02.03.2010
24.06.2010
27.07.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version