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

THE DB2 "LOCK_COUNT" VALUE RETURNED FROM MON_GET_LOCKS TABLE
FUNCTION IS NOT CORRECT.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
when we use the  MON_GET_LOCKS function the LOCK_COUNT and the 
LOCK_HOLD_COUNT are both 0's . 
 
Eg: 
 
db2 "SELECT lock_count, lock_hold_count FROM 
TABLE(SNAP_GET_LOCK('sample', -2))"|more 
 
LOCK_COUNT           LOCK_HOLD_COUNT 
-------------------- -------------------- 
                   1                    0 
                   1                    0 
                   1                    0 
                   1                    0 
                   1                    0 
                   1                    0 
                   1                    0 
                   1                    0 
 
db2 "SELECT lock_count, lock_hold_count FROM TABLE 
(MON_GET_LOCKS( CLOB(''), -2)) 
 
LOCK_COUNT           LOCK_HOLD_COUNT 
-------------------- -------------------- 
                   0                    0 
                   0                    0 
                   0                    0 
                   0                    0 
                   0                    0 
                   0                    0 
                   0                    0 
                   0                    0 
                   0                    0 
                   0                    0
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users running on V9.7 GA and FP1 who use the                 * 
* MON_GET_LOCKSfunction.                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* when we issue a MON_GET_LOCKS the LOCK_COUNT and             * 
* theLOCK_HOLD_COUNT are both 0's .Eg:"db2 "insert into        * 
* msdb2.ORDER_CONTRACT select * fromathena.ORDER_CONTRACT      * 
* fetch first 1000000 rows only"While insert is running issue  * 
* :"SELECT * FROM TABLE (MON_GET_LOCKS( CLOB(''), -2))"to get  * 
* information about all the locks in the database.The          * 
* LOCK_COUNT and LOCK_HOLD_COUNT columns are both              * 
* zero.+++++++++++++++++++++++++++++++++APPLICATION_HANDLE     * 
* MEMBER LOCK_NAMELOCK_OBJECT_TYPE_IDLOCK_OBJECT_TYPE          * 
*       LOCK_MODE LOCK_CURRENT_MODELOCK_STATUS LOCK_ATTRIBUTES * 
*  LOCK_RELEASE_FLAGS LOCK_RRIIDLOCK_COUNT                     * 
* LOCK_HOLD_COUNT      TBSP_IDTAB_FILE_ID                      * 
* ADDITIONAL_DETAILS...69801      6                            * 
* FAFF97804E001D000000000052x'52'ROW                           * 
*    X        -G          0000000000000008 00000000400000000   * 
*                  0                    0-6                    * 
* -32617 -Workaround:use db2pd -locks or SNAP_GET_LOCK table   * 
* function.                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to FP2                                               * 
****************************************************************
Local-Fix:
use db2pd -locks or SNAP_GET_LOCK table function.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 9.7 Fix Pack 2
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66647 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.02.2010
08.07.2010
08.01.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList