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

DB2 MAY FAIL READING PAGES FROM LOG FILE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Once problem happens, following messages are logged to the
db2diag.log:

2017-05-13-00.21.24.455042-300 I983584551A11037   LEVEL: Error
PID     : 2687738              TID  : 7712        PROC : db2sysc
0
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE
EDUID   : 7712                 EDUNAME: db2loggr (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services, sqlpgarl,
probe:2440
MESSAGE : Bp a00030000212000 blkOffSet 48702 ReadCount 8
blksRead 0 FCBp:

2017-05-13-00.21.24.455707-300 I983595589A450     LEVEL: Severe
PID     : 2687738              TID  : 7712        PROC : db2sysc
0
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE
EDUID   : 7712                 EDUNAME: db2loggr (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services, sqlpgarl,
probe:2440
RETCODE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not
exist"
          DIA8506C Unexpected end of file was reached.

2017-05-13-00.21.24.459179-300 I983596689A1405    LEVEL: Error
PID     : 2687738              TID  : 78105       PROC : db2sysc
0
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE
APPHDL  : 0-55777              APPID:
10.10.10.10.40577.180712180858
AUTHID  : DB2INST1
EDUID   : 78105                EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services, sqlpgrlg,
probe:2320
DATA #1 : 
-2029060087 when reading LSO 67601888663164 from log file
S0506978.LOG  dpsAgtCbFlags 0 setSkipOutputBuf 1
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x090000000213CA00 pdLogPrintf + 0x70
  [1] 0x0900000000FCF800 pdLogPrintf@glue23B + 0xC4
  [2] 0x090000000183F784
sqlpgrlg__FP8sqeAgentUlN22PcP13SQLO_MEM_POOLP8SQLP_LRHPPc +
0x1E8
  [3] 0x0900000002091264
sqlptudo__FP8sqeAgentPUlP15SQLD_RECOV_INFOP11SQLP_TENTRY + 0x15C
  [4] 0x0900000002091698 sqlptud1__FP8sqeAgentUl + 0x3C
  [5] 0x0900000002F3BBB8
sqlpxrbk__FP8sqeAgentP15SQLXA_CALL_INFOPiP9SQLP_GXIDPP11sqlo_xla
tch + 0x20
  [6] 0x090000000209557C
sqlrrbck_dps__FP8sqlrr_cbiN22P15SQLXA_CALL_INFOP9SQLP_GXID +
0x1C4
  [7] 0x0900000002096F9C
sqlrrbck__FP8sqlrr_cbiN32P15SQLXA_CALL_INFO + 0x134
  [8] 0x0900000002097648 sqlrr_rollback__FP14db2UCinterface +
0xB0
  [9] 0x090000000209750C
sqljs_ddm_rdbrllbck__FP14db2UCinterfaceP13sqljDDMObject + 0x174


This APAR introduces retry logic which let to prevent temporary
errors, along with additional code which dumps additional
diagnostic messages in case of failure in retry.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 version 10.5 fixpack 10                       *
****************************************************************
Local Fix:
N/A
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.08.2017
16.07.2018
16.07.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)