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

Excessive db2diag message while running readlog program

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
The following db2diag messages may be seen every few seconds 
while running readlog program. 
 
2016-07-21-12.21.59.785000-420 I142450F575          LEVEL: Info 
PID     : 3068                 TID : 5868           PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000           DB   : 
SRV116DB 
APPHDL  : 0-1798               APPID: 
127.0.0.1.53656.160721191801 
AUTHID  : DB2ADMIN             HOSTNAME: srv116 
EDUID   : 5868                 EDUNAME: db2shred (SRV116DB) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:8091 
DATA #1 : <preformatted> 
Starting shredder mapping phase. 
   shrScanStartLfs = 26765 
   shrScanStartLsn = 0000000000316378 
 
2016-07-21-12.21.59.800000-420 I143027F575          LEVEL: Info 
PID     : 3068                 TID : 5868           PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000           DB   : 
SRV116DB 
APPHDL  : 0-1798               APPID: 
127.0.0.1.53656.160721191801 
AUTHID  : DB2ADMIN             HOSTNAME: srv116 
EDUID   : 5868                 EDUNAME: db2shred (SRV116DB) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:8372 
DATA #1 : <preformatted> 
Starting shredder log data reading phase. 
   scanStartLso    = 988120227 
   scanStartExtent = 206
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2V11                                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 11.1 Mod1 Fix Pack 1                          * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
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
First fixed in DB2 11.1 Mod1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.12.2016
11.05.2017
11.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
11.1.1.1 FixList