DB2 - Problem description
Problem IT16951 | Status: Closed |
ARCHIVED LOG FILES MAY NOT BE RENAMED/DELETED AFTER CRASH RECOVERY PROCESSED THEM | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Archived log files may not be renamed/deleted after crash recovery processed them. In the following example of db2daig.log entries, crash recovery processed archived log files from S0000053.LOG to S0000057.LOG. But after crash recovery, those log files remained in log path, along with a new set of active log files. ........... 016-09-06-13.43.06.310326-240 I253764A565 LEVEL: Info PID : 51052904 TID : 4437 PROC : db2sysc 0 INSTANCE: dbinst NODE : 000 DB : SAMPLE HOSTNAME: sandbox EDUID : 4437 EDUNAME: db2logmgr (SAMPLe) 0 FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180 DATA #1 : <preformatted> Completed archive for log file S0000053.LOG to /TMP/dbinst/temp/logarch/dbinst/SAMPLE/NODE0000/LOGSTREAM0000/C 0000000/ from /home2/dbinst/dbinst/NODE0000/SQL00005/LOGSTREAM0000/. ........... 2016-09-06-13.43.14.393534-240 I257744A565 LEVEL: Info PID : 51052904 TID : 4437 PROC : db2sysc 0 INSTANCE: dbinst NODE : 000 DB : SAMPLE HOSTNAME: sanbox EDUID : 4437 EDUNAME: db2logmgr (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180 DATA #1 : <preformatted> Completed archive for log file S0000057.LOG to /TMP/dbinst/temp/logarch/dbinst/SAMPLE/NODE0000/LOGSTREAM0000/C 0000000/ from /home2/dbinst/dbinst/NODE0000/SQL00005/LOGSTREAM0000/. ........ 2016-09-06-13.45.39.976191-240 I277502A1292 LEVEL: Info PID : 42926520 TID : 3343 PROC : db2sysc 0 INSTANCE: dbinst NODE : 000 DB : SAMPLE APPHDL : 0-52 APPID: *N0.dbinst.160906174539 UTHID : dbinst HOSTNAME: sanbox EDUID : 3343 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:300 DATA #1 : <preformatted> Crash recovery started. Recovery status for log stream 0 lowtranlsn: 00000000020C3998 minbufflsn: 00000000020C3998 headlsn: 00000000020C3998 recoveryStartingLFSLSN: 0/0000000000000000 initialRecoveryStartingLFSLSN: 0/0000000000000000 groupHeadLsn: 00000000020C3998 groupMinBuffLSN: 00000000020C3998 HeadExtentID: 53 GroupHeadExtentID: 53 rfwdLogChainId: 0 rfwdHeadChainId: 0 numLogFilesInRecovery: 0 nextLso: 4081119457 nextLsn: 00000000020C3998 minPseudoLsn: FFFFFFFFFFFFFFFF LastFullRecLfsLsnLso: 1256622/00000000020C39E5/4101988622 LastRecLfsLsnLsoLFH: 1256622/00000000020C39E5/4101988622 ............ 2016-09-06-13.45.40.391946-240 I288601A1329 LEVEL: Info PID : 42926520 TID : 3343 PROC : db2sysc 0 INSTANCE: dbinst NODE : 000 DB : SAMPLE APPHDL : 0-52 APPID: *N0.dbinst.160906174539 AUTHID : DBINST HOSTNAME: sanbox DUID : 3343 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlpRecoveryPhasePostProcessing, probe:990 DATA #1 : <preformatted> After recovery phase post processing. Recovery status for log stream 0 lowtranlsn: 00000000020C3A2B minbufflsn: 00000000020C39E6 headlsn: 00000000020C39E6 recoveryStartingLFSLSN: 0/0000000000000000 initialRecoveryStartingLFSLSN: 0/0000000000000000 groupHeadLsn: 00000000020C39E6 groupMinBuffLSN: 00000000020C39E6 HeadExtentID: 58 GroupHeadExtentID: 58 rfwdLogChainId: 0 rfwdHeadChainId: 0 numLogFilesInRecovery: 5 nextLso: 4101994579 nextLsn: 00000000020C3A2B minPseudoLsn: FFFFFFFFFFFFFFFF LastFullRecLfsLsnLso: 1256623/00000000020C3A2A/4101994578 LastRecLfsLsnLsoLFH: 1256623/00000000020C3A2A/4101994578 ........ 2016-09-06-13.45.40.443185-240 E292178A495 LEVEL: Info PID : 42926520 TID : 3343 PROC : db2sysc 0 INSTANCE: dbinst NODE : 000 DB : SAMPLE APPHDL : 0-52 APPID: *N0.dbinst.160906174539 AUTHID : DBINST HOSTNAME: sanbox EDUID : 3343 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:3100 MESSAGE : ADM1531I Crash recovery has completed successfully. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 Fix Pack 6 * **************************************************************** | |
Local Fix: | |
Deactivate and activate database | |
Solution | |
First fixed in DB2 10.1 Fix Pack 6 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.09.2016 02.03.2017 02.03.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |