DB2 - Problem description
Problem IC95484 | Status: Closed |
DB2 ONLINE BACKUP WITH INCLUDE LOGS FAILS WITH ERROR SQL2428N | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
An DB2 online backup operation with INCLUDE LOGS may fail with error SQL2428N. SQL2428N The BACKUP did not complete because one or more of the requested log files could not be retrieved. During generation of the backup image DB2 retrieves the transaction log files for inclusion in the backup image. An attempt to open the log file is failing and following messages can be seen in the db2diag.log file: 2012-06-20-14.56.23.951981+120 I395941A441 LEVEL: Warning PID : 9240656 TID : 3244 PROC : db2sysc 0 INSTANCE: db2inst NODE : 000 EDUID : 3244 EDUNAME: db2logmgr (TESTDB) 0 FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4148 MESSAGE : Completed retrieve for log file S0000079.LOG on chain 1 to /db2data/db2inst/NODE0000/SQL00014/SQLOGDIR/. 2012-06-20-14.56.23.954085+120 I396383A359 LEVEL: Error PID : 9240656 TID : 3244 PROC : db2sysc 0 INSTANCE: db2inst NODE : 000 EDUID : 3244 EDUNAME: db2logmgr (TESTDB) 0 FUNCTION: DB2 UDB, data protection services, sqlpgole, probe:3200 MESSAGE : Error 118489302 opening database log extent 79: 2012-06-20-14.56.23.955852+120 I396743A445 LEVEL: Error PID : 9240656 TID : 3244 PROC : db2sysc 0 INSTANCE: db2inst NODE : 000 EDUID : 3244 EDUNAME: db2logmgr (TESTDB) 0 FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4150 RETCODE : ZRC=0x071000D6=118489302=SQLP_EXT_DBID_INCORR "Database ID does not match Extent probably for another database." 2012-06-20-14.56.24.113750+120 I397659A525 LEVEL: Error PID : 9240656 TID : 7355 PROC : db2sysc 0 INSTANCE: db2inst NODE : 000 DB : TESTDB APPHDL : 0-5572 APPID: *LOCAL.db2id004.120620125442 AUTHID : DB2USR EDUID : 7355 EDUNAME: db2bm.2691.0 (TESTDB) 0 FUNCTION: DB2 UDB, data protection services, sqlpOpenLogForBackup, probe:20 RETCODE : ZRC=0x82100016=-2112880618=SQLPLFR_RC_RETRIEVE_FAILED "Log could not be retrieved" 2012-06-20-14.56.24.115078+120 E398185A575 LEVEL: Severe PID : 9240656 TID : 7355 PROC : db2sysc 0 INSTANCE: db2inst NODE : 000 DB : TESTDB APPHDL : 0-5572 APPID: *LOCAL.db2id004.120620125442 AUTHID : DB2USR EDUID : 7355 EDUNAME: db2bm.2691.0 (TESTDB) 0 FUNCTION: DB2 UDB, database utilities, sqlubProcessLogExtent, probe:1844 MESSAGE : ADM8010E Backup was unable to copy requested log file "S0000079.LOG" for inclusion in the backup image. The backup has been aborted. DB2 is querying for the log file in the highest log chain. This might not neccessarily be the right log file for inclusion to the backup image. Following steps will reproduce the issue: - create database (with LOGARCHMETH set) - backup, restore and rfwd to get a new log chain 1 - generate some logs on log chain 1 - drop database - create database (log chain 0) - generate some logs on log chain 0 - run online backup (which retrieves log from log chain 1) | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to 10.5.0.3 * **************************************************************** | |
Local Fix: | |
1) Back up the old log data on TSM and delete the logs. 2) Change the TSM option so that the log files are archived to there own "container" (-fromnode and -fromowner are the common options). | |
available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem Fixed In 10.5.0.3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.08.2013 28.02.2014 28.02.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.3 | |
10.5.0.3 |