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

DB2 MIGHT TRY TO READ LOG RECORDS THAT DO NO LONGER EXIST AFTER LOG FILE
TRUNCATION

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
It may happen that Db2 wants to perform a rollback with the use 
of log records that no longer exist: 
 
2017-09-21-10.30.43.537525+000 I73458A13104         LEVEL: Error 
PID     : 9175218              TID : 105437         PROC : 
db2sysc 0 
INSTANCE: db2jkl               NODE : 000           DB   : JKL 
APPHDL  : 0-37321              APPID: 
165.131.135.142.29701.170921103031 
AUTHID  : SAPR3                HOSTNAME: server 
EDUID   : 105437               EDUNAME: db2agent (JKL) 0 
FUNCTION: DB2 UDB, data protection services, sqlptudo, 
probe:1010 
MESSAGE : ZRC=0x87100048=-2028994488=SQLP_BADLSO "Invalid LSO 
value." 
          DIA8546C An invalid log sequence offset (LSO), the 
value was "". 
DATA #1 : String, 34 bytes 
undolso / TEntryp / agtCB / dpsAcb 
DATA #2 : unsigned integer, 8 bytes 
108027041854878 
DATA #3 : SQLP_TENTRY, PD_TYPE_SQLP_TENTRY, 11856 bytes 
pSuccTid = a000204af104280 
pPrevTid = a000204af01ba80 
succ_lsn = 0 
pre_lsn = 0 
succ_undoLsn = 0 
pre_undoLsn =0 
logSpace = 1736 
ICushionContribution = 0 
logSpaceSaved = 0 
extraReserved = 18264 
totalReservedLogSpace = 246943 
mrtPenlist Address = 0 
Pending List Address = 0 
Pending List End Address = 0 
First Pending list entry for update MRT = 0 
tsp_to_repair = 0 
tsp_repaired = 0 
Table Space List Address = 0 
Transaction Entry State = 6: SQLP_TSAVEPOINT 
tflag = 00000000 
tflag2 = 00000200 
 
The root cause for this issue is unknown. This APAR will add 
debugging code that provide additional information for future 
root cause analysis.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Mod 3 Fixpack 3.                         * 
****************************************************************
Local Fix:
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
See Problem Description above.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.11.2017
16.03.2018
16.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)