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

LOCK TIMEOUT MESSAGES MAY FLOOD DB2DIAG.LOG

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Internal DB2 processes, such as the health monitor and other 
internal monitoring processes, may seem to flood the db2diag.log 
with lock timeout messages.  Although these processes are indeed 
encountering lock timeouts, they are expected and are able to 
handle these situations on their own. 
 
These messages should not be considered to be errors, rather 
they should be written as informational only (seen at diaglevel 
4).  To identify this APAR, you will see db2diag.log messages 
similar to the following three types: 
 
2009-10-07-14.53.44.322066-240 I8201090A548       LEVEL: Error 
PID     : 1482762              TID  : 7256        PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000         DB   : MYDB 
APPHDL  : 0-49                 APPID: *LOCAL.DB2.091007183609 
AUTHID  : DB2INST 
EDUID   : 7256                 EDUNAME: db2lused (MYDB) 0 
FUNCTION: DB2 UDB, catalog services, sqlrlCatalogScan::fetch, 
probe:40 
RETCODE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT 
          "LockTimeOut - tran rollback Reason code 68" 
DATA #1 : Hex integer, 4 bytes 
0x00000005 
 
2009-10-07-14.53.44.322524-240 I8201639A507       LEVEL: Error 
PID     : 1482762              TID  : 7256        PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000         DB   : MYDB 
APPHDL  : 0-49                 APPID: *LOCAL.DB2.091007183609 
AUTHID  : DB2INST 
EDUID   : 7256                 EDUNAME: db2lused (MYDB) 0 
FUNCTION: DB2 UDB, catalog services, sqlrlCatalogScan::update, 
probe:70 
RETCODE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT 
          "LockTimeOut - tran rollback Reason code 68" 
 
2010-01-11-09.00.58.138136-300 I522639A526        LEVEL: Error 
PID     : 995500               TID  : 6358        PROC : db2sysc 
0 
INSTANCE: db2inst               NODE : 000         DB   : MYDB 
APPHDL  : 0-1332               APPID: 
*LOCAL.db2inst.100111140018 
AUTHID  : DB2INST 
EDUID   : 6358                 EDUNAME: db2agent (MYDB) 0 
FUNCTION: DB2 UDB, catalog services, 
sqlrlCatalogScan::postUpdateCacheHandlin, probe:10 
RETCODE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT 
          "LockTimeOut - tran rollback Reason code 68" 
 
These db2diag.log entries can safely be ignored.  If your 
application is encountering lock timeouts, please refer to the 
DB2 Information Center for details on diagnosing lock timeouts.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Version 9.7 GA through to Fix Pack 1 servers on      * 
* Linux, Unix and Windows platforms.                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Lock timeout messages are written to db2diag.log when they   * 
* occur as DB2 is accessing or updating the system catalog     * 
* tables.  These lock timeouts messages only need to be        * 
* displayed as informational.                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 2, or simply ignore the  * 
* messages.                                                    * 
****************************************************************
Local-Fix:
None.  These messages can safely be ignored.
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
Problem first fixed in DB2 Version 9.7 Fix Pack 2 and all 
subsequent Fix Packs.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.01.2010
03.05.2010
03.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2,
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList