Workbench Becomes Unresponsive During Baseline_update Operations

(Doc ID 2398308.1)

Last updated on MAY 17, 2018

Applies to:

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

Goal

On : 3.1.2 version, Indexing and Search (Data Ingest, CAS, MDEX, Forge, Dgidx)

Is it expected behavior that the Workbench be unavailable for approximately 30 seconds during the distribution step that occurs after the Dgidx indexing process?

Why is our workbench unresponsive after we trigger a baseline or partial update.
 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms