suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT38504 Status: Closed

ONLINE BACKUP MAY FAIL WHILE PROCESSING TRANSACTION LOG FILE - BAD PAGELSO
FOUND FOR LOG FILE

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
Online backup may fail while processing a transaction log file.
The db2diag.log will show the following:


2021-09-12-06.20.36.469314-240 I40087923E748        LEVEL: Info
PID     : 23734                TID : 17592668320096 PROC :
db2sysc 69
INSTANCE: db2inst1             NODE : 069           DB   :
SAMPLE
HOSTNAME: node0306-fab
EDUID   : 178                  EDUNAME: db2lfr.69 (SAMPLE) 69
FUNCTION: DB2 UDB, recovery manager,
sqlplfrNeedToReopenCurrentExtFCB, probe:6483
DATA #1 : SQLPLFR_SCAN_ID, PD_TYPE_SQLPLFR_SCAN_ID, 8 bytes
LFR Scan Num            = 2592081
LFR Scan Caller's EDUID = 303365
MESSAGE : LFR needs to REOPEN the extent.
DATA #2 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes
3424
DATA #3 : unsigned integer, 8 bytes
54
DATA #4 : unsigned integer, 8 bytes
55
DATA #5 : Boolean, 1 bytes
false
DATA #6 : Boolean, 1 bytes
false

...

2021-09-12-06.20.53.317755-240 I40093574E597        LEVEL: Error
PID     : 23734                TID : 17592668320096 PROC :
db2sysc 69
INSTANCE: db2inst1             NODE : 069           DB   :
SAMPLE
HOSTNAME: node0306-fab
EDUID   : 178                  EDUNAME: db2lfr.69 (SAMPLE) 69
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMReadLog,
probe:2713
MESSAGE : ZRC=0x82100017=-2112880617=SQLPLFR_RC_RETRIEVE_RETRY
          "Log retrieval needs to be retried by LFR."
DATA #1 : SQLPLFR_SCAN_ID, PD_TYPE_SQLPLFR_SCAN_ID, 8 bytes
LFR Scan Num            = 2592081
LFR Scan Caller's EDUID = 303365

...

2021-09-12-06.20.59.442442-240 I40105765E600        LEVEL:
Severe
PID     : 23734                TID : 17734913945952 PROC :
db2sysc 69
INSTANCE: db2inst1             NODE : 069           DB   :
SAMPLE
APPHDL  : 0-56768              APPID: *N0.db2inst1.211117030324
AUTHID  : DB2INST1             HOSTNAME: node0306-fab
EDUID   : 303365               EDUNAME: db2bm.298646.0 (SAMPLE)
69
FUNCTION: DB2 UDB, data protection services,
sqlpReadLogForBackup, probe:40
MESSAGE : Bad pagelso found for log file:
DATA #1 : Hexdump, 4 bytes
0x000010213B3EC924 : 600D 0000
`...


The db2diag.log suggests that a backwards page was found in
S0003424.LOG, i.e., the log file is corrupted, however db2fmtlog
will show that the file is fine.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Those that take Db2 non-snapshot backups.                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Update to the latest fix pack.                               *
****************************************************************
Local Fix:
Retry BACKUP command.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Those that take Db2 non-snapshot backups.                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Update to the latest fix pack.                               *
****************************************************************
Comment
Problem was first fixed in Db2 Version 11.5.8.0.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.09.2021
29.12.2021
11.04.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)