|
Problem IC65587
|
Status: Geschlossen |
Event view log is not accurate when UPDATE INDEX for a text search index finds empty documents in the document set. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* all platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* When UPDATE INDEX for a text search index findsempty *
* documents in the set of documents it operates on,thereare *
* scenarios where the summary logged in the event view isnot *
* accurate.The count for the number of empty documentsskipped *
* is always reported as "0" for cases when the updateindex *
* operation is an incremental update. Consequently, thesum of *
* the documents inserted, documents updated, documentsdeleted, *
* empty documents skipped and the documents notindexedwill not *
* add up to the number of rows being reported asprocessed. *
* Initial updates are not affected by thisproblem.For *
* example:After completion of an incrementalupdate, the record *
* in the event view is:-2009-10-23-17.42.18.850674 1 *
* 0CIE00005IDB2 Text Search Index update statistics: *
* "138644"number ofrows processed. "112434" documents *
* inserted, "0"documentsupdated, "0" documents deleted, "0" *
* empty documents skippedsuccessfully, and "0" documents not *
* indexed due to documenterrors.The correct record should have *
* been:-2009-10-23-17.42.18.850674 1 *
* 0CIE00005IDB2 Text Search Index update statistics: *
* "138644"number ofrows processed. "112434" documents *
* inserted, "0"documentsupdated, "0" documents deleted, *
* "26210" empty documentsskipped successfully, and "0" *
* documents not indexed due todocument errors. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.5 Fix Pack 6 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
This problem is fixed in DB2 Version 9.5 Fix Pack 6. Users
should be able to see the number of skipped empty documents in
the event view.
Following is an example of what a user would see in the event
view:
- 2009-10-23-17.42.18.850674 1 0 CIE
00005I DB2 Text Search Index update statistics: "138644"
num
ber of rows processed. "112434" documents inserted, "0"
doc
uments updated, "0" documents deleted, "26210" empty
doc
uments skipped successfully, and "0" documents not indexed
due
to document errors. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Kommentar |
Problem fixed in a Fix Pack. |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC65738
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 14.01.2010
22.06.2010
22.06.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.FP6
|
| Problem behoben lt. FixList in der Version |
