My Oracle Support Banner

Full Deployments Are Causing Large SRCH_UPDATE_QUEUE, Which Is Causing Search Indexes To Take Longer Than Expected (Doc ID 1474507.1)

Last updated on FEBRUARY 04, 2019

Applies to:

Oracle ATG Web Commerce Search - Version 10.0 to [Release 10]
Information in this document applies to any platform.


Performing a Content Administration (CA) Full Deployment is causing the /atg/search/repository/IncrementalItemQueueRepository.item (srch_update_queue table) to fill up. Consequently, Search indexes are taking an extraordinarily long amount of time to complete and may have appear to hang. If the srch_update_queue is truncated prior to running the Search Full Index, the index completes in a fraction of the time.  

Thread dumps taken when the problem is happening will show that the index is trying to clean up, meaning delete the entries in the srch_update_queue table.

Thread from SearchAdmin instance:


The configuration has been confirmed as follows...

-- All instances have their ProductCatalogOutputConfig.IncrementalUpdateSeconds=-1
-- And enableIncrementalLoading=false for those same IOCs
-- The only exception to the above is the ProductCatalogOutputConfig.enableIncrementalLoading on the instance SearchAdmin is using for its {Search_Project}-> Content Set.


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
 Thread from SearchAdmin instance:
 Thread from indexing server:
 For versions prior to ATG

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