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

DB2 MIGHT ABORT IN SQLPWRITETOLOG, PROBE:1370

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
DB2 database might abort with "sqlpWriteToLog, probe:1370" like 
in the following db2diag.log entry: 
 
2015-07-06-20.24.41.746289+120 I14813586A589      LEVEL: Severe 
PID     : 18613976             TID  : 232928      PROC : db2sysc 
0 
INSTANCE: db2inst1            NODE : 000         DB   : SAMPLE 
APPHDL  : 0-51592              APPID: 
32.81.177.76.32616.150705202922 
AUTHID  : DB2INST1 
EDUID   : 232928               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, sqlpWriteToLog, 
probe:1370 
DATA #1 : <preformatted> 
curLso 1018516166148705 too big, myLso 1018516166148705 myLrc 
129408182316 totalLength 76 bytesLeftToWrite 76 currentPage 0 
bytesLeftPage 3468 partsIdx 0
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 7.                      * 
****************************************************************
Local Fix:
It might help to increase LOGBUFSZ to avoid the crash.
Solution
First fixed in DB2 Version 10.5 Fix Pack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.09.2015
21.01.2016
21.01.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