CSC Incremental Indexing Job Takes Long Time due to Slow Query
Last updated on JULY 05, 2017
Applies to:Oracle Commerce Service Center - Version 11.1 and later
Information in this document applies to any platform.
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:
- JDBC data source configuration
- JVM commandline parameter, e.g. -Doracle.jdbc.ReadTimeout 600
- 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.
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms