home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IT08250 Status: Closed

PURESCALE: FUNCTION SQLPSHRVALIDATELOGSTREAMENDPOINT MIGHT GENERATE MANY
WARNINGS IN DB2DIAG.LOG AND DUMP FILES REPEATEDLY

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The following warning in db2diag.log and dump files might be 
generated repeatedly when there is some idle member(s) on 
pureScale environment and Q Replication Capture is in running. 
 
2015-03-15-22.04.43.962458+540 I1754A2554           LEVEL: 
Warning 
PID     : 4916132              TID : 218074         PROC : 
db2sysc 4 
INSTANCE: db2inst1             NODE : 004           DB   : 
SAMPLEDB 
APPHDL  : 4-246                APPID: *N4.db2inst1.150313221138 
AUTHID  : DB2INST1             HOSTNAME: hostname1 
EDUID   : 218074               EDUNAME: db2agent (SAMPLEDB) 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] 0x090000002C388378 pdLogPrintf + 0x28 
  [1] 0x090000002B122124 
sqlpshrValidateLogStreamEndPoint__FP14sqlpMasterDbcbP17SQLPSHR_M 
ASTER_CBP17SQLPSHR_WORKER_CBUlCUlCbT6 + 0xFE4 
  [2] 0x09000000286FE838 
sqlpshrScanNext__FPvP8sqeAgentUlPP16SQLPR_LOGREC_DISPUl + 0x9F8C 
  [3] 0xFFFFFFFFFFFFFFFD ?unknown + 0x100000000 
  [4] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 
  [5] 0x09000000287028D8 
sqlpshrScanNext__FPvP8sqeAgentUlPP16SQLPR_LOGREC_DISPUl + 0x20C8 
  [6] 0x090000002C9983F0 
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5 
sqlca + 0x56378 
  [7] 0x090000002C9964B0 
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5 
sqlca + 0x54438 
  [8] 0x090000002C8ABFA8 
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5 
sqlca + 0xF50 
  [9] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 
  [10] 0x090000002C8ABFA8 
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5 
sqlca + 0xF50 
  [11] 0x090000002C8B7D80 
sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo + 0x5FC 
  [12] 0x090000002AF23204 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x650 
  [13] 0x090000002AF1A6F0 
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xFC4 
  [14] 0x090000002AF1A6F0 
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xFC4 
  [15] 0x090000002AF1ABC8 
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x149C 
  [16] 0x090000002C821C98 
@72@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA8 
  [17] 0x090000002C8227A8 
@72@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x5F8 
  [18] 0x090000002A5C96BC RunEDU__8sqeAgentFv + 0x4912C 
  [19] 0x090000002A60DA50 RunEDU__8sqeAgentFv + 0x128 
  [20] 0x090000002B99BD24 EDUDriver__9sqzEDUObjFv + 0x130 
  [21] 0x090000002AA469AC sqloEDUEntry + 0x38C 
  [22] 0x0900000000BB0E10 _pthread_body + 0xF0 
  [23] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 
 
2015-03-15-22.04.43.963112+540 I4309A182          LEVEL: Warning 
PID:4916132 TID:218074 NODE:004 Title: SQLPSHR_WORKER_CB 
Dump File:/db2/db2dump/DIAG0004/4916132.218074.004.dump.bin
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use db2Readlog API in pureScale systems.           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V10.5 FixPack 7 or later.              * 
****************************************************************
Local Fix:
Drive some activities on all members, and write a log record on 
every stream. 
This can be done by creating a dummy table on each member, 
followed by dropping it. 
 
db2 "create table dummy (x int)"; db2 "drop table dummy";
Solution
This problem was first fixed in DB2 V10.5 FixPack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.04.2015
08.02.2016
08.02.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList