|
Problem IC65595
|
Status: Closed |
A ONLINE backup using /INCLUDE/LOGS fails with SQL2428N and "Log could not be retrieved" in the db2diag.log. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A backup, which includes log files, may fail if the log files
that the backup needs are archived. Backup processing can
timeout waiting for archived log files to be moved from the
physical archive, if the files are large.
You will come across the following error messages from the
db2diag.log:
2010-01-08-02.06.01.052413-300 I76730A364 LEVEL: Warning
PID : 123456 TID : 1234 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000
EDUID : 1234 EDUNAME: db2logmgr (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0000464.LOG.
2010-01-08-02.06.11.592397-300 I77095A518 LEVEL: Error
PID : 123456 TID : 1111 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-12212 APPID:
*LOCAL.db2inst1.100108021230
AUTHID : TESTUSER
EDUID : 1111 EDUNAME: db2bm.421213.20 (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services,
sqlpOpenLogForBackup, probe:20
RETCODE : ZRC=0x82100016=-2112880618=SQLPLFR_RC_RETRIEVE_FAILED
"Log could not be retrieved" |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* The retrieval processing was not fast enough and the *
* backupprocessing assumes that the necessary log files will *
* beready but fails when it could not find one of the files. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 2. *
**************************************************************** |
| Local Fix: |
Be sure that archived log files that the backup needs are
available before the backup is attempted. |
| 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 |
First fixed in DB2 Version 9.7 Fix Pack 2. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66808 IC69324
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.01.2010
25.05.2010
25.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
|
 |
