During processing which utilizes DB2 ReadLogAPI, user might
notice following messages in the db2diag.log:
2015-08-04-10.50.54.316334+060 I9095133E2803 LEVEL:
Warning
PID : 133205 TID : 140736917923584 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-1975 APPID:
*LOCAL.db2inst1.150804093504
AUTHID : DB2INST1 HOSTNAME: hostname
EDUID : 35 EDUNAME: db2agent (SAMPLE) 0
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] 0x00007FFFEDD8F1DF pdLogPrintf + 0x8F
[1] 0x00007FFFF2EB7641
_Z32sqlpshrValidateLogStreamEndPointP14sqlpMasterDbcbP17SQLPSHR_
MASTER_CBP17SQLPSHR_WORKER_CBmmbb + 0x851
[2] 0x00007FFFF2EB9BB3
_Z24sqlpshrLogMergeForWorkerP17SQLPSHR_WORKER_CBmPmS1_S1_ +
0x823
[3] 0x00007FFFF2EBAB15
_Z24sqlpshrLogMergeIterationP8sqeAgentP17SQLPSHR_MASTER_CBmPmS3_
S3_ + 0xC5
[4] 0x00007FFFF2EBB123
_Z15sqlpshrLogMergeP8sqeAgentP17SQLPSHR_MASTER_CBPm + 0x113
[5] 0x00007FFFF2EBB6AE
_Z15sqlpshrScanNextPvP8sqeAgentmPP16SQLPR_LOGREC_DISPm + 0x32E
[6] 0x00007FFFF2DFA0FD
_Z22sqlpgReadLogReadActionP8sqeAgentP14sqlpMasterDbcbjP15SQLP_RE
ADLOG_CBP17SQLP_READLOG_INFOmPc + 0x37D
[7] 0x00007FFFF2DFCF2F
_Z15sqlpgReadLogAPIP8sqeAgentjP6db2LRIS2_S2_mmPcP17SQLP_READLOG_
INFOP5sqlca + 0xA2F
[8] 0x00007FFFF2EF075D
_Z22sqlpReadLogInternalAPIP8sqeAgentjP6db2LRIS2_S2_PcjP17SQLP_RE
ADLOG_INFOjP5sqlca + 0xDD
[9] 0x00007FFFF2EF0DA5
_Z15sqlpReadLogDRDAP5sqldaS0_P8sqeAgentP5sqlca + 0x465
[10] 0x00007FFFEFFD968E
_Z19sqlerKnownProcedureiPcPiP5sqldaS2_P13sqlerFmpTableP8sqeAgent
P5sqlca + 0x76E
[11] 0x00007FFFEFFDAFD3
_Z11sqlerCallDLP14db2UCinterfaceP9UCstpInfo + 0x733
[12] 0x00007FFFF3C86A87
_Z19sqljs_ddm_excsqlsttP14db2UCinterfaceP13sqljDDMObject + 0x9E7
[13] 0x00007FFFF3C85AFE
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U
Cinterface + 0x7E
[14] 0x00007FFFF00C28DC
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb +
0x36C
[15] 0x00007FFFF00BCBA0
/db2/opt/db2_home/db2i1/sqllib/lib64/libdb2e.so.1 + 0x33D5BA0
[16] 0x00007FFFF00BB1FC
/db2/opt/db2_home/db2i1/sqllib/lib64/libdb2e.so.1 + 0x33D41FC
[17] 0x00007FFFF00B8259
/db2/opt/db2_home/db2i1/sqllib/lib64/libdb2e.so.1 + 0x33D1259
[18] 0x00007FFFF00B7E4B
_Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0xEB
[19] 0x00007FFFEFDBD186 _ZN8sqeAgent6RunEDUEv + 0xC96
[20] 0x00007FFFF15A90A7 _ZN9sqzEDUObj9EDUDriverEv + 0xF7
[21] 0x00007FFFF0D7B091 sqloEDUEntry + 0x301
[22] 0x00000034BF2079D1 /lib64/libpthread.so.0 + 0x79D1
[23] 0x00000034BEAE88FD clone + 0x6D
Values to validate end of log stream does not accurately
represent all logs flushed to disk, and as a result may cause
this validation message to appear incorrectly. The messages are
not harmful in a non-purescale environment, as subsequent
ReadLogAPI calls processes previously missed log records
correctly. In a purescale environment, this message will result
in an error as it may indicate logs were merged in the wrong
order.
This APAR fix is to ensure that the values used in the
validation properly account for flushing to disk that may
happen. |
