|
Problem IC65738
|
Status: Closed |
Event view log is not accurate When UPDATE INDEX for a text search index finds empty documents in the document set. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When UPDATE INDEX for a text search index finds empty documents
in the set of documents it operates on, there are scenarios
where the summary logged in the event view is not accurate. The
count for the number of empty documents skipped is always
reported as "0" for cases when the update index operation is an
incremental update. Consequently, the sum of the documents
inserted, documents updated, documents deleted, empty documents
skipped and the documents not indexed will not add up to the
number of rows being reported as processed. Initial updates are
not affected by this problem.
For example:
After completion of an incremental update, the record in the
event view is:
- 2009-10-23-17.42.18.850674 1 0
CIE00005I DB2 Text Search Index update statistics: "138644"
number of rows processed. "112434" documents inserted, "0"
documents updated, "0" documents deleted, "0" empty documents
skipped successfully, and "0" documents not indexed due to
document errors.
The correct record should have been:
- 2009-10-23-17.42.18.850674 1 0
CIE00005I DB2 Text Search Index update statistics: "138644"
number of rows processed. "112434" documents inserted, "0"
documents updated, "0" documents deleted, "26210" empty
documents skipped successfully, and "0" documents not indexed
due to document errors. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* When UPDATE INDEX for a text search index finds *
* emptydocumentsin the set of documents it operates on, there *
* are scenarioswhere the summary logged in the event view is *
* not accurate.Thecount for the number of empty documents *
* skipped is alwaysreported as "0" for cases when the update *
* index operation isanincremental update. Consequently, the *
* sum of the documentsinserted, documents updated, documents *
* deleted, emptydocumentsskipped and the documents not indexed *
* will not add up to thenumber of rows being reported as *
* processed. Initial updatesarenot affected by this *
* problem.For example:After completion of an incremental *
* update, the record in theevent view is:- *
* 2009-10-23-17.42.18.850674 1 0CIE00005I *
* DB2 Text Search Index update statistics: "138644"number of *
* rows processed. "112434" documents inserted, "0"documents *
* updated, "0" documents deleted, "0" emptydocumentsskipped *
* successfully, and "0" documents not indexed due todocument *
* errors.The correct record should have been:- *
* 2009-10-23-17.42.18.850674 1 0CIE00005I *
* DB2 Text Search Index update statistics: "138644"number of *
* rows processed. "112434" documents inserted, "0"documents *
* updated, "0" documents deleted, "26210" emptydocuments *
* skipped successfully, and "0" documents notindexeddue to *
* document errors. *
****************************************************************
* RECOMMENDATION: *
* upgrade to V97FP2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
V97FP2 will have this fix
number of empty documents skipped will be displayed in the event
table |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.01.2010
31.05.2010
31.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
