|
Problem IC66414
|
Status: Closed |
TIMEOUT VALUE FOR LOG RETRIEVE IS HARD CODED. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The timeout value for log retrieve is hard coded. In the
environment that takes long to retrieve a log file, a backup
include log operation can fail, e.g.
2010-01-28-19.55.11.527724-300 I1641274E367 LEVEL:
Warning
PID : 4035 TID : 46912862415168PROC :
db2sysc 0
INSTANCE: db2bwq NODE : 000
EDUID : 32 EDUNAME: db2logmgr (BWQ) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0000030.LOG.
2010-01-28-19.55.18.340276-300 I1641642E516 LEVEL: Error
PID : 4035 TID : 46931250243904PROC :
db2sysc 0
INSTANCE: db2bwq NODE : 000 DB : BWQ
APPHDL : 0-23319 APPID: *N0.db2bwq.100128220043
AUTHID : BWQADM
EDUID : 4237 EDUNAME: db2bm.4217.4 (BWQ) 0
FUNCTION: DB2 UDB, data protection services,
sqlpOpenLogForBackup, probe:20
RETCODE : ZRC=0x82100016=-2112880618=SQLPLFR_RC_RETRIEVE_FAILED
"Log could not be retrieved"
2010-01-28-19.55.18.340666-300 E1642159E566 LEVEL: Severe
PID : 4035 TID : 46931250243904PROC :
db2sysc 0
INSTANCE: db2bwq NODE : 000 DB : BWQ
APPHDL : 0-23319 APPID: *N0.db2bwq.100128220043
AUTHID : BWQADM
EDUID : 4237 EDUNAME: db2bm.4217.4 (BWQ) 0
FUNCTION: DB2 UDB, database utilities, sqlubProcessLogExtent,
probe:1787
MESSAGE : ADM8010E Backup was unable to copy requested log file
"S0000030.LOG"
for inclusion in the backup image. The backup has been
aborted. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* TIMEOUT VALUE FOR LOG RETRIEVE IS HARD CODED. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW Version 9.7 Fix Pack 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 |
Problem was first fixed in Version 9.7 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Comment |
This APAR is a duplicate of IC65595 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.02.2010
02.07.2010
20.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.,
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
