IBM Support

JR50129: Preprocess/buildindex takes a long time

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If your catalog is very large, preprocess and buildindex can
    take a very long time.
    

Local fix

Problem summary

  • If your catalog is very large, preprocess and buildindex can
    take a very long time.
    

Problem conclusion

  • This APAR introduces sharding to preprocess/buildindex, to split
     up buildindex/preprocess into multiple parallel processes (key
    split on catentry_id). Each preprocess shard has it's own set of
     temporary preprocess tables, and each buildindex shard is it's
    own separate index. At the end of buildindex, a 'merge' command
    is run to combine the shards into one final index. Please refer
    to the additional steps in the APAR readme for setting up
    sharding and merging.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR50129

  • Reported component name

    WC BUS DEV ED W

  • Reported component ID

    5724I3900

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-02

  • Closed date

    2015-08-06

  • Last modified date

    2015-08-06

  • 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

    WC BUS DEV ED W

  • Fixed component ID

    5724I3900

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSYT2H","label":"WebSphere Commerce Developer Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB31","label":"WCE Watson Marketing and Commerce"}}]

Document Information

Modified date:
11 December 2021