My Oracle Support Banner

Partial Update does not Remove Records from the Index while Baseline Update does Remove Records (Doc ID 1988983.1)

Last updated on APRIL 03, 2019

Applies to:

Oracle Commerce Platform - Version 10.1.2 and later
Information in this document applies to any platform.


When you switch off site membership for a SKU it is not removed from the MDEX after a partial update.

Baseline update removes the sku.

The partials/forge_output file is 0kB (when there are no other changes).

You have already verified that
Bug 14113907 - directory for serialization is missing in the standalone deployment
is not affecting your system.


1. Set up a SKU that is a member of siteA but not siteB
2. Do baseline update.
3. Edit the SKU such as to make it not valid on siteA
4. incrementally deploy the project.
5. trigger a partial update
6. The SKU still remains associated to siteA in the MDEX

This warning shows up 3 times:


But there is no

Expected Behavior:
The SKU record for siteA should no longer be in the MDEX

Actual Behavior:
The SKU still remains associated to siteA in the MDEX


No recent changes in configuration, this is a product defect present in Oracle Commerce Endeca Integration versions. 


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.