My Oracle Support Banner

CSC Incremental Indexing Job Takes Long Time due to Slow Query (Doc ID 2021763.1)

Last updated on JULY 11, 2018

Applies to:

Oracle Commerce Service Center - Version 11.1 and later
Information in this document applies to any platform.

Symptoms

Oracle Commerce Service Center (CSC) 11.1 scheduled incremental indexing job may take long time, and sometimes it can run for several hours. To check if a slow merge query is running during indexing, please enable loggingDebug on following component on indexing server:

In this case, you can disable the timeout temporarily to reveal the problematic merge query and confirm you encounter the same problem this article describes. There are three possible places that this connection timeout may be set:

  1. JDBC data source configuration
  2. JVM commandline parameter, e.g. -Doracle.jdbc.ReadTimeout 600
  3. jdbcQueryTimeout property of ProfileOutputConfig, OrderOutputConfig or other components, if any, of IndexingOutputConfig class

Please back up the value before disable it so you can put it back after the merge query performance issue is resolved.

After the timeout is disabled, you should see the above lengthy running merge query in the log without socket read timeout exception.

Changes

Version 11.1 added a new component /atg/textsearch/indexing/operation/<db_type>/MergeStagingToTokens that stores merge query in its SQL property. This query is executed whenever incremental indexing runs.

Cause

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
Symptoms
Changes
Cause
Solution
 1. Upgrade to a Version with This Fix
 2. Configure Incremental Indexing Components
 3. Resolve Long Token Issue
 4. If you have disabled Socket read timeout previously, restore the change
References


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