DB2 - Problem description
Problem IT06662 | Status: Closed |
AN INITIAL UPDATE OF TEXT INDEX ALWAYS REPORTS CTE0360 ERROR IN DB2DIAG.LOG. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
The error messages like below are recorded in db2diag.log. 2011-12-07-14.32.30.916579+540 I2275A421 LEVEL: Error PID : 1364210 TID : 1 PROC : db2text INSTANCE: db2inst1 NODE : 000 APPID : *LOCAL.db2inst1.111207053234 EDUID : 1 FUNCTION: DB2 UDB, Net Search Extender, CteUpdateCommand::updateTextIndex, probe:99 MESSAGE : CTE reason DATA #1 : Hexdump, 4 bytes 0x00000001100C5318 : 0000 0168 ...h 2011-12-07-14.32.30.917078+540 I2697A410 LEVEL: Error PID : 1364210 TID : 1 PROC : db2text INSTANCE: db2inst1 NODE : 000 APPID : *LOCAL.db2inst1.111207053234 EDUID : 1 FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary logging fu, probe:0 MESSAGE : Message DATA #1 : String, 59 bytes CTE0360 "Disk Space Check was skipped for NSE index update" This error message is reported always when initial update of text index in V9.7 FixPack 5. NSE expects this message when incremental updates with SKIPDISKSPACECHECK option, the message level will be lower to Info when initial updates. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users who use NSE. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Please upgrade to DB2 V10.1 FixPack 5 or later. * **************************************************************** | |
Local Fix: | |
Please ignore the error message in case of initial update of text indexes. | |
Solution | |
This problem was first fixes in DB2 V10.1 FixPack 5. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.01.2015 14.07.2015 14.07.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.5 |