DB2 - Problembeschreibung
Problem IC91488 | Status: Geschlossen |
DB2SUPPORT -D <DB_NAME> MIGHT HANG BECAUSE OF LOCK HELD BY OTHER APPLICATIONS ON SYSTEM CATALOG ROWS/TABLES | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
Collecting db2support with -d option might hang at the following entry: [Select count(*) from sysibm.systables where type='T' and creator ...] because of locks held by other applications on system catalog rows/tables | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1 Fix Pack 3. * **************************************************************** | |
Local-Fix: | |
Use -nco option to avoid database connection | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 version 10.1 Fix Pack 3. Starting from this version isolation level used by db2support tool can be specified via "-il" switch, which previously was applicable only to optimizer mode ("-st", "-sf"). In order to avoid locking, db2support can be collected with uncommitted read (UR) isolation level, e.g. $ db2support . -d <db_name> -il UR | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 11.04.2013 27.09.2013 27.09.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |