DB2 - Problem description
Problem IC70116 | Status: Closed |
USERS MAY SEE INFO MESSAGE FROM SQLRLCATALOGSCAN::FETCH SHOWING IN DB2DIAG.LOG WHEN DIAGLEVEL=2 | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
This APAR is to address the issue that following db2diag.log Info entry appears when diaglevel not equal to 4 2010-07-13-03.50.31.578000-300 I4F567 LEVEL: Info PID : 4608 TID : 2424 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : KSUFAA APPHDL : 0-33 APPID: *LOCAL.DB2.100712213508 AUTHID : ONEWEBUSER EDUID : 2424 EDUNAME: db2lused (KSUFAA) FUNCTION: DB2 UDB, catalog services, sqlrlCatalogScan::fetch, probe:40 RETCODE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT "LockTimeOut - tran rollback Reason code 68" DATA #1 : Hex integer, 4 bytes 0x00000005 | |
Problem Summary: | |
Problem Description: USERS MAY SEE INFO MESSAGE FROM SQLRLCATALOGSCAN::FETCH SHOWING IN DB2DIAG.LOG WHEN DIAGLEVEL=2 Problem Summary: This APAR is to address the issue that following db2diag.log Info entry appears when diaglevel not equal to 4 2010-07-13-03.50.31.578000-300 I4F567 LEVEL: Info PID : 4608 TID : 2424 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : KSUFAA APPHDL : 0-33 APPID: *LOCAL.DB2.100712213508 AUTHID : ONEWEBUSER EDUID : 2424 EDUNAME: db2lused (KSUFAA) FUNCTION: DB2 UDB, catalog services, sqlrlCatalogScan::fetch, probe:40 RETCODE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT "LockTimeOut - tran rollback Reason code 68" DATA #1 : Hex integer, 4 bytes 0x00000005 | |
Local Fix: | |
The message can be safely ignored | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem is first fixed in Version 9.7 Fixpack 4 | |
Workaround | |
The message can be safely ignored | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC73201 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.07.2010 29.04.2011 29.04.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |