DB2 - Problembeschreibung
Problem IT05914 | Status: Geschlossen |
DB2CKLOG MIGHT WRONGLY REPORT A LOGFILE AS INVALID, IF IT IS A TRUNCATED LOGFILE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
db2cklog might report the following for a log file that was truncated by eg ARCHIVE LOG command. ======================================================== "db2cklog": Processing log file header of "S00nnnnn.LOG". "db2cklog": Processing log pages of "S00nnnnn.LOG" (total log pages: "6843"). ==> page "1" ... ==> page "1001" ... ==> page "2001" ... ==> page "3001" ... ==> page "4001" ... ==> page "5001" ... ==> page "6001" ... DBT7067E Log file validation failed because a log page ends with an unexpected log record type. Header flag of the log page: "0x001C". Unexpected log record type: "0x0084". DBT7048E The db2cklog utility determined that the current log file is invalid. "db2cklog": Finished processing log file "S00nnnnn.LOG". Return code: "0". ======================================================== | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.5 fixpack 7 * **************************************************************** | |
Local-Fix: | |
n/a | |
Lösung | |
Problem was first fixed in DB2 version 10.5 fixpack 7 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 04.12.2014 22.01.2016 22.01.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |