IBM Support

PJ45150: CSS CLEANUP MECHANIZE OF *.WDG FILES IS NEEDED

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Large number of *.wdg files is being accumulated in the
    index/collection folder. The content of each file is 'I can
    write!" from the CSS server when it checks on the share .
    Customer system has more than an thousand files that were
    created just today and he was doing manual deletes and asking
    when it will be addressed in the product.
    
    Please review the *.wdg  file cleanup mechanism and make it more
    aggressive so it does not leave a such heavy footprint .
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of 5.2.1.7-P8CSS and 5.5.0.0-P8CSS and prior releases  *
    * on all supported platforms.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * On the CSS/ECMTS server customers notices an extremely large *
    * number (hundreds sometimes thousands) of old .wdg "watchdog" *
    * files in the file system collection directory (e.g.          *
    * C:\os1_cssindex1\os1_Document_20171214154221_496A66B408344C2 *
    * 994767CE87647230F).  While it is common and expected for     *
    * many (possibly dozens) of these files to be present during   *
    * indexing/search operations, one for each commit point in the *
    * index, they should be regularly "cleaned up" as commit       *
    * points are removed.  However this was not always adequately  *
    * done resulting in some customer collections accumulating a   *
    * large number of files.  Functionally there would be no       *
    * impact to the excessive number of .wdg files past taking up  *
    * disk space.                                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to 5.2.1.7-P8CSS-IF001 or 5.5.1.0-P8CSS or higher.   *
    ****************************************************************
    

Problem conclusion

  • Fixed in 5.2.1.7-P8CSS-IF001 and 5.5.1.0-P8CSS and higher.
    
    CSS/ECMTS watchdog cleanup code was modified to more thoroughly
    remove the obsolete .wdg files when corresponding commit points
    were removed.  In addition, while indexing operations occur, a
    twice daily check is done for orphaned .wdg files which are
    removed if no corresponding commit point is present.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ45150

  • Reported component name

    CONTENT SEARCH

  • Reported component ID

    5724R8109

  • Reported release

    521

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-10

  • Closed date

    2018-03-15

  • Last modified date

    2018-03-15

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

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

Fix information

  • Fixed component name

    CONTENT SEARCH

  • Fixed component ID

    5724R8109

Applicable component levels



Document information

More support for: FileNet Content Manager
Content Search Services

Software version: 5.2.1

Reference #: PJ45150

Modified date: 15 March 2018


Translate this page: