|
Problem IC96143
|
Status: Closed |
CLEAR NSE LOG TABLE ENTRIES ON THE VALUE SET FOR COMMITCOUNT |
| product: |
DB2 NET SEARCH / 5765F3800 / A10 - DB2 |
| Problem description: |
The index update crashed after processing 700,000 documents.This
lead to an abort of the complete index update, and the work of
indexing the previous 700,000 documents was lost. Then, the
index update is restarted with intermediate commits to at least
save the work until the crash. This didn't help to find the
'culprit' document as the log table remained unchanged and was
not updated to reflect the already processed documents. Even
though the index now contains several hundred thousand
successfully indexed documents, that work is completely redone. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V10.1 FP3 or later fix pack *
**************************************************************** |
| Local Fix: |
1) Upgrade to ICC indexer and use maxbatchSize parameter to do
indexing in batches
2) Rely on any custom programming technique to find the document
causing the crash. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
|
| Solution |
Upgrade to V10.1 FP3 or later fix pack and follow the below
steps to avail the fix:
export NSE_CLEAR_LOG_ON_COMMIT=TRUE
db2set DB2ENVLIST=NSE_CLEAR_LOG_ON_COMMIT
restart DB2/NSE
issue the incremental index update with COMMIT COUNT set
It is expected to have a slight degradation in the performance
of index update with this fix when
compared to the default behavior due to the overhead involved in
clearing the log table entries per commit. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.09.2013
12.11.2013
12.11.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
