IC87467: CLEAR NSE LOG TABLE ENTRIES ON THE VALUE SET FOR COMMITCOUNT

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error 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.
    

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.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * By default, NSE log table will be cleared only at the end of *
    * update index processing.                                     *
    * If you would like to clear the log table once the commit is  *
    * finished ( for                                               *
    * incremental index update with commit count value set ), you  *
    * should set the environmental                                 *
    * variable "NSE_CLEAR_LOG_ON_COMMIT" before updating the       *
    * index. Here are the steps:                                   *
    *                                                              *
    * 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     *
    ****************************************************************
    

Problem conclusion

  • 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.
    3) Upgrade to V9.7 FP8 or later
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC87467

  • Reported component name

    DB2 NET SEARCH

  • Reported component ID

    5765F3800

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-25

  • Closed date

    2013-03-28

  • Last modified date

    2013-03-28

  • APAR is sysrouted FROM one or more of the following:

    IC86768

  • APAR is sysrouted TO one or more of the following:

    IC95998 IC96141 IC96143 IC96144

Fix information

  • Fixed component name

    DB2 NET SEARCH

  • Fixed component ID

    5765F3800

Applicable component levels

  • R970 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for Linux, UNIX and Windows
Extenders - Net Search Extender

Software version:

9.7

Reference #:

IC87467

Modified date:

2013-03-28

Translate my page

Machine Translation

Content navigation