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

Last updated on DECEMBER 22, 2016

Applies to:

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

Symptoms

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.

 

Steps:
---------
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

Error:
-------
This warning shows up 3 times:

Contains
    BrandToDimensionOutputConfig.ser
  CategoryToDimensionOutputConfig.ser
  PromotionToDimensionOutputConfig.ser
But there is no
   ProductCatalogOutputConfig.ser

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

Changes

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

Cause

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