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 IT29178 Status: Closed

Detect LFR moving to next extent too early and fail so that readlog does
not skip log records.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
=== Capture log ===
2019-03-26-22.06.02.880169  ASN8041D
"Q Capture" : "QASN" : "LogrdThread" : db2LogRead API is sending
us backwards in theDB2 Log: First LSN is
"0000:0005:1552:b1ac:0000:d96b:43dc:0c78" while Next Start LSN
is "0000:0000:0000:0000:0000:0000:0000:0000"
2019-03-26-22.06.02.880338  ASN0552E
"Q Capture" : "QASN" : "logrd" : The program encountered an SQL
error. The server name is "CXL1". The SQL request is
"db2ReadLog". The table name is "". The SQLCODE is "-1273". The
SQLSTATE is "     ". The SQLERRMC is "CXL1??88357.LOG??". The
SQLERRP is "SQLPRLOG".
SQL1273N  An operation reading the logs on database "CXL1"
cannot continue because of a missing log file "S0188357.LOG" on
database partition "0" and log stream "3".
2019-03-26-22.06.02.880382  ASN0005E
CAPTURE "QASN" : "LogrdThread". The Capture program encountered
an error when reading the DB2 log.  The log sequence number is
"0000:0005:1552:B1AC:0000:D96B:43DC:0C78", the SQLCODE is
"-1273", and the reason code is "".
2019-03-26-22.06.05.881483  ASN8999D
db2ReadLog SQL1273 retry 1 of 5

=== db2diag.log ===
2019-03-26-22.06.02.838600+480 I826860A1535         LEVEL: Error
PID     : 5243322              TID : 86637          PROC :
db2sysc 3
INSTANCE: db2inst2             NODE : 003           DB   : CXL1
APPHDL  : 3-1414               APPID:
172.17.31.111.33523.190322100003
AUTHID  : QREPADM              HOSTNAME: cxl2csdp04
EDUID   : 86637                EDUNAME: db2agent (CXL1) 3
FUNCTION: DB2 UDB, recovery manager,
sqlpshrValidateLogStreamEndPoint, probe:1130
MESSAGE : ZRC=0x86100026=-2045771738=SQLPR_MISSING_LOG_EXT
          "Used by various operations reading the logs to
indicate a missing log extent."
DATA #1 : 
Forward phase of recovery on stream 3 did not reach end of logs.
stream returned log records: yes
found logRecs after end pt: no
                    lastExt: 188356
   lastExtNeededForRecovery: 188356
   lastExtNeededForTbspRfwd: 0
                 nextRecLso: 31446629380908
              LastRecLsoLFH: 31446620699338
              shrScanEndLso: 18446744073709551615
             shrLastDiskLso: 31446629382261
        shrScanNextFlagsOut: 0x1
      highestLfsLsnProduced: 21832577517/0000D96B43DC10CE
              maxStopLfsLsn:
18446744073709551615/FFFFFFFFFFFFFFFF
delayErrorUntilNextLogRead: true
            isReadLogOrOlic: true
                 isTbspRfwd: false
    gBkpEndMarker LFS / LSN: 21626398456/0000D96A76846027
                 LFH hflag1: 0x0
                 LFH hflag2: 0x0
                 LFH hflag3: 0x0
                GLFH hflag1: 0x20
                GLFH hflag2: 0x0

2019-03-26-22.06.02.872811+480 I828396A1061         LEVEL:
Warning
PID     : 5243322              TID : 86637          PROC :
db2sysc 3
INSTANCE: db2inst2             NODE : 003           DB   : CXL1
APPHDL  : 3-1414               APPID:
172.17.31.111.33523.190322100003
AUTHID  : QREPADM              HOSTNAME: cxl2csdp04
EDUID   : 86637                EDUNAME: db2agent (CXL1) 3
FUNCTION: DB2 UDB, recovery manager, sqlpshrScanNext, probe:3485
MESSAGE : ZRC=0x86100026=-2045771738=SQLPR_MISSING_LOG_EXT
          "Used by various operations reading the logs to
indicate a missing log extent."
DATA #1 : String, 41 bytes
Ignoring error detected on log stream id:
DATA #2 : db2LogStreamIDType, PD_TYPE_DB2_LOG_STREAM_ID, 2 bytes
3
DATA #3 : String, 11 bytes
At LFS/LSN:
DATA #4 : unsigned integer, 8 bytes
21832577585
DATA #5 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
0000D96B43DC1735
DATA #6 : String, 37 bytes
Because the log merge is finishing at
DATA #7 : unsigned integer, 8 bytes
21832577517
DATA #8 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
0000D96B43DC10CE

2019-03-26-22.06.02.873924+480 I829458A609          LEVEL: Error
PID     : 5243322              TID : 86637          PROC :
db2sysc 3
INSTANCE: db2inst2             NODE : 003           DB   : CXL1
APPHDL  : 3-1414               APPID:
172.17.31.111.33523.190322100003
AUTHID  : QREPADM              HOSTNAME: cxl2csdp04
EDUID   : 86637                EDUNAME: db2agent (CXL1) 3
FUNCTION: DB2 UDB, data protection services,
sqlpgReadLogReadAction, probe:15600
MESSAGE : ZRC=0x86100026=-2045771738=SQLPR_MISSING_LOG_EXT
          "Used by various operations reading the logs to
indicate a missing log extent."

2019-03-26-22.06.02.878903+480 I830068A604          LEVEL:
Warning
PID     : 5243322              TID : 86637          PROC :
db2sysc 3
INSTANCE: db2inst2             NODE : 003           DB   : CXL1
APPHDL  : 3-1414               APPID:
172.17.31.111.33523.190322100003
AUTHID  : QREPADM              HOSTNAME: cxl2csdp04
EDUID   : 86637                EDUNAME: db2agent (CXL1) 3
FUNCTION: DB2 UDB, data protection services, sqlpgReadLogAPI,
probe:17350
MESSAGE : ZRC=0x86100026=-2045771738=SQLPR_MISSING_LOG_EXT
          "Used by various operations reading the logs to
indicate a missing log extent."

2019-03-26-22.06.02.879485+480 E830673A545          LEVEL: Error
PID     : 5243322              TID : 86637          PROC :
db2sysc 3
INSTANCE: db2inst2             NODE : 003           DB   : CXL1
APPHDL  : 3-1414               APPID:
172.17.31.111.33523.190322100003
AUTHID  : QREPADM              HOSTNAME: cxl2csdp04
EDUID   : 86637                EDUNAME: db2agent (CXL1) 3
FUNCTION: DB2 UDB, data protection services, sqlpgReadLogAPI,
probe:1
DATA #1 : String, 12 bytes
S0188357.LOG
DATA #2 : String, 1 bytes
0
DATA #3 : String, 1 bytes
3
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.05.2019
20.01.2020
20.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)