Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC67529 Status: Closed

HADR STANDBY IN LOCAL CATCHUP HAS TOO MANY 'EXTENT MAY BE
STALE'MESSAGES IN DB2DIAG.LOG

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When an HADR Standby starts, while it is still in 'Local 
Catchup' state, messages similar to the following may be present 
in the db2diag.log: 
 
2010-03-29-14.36.21.253815-420 I256687E359         LEVEL: 
Warning 
PID     : 26546                TID  : 47046065121600PROC : 
db2sysc 
INSTANCE: inst1             NODE : 000 
EDUID   : 349                  EDUNAME: db2lfr (SAMPLE) 
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, probe:600 
MESSAGE : Extent 140 in log path may be stale. Trying archive. 
 
2010-03-29-14.36.21.258356-420 I257406E366         LEVEL: 
Warning 
PID     : 26546                TID  : 47046438414656PROC : 
db2sysc 
INSTANCE: inst1             NODE : 000 
EDUID   : 346                  EDUNAME: db2logmgr (SAMPLE) 
FUNCTION: DB2 UDB, data protection services, 
sqlpgRetrieveLogFile, probe:4130 
MESSAGE : Started retrieve for log file S0000140.LOG. 
 
 
One or two of those messages is normal.  In some cases you may 
see a lot, with corresponding log archive retrieval requests 
from the HADR Standby.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All HADR users                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Extra messages in the db2diag.log as well as unnecessary log * 
* archive retrievals during HADR Standby Local Catchup.        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 Fixpack 2                             * 
****************************************************************
Local Fix:
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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

Solution
At most 2 'extent may be stale' db2diag.log messages during HADR 
Standby Local Catchup.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67535 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.03.2010
13.05.2010
13.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList