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

SQLCODE -1273 OR -2038 ERRORS IS RETURNED ON DB2 READ LOG API CALL FROM Q
CAPTURE PROGRAM

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Q Capture program may stop after receiving SQLCODE -1273 or 
-2038 errors on db2 read log api call even though the 
transaction log file including the requested LSN surely exists 
in the archive log directory. 
 
  This error symoton logs the following warning / errror 
messages in db2diag.log and formatted shredder EDU flight 
recorder like *SQLP.SHREDDER_MASTER.events.bin should be 
checked. 
 
2016-06-30-06.11.39.821845+540 I67816564A2642       LEVEL: 
Warning 
PID     : 11797032             TID : 360745         PROC : 
db2sysc 4 
INSTANCE: db2inst1             NODE : 004           DB   : 
DBNAME 
APPHDL  : 4-55756              APPID: *N4.db2inst1.160629150238 
AUTHID  : QCAPTURE             HOSTNAME: hostname 
EDUID   : 360745               EDUNAME: db2agent (DBNAME) 4 
FUNCTION: DB2 UDB, recovery manager, 
sqlpshrValidateLogStreamEndPoint, probe:1122 
DATA #1 : <preformatted> 
Some log records might not be returned on this call, will be 
returned on next call. Please collect the diag data and send it 
to IBM support 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x090000002E08A04C pdLogPrintf + 0x28 
  [1] 0x0900000029CE57EC 
sqlpshrValidateLogStreamEndPoint__FP14sqlpMasterDbcbP17SQLPSHR_M 
ASTER_CBP17SQLPSHR_WORKER_CBUlCUlCbT6 + 0xFE8 
  [2] 0x0900000029163BD0 
sqlpshrScanNext__FPvP8sqeAgentUlPP16SQLPR_LOGREC_DISPUl + 0x7488 
  [3] 0x0900000029162048 
sqlpshrScanNext__FPvP8sqeAgentUlPP16SQLPR_LOGREC_DISPUl + 0x5900 
  [4] 0x0900000029161BE8 
sqlpshrScanNext__FPvP8sqeAgentUlPP16SQLPR_LOGREC_DISPUl + 0x54A0 
  [5] 0x090000002916A44C 
sqlpshrScanNext__FPvP8sqeAgentUlPP16SQLPR_LOGREC_DISPUl + 0x20C8 
  [6] 0x090000002E4855E4 
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5 
sqlca + 0x572F0 
  [7] 0x090000002E482444 
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5 
sqlca + 0x54150 
  [8] 0x090000002E3A2514 
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5 
sqlca + 0xF50 
  [9] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 
  [10] 0x090000002E3A2514 
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5 
sqlca + 0xF50 
  [11] 0x090000002E3AE408 
sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo + 0x5FC 
  [12] 0x090000002D6EAD64 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x6C0 
  [13] 0x090000002D6F96F4 
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x1164 
  [14] 0x090000002D6F96F4 
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x1164 
  [15] 0x090000002D6F92E8 
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xD58 
  [16] 0x090000002C0D6F7C 
@72@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA8 
  [17] 0x090000002C0D7A90 
@72@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x5F8 
  [18] 0x090000002C35F788 RunEDU__8sqeAgentFv + 0x3D7F8 
  [19] 0x090000002C3AF384 RunEDU__8sqeAgentFv + 0x120 
  [20] 0x090000002CD36844 EDUDriver__9sqzEDUObjFv + 0x134 
  [21] 0x090000002DEF3C58 sqloEDUEntry + 0x390 
  [22] 0x0900000000BB0E10 _pthread_body + 0xF0 
  [23] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 
 
2016-06-30-06.11.39.880699+540 I67824745A1500       LEVEL: Error 
PID     : 11797032             TID : 360745         PROC : 
db2sysc 4 
INSTANCE: db2inst1             NODE : 004           DB   : 
DBNAME 
APPHDL  : 4-55756              APPID: *N4.db2inst1.160629150238 
AUTHID  : QCAPTURE             HOSTNAME: hostname 
EDUID   : 360745               EDUNAME: db2agent (DBNAME) 4 
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 : <preformatted> 
Forward phase of recovery on stream 4 did not reach end of logs. 
stream returned log records: yes 
 found logRecs after end pt: no 
                    lastExt: 71812 
   lastExtNeededForRecovery: 71812 
   lastExtNeededForTbspRfwd: 0 
                 nextRecLso: 18733190811118 
              LastRecLsoLFH: 18733190811987 
              shrScanEndLso: 18446744073709551615 
             shrLastDiskLso: 18733190811988 
        shrScanNextFlagsOut: 0x1 
      highestLfsLsnProduced: 4947246650/0000000E439DA39C 
              maxStopLfsLsn: 
18446744073709551615/FFFFFFFFFFFFFFFF 
            isReadLogOrOlic: true 
                 isTbspRfwd: false 
    gBkpEndMarker LFS / LSN: 4114349644/0000000BB92E7683 
                 LFH hflag1: 0x0 
                 LFH hflag2: 0x1 
                 LFH hflag3: 0x0 
                GLFH hflag1: 0x100060 
                GLFH hflag2: 0x0
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2 read log api user                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 FixPack 9 or later               * 
****************************************************************
Local Fix:
Solution
Fixed in DB2 Version 10.5 FixPack 9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.07.2016
27.09.2017
27.09.2017
Problem solved at the following versions (IBM BugInfos)
9.0.
Problem solved according to the fixlist(s) of the following version(s)