My Oracle Support Banner

Cleaning Stage for ProductCatalogOutputConfig During Baseline Index Takes Long Time For a Particular Environment (Doc ID 1947063.1)

Last updated on OCTOBER 05, 2020

Applies to:

Oracle Commerce Platform - Version 10.1.1 and later
Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 3.1.0 and later
Information in this document applies to any platform.


Baseline indexing is taking much longer in ATG Staging site than ATG Production site although the indexing server uses the same hardware with the same size of heap memory.

For Staging, it takes 4 hours whereas Production it takes 1.5 hours.

The step that takes up most of the time in Staging is when /atg/commerce/search/ProductCatalogOutputConfig_staging is in the CLEANING state.

Per the article, Cleaning Stage for ProductCatalogOutputConfig During Baseline Index Takes Long Time. (Doc ID 1624927.1) deleted records from srch_update_queue table and applied the patch for BUG 18178665 - Cleaning data in srch_update_queue after baseline is taking long time but these steps did not help to speed up the CLEANING process for Staging.

Thread dumps did not show any hung threads.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.