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

WITH INFINITE LOGGING, AFTER FAILED LOG ARCHIVAL, TRANSACTION MIGHT GET
STUCK DUE TO MAXIMUM ALLOWABLE UNARCHIVED LOG

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
With infinite logging enabled, in environments where new 
transactional log files are produced very often, active 
transactions might get stuck waiting for new logs to be 
allocated. 
 
For problem to occur following conditions must be true: 
1. Infinite logging must be enabled (LOGSECOND -1) 
2. New logs have to be produced more often than ARCHRETRYDELAY 
database parameter is set. Usually this is the case when 
LOGFILSIZ is set to very low value. 
3. There is a transaction that spans across more than 256 logs 
4. In the past there was a failed log archival. 
 
Before problem occurs, multiple errors about failed FAILARCHPATH 
cleanup will be logged, e.g: 
 
2014-12-17-15.44.03.984770+060 E11404703E482         LEVEL: 
Warning 
PID     : 4626                 TID : 46912937912064  PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
HOSTNAME: db2host 
EDUID   : 37                   EDUNAME: db2logmgr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgCleanFailArchPath, probe:4920 
DATA #1 : <preformatted> 
Unable to find log file 339345 for LOGARCHMETH1.  Assume log was 
archived and continue. 
 
 
As the result following message will be logged in db2diag.log: 
 
2015-01-07-04.10.49.832799+060 E3366782E519          LEVEL: 
Warning 
PID     : 17323                TID : 46912874997504  PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
HOSTNAME: db2host 
EDUID   : 62                   EDUNAME: db2loggr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, sqlpgadf, probe:540 
DATA #1 : <preformatted> 
Maximum allowable unarchived log files reached. 
DB2 will continue to reissue archive requests. 
Check that log archiving is working properly. 
 
despite the fact that currently log archival is working 
properly. 
Active transaction will get stuck in Commit active or Compiling 
state, with following functions on the top of the stack: 
 
sqlpgResSpace 
sqlpWriteLR 
 
and waiting for SQLO_LT_SQLP_DBCB__add_logspace_sem latch.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 5 or higher.            * 
****************************************************************
Local-Fix:
Recycle the database or reduce ARCHRETRYDELAY: 
db2 update db cfg for <db_name> using archretrydelay 0 immediate
Lösung
Problem first fixed in DB2 version 10.1 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
16.03.2015
26.07.2015
31.05.2017
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList