DB2 - Problembeschreibung
Problem IT07128 | Status: Geschlossen |
AN INITIAL UPDATE OF TEXT INDEX ALWAYS REPORTS CTE0360 ERROR IN DB2DIAG.LOG. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users who use text search. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Please upgrade to DB2 V10.5 FixPack 7 or later. * **************************************************************** | |
Local-Fix: | |
Please ignore the error message in case of initial update of text indexes. | |
Lösung | |
This problem was first fixed in DB2 V10.5 FixPack 7. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 18.02.2015 21.01.2016 21.01.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |