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

USER INTERRUPT ERROR MESSAGES IN DB2DIAG.LOG DUE TO AUTO RUNSTATS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The db2diag.log shows ERROR messages "User Interrupt", which are 
caused by interrupted automatic runstats. 
For example: 
 
FUNCTION: DB2 UDB, catalog services, sqlrlCatalogScan::update, 
probe:80 
RETCODE : ZRC=0x80100003=-2146435069=SQLP_LINT "Interrupt from 
application" 
          DIA8003C The interrupt  has been received. 
 
or 
 
FUNCTION: DB2 UDB, catalog services, sqlrlCatalogScan::update, 
probe:80 
RETCODE : ZRC=0x80100003=-2146435069=SQLP_LINT "Interrupt from 
application" 
          DIA8003C The interrupt  has been received. 
 
or 
 
FUNCTION: DB2 UDB, catalog services, sqlrlCatalogScan::update, 
probe:60 
RETCODE : ZRC=0x80480003=-2142765053=SQLDXE_INTR "User 
Interrupt" 
          DIA8003C The interrupt  has been received. 
 
 
While runstats is a low priority task, it is expected to get 
interrupted when the current table gets locked for normal change 
operations. 
Therefore the interrupt messages should be logged as 
'Information' instead of 'ERROR' and become only visible with 
DIAGLEVEL 4. 
Detailed runstats messages are still to be find in the 
db2optstats log files.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 7.                      * 
****************************************************************
Local Fix:


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       :

02.09.2015
20.01.2016
20.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