| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC84230 | Status: Closed |
HADR STANDBY MAY TRY TO RETRIEVE LOG FILES EVEN WHEN LOG ARCHIVE METHOD IS SET TO LOGRETAIN | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
HADR standby database may still try to retrieve log files from
archive device even after userexit is turned off.
When hitting the problem, database configuration looks like
this:
Log retain for recovery enabled (LOGRETAIN) =
RECOVERY
First log archive method (LOGARCHMETH1) =
LOGRETAIN
User exit for logging enabled (USEREXIT) = OFF
Normally, with the above configuration, HADR standby should not
retrieve log files for local catchup. However, when hitting this
problem, similar messages could be found in db2diag.log:
2011-05-21-20.37.50.736389-300 I71697A360 LEVEL: Warning
PID : 25165998 TID : 5792 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000
EDUID : 5792 EDUNAME: db2lfr (SAMPLE) 0
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, probe:600
MESSAGE : Extent 249204 in log path may be stale. Trying
archive.
2011-05-21-20.37.50.736576-300 I72058A364 LEVEL: Warning
PID : 25165998 TID : 5021 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000
EDUID : 5021 EDUNAME: db2logmgr (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0249204.LOG.
2011-05-21-20.37.50.736675-300 I72423A418 LEVEL: Warning
PID : 25165998 TID : 5021 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000
EDUID : 5021 EDUNAME: db2logmgr (HADRDB) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLogFile, probe:4148
MESSAGE : Completed retrieve for log file S0249204.LOG on chain
0 to
/db2/P21/log_dir/NODE0000/.
Please also take db2pd -db dbname -dpsdbcb and send the output
to
IBM or further investigation. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 FP1 or subsequent fix pack * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
| Solution | |
Problem First Fixed in DB2 Version 10.1 Fix Pack 1 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.06.2012 05.12.2012 05.12.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.1 |
|
| 10.5.0.1 |
|