How to Avoid Switching Datasource during BCC Deployment (Doc ID 2216419.1)

Last updated on DECEMBER 20, 2016

Applies to:

Oracle Commerce Merchandising - Version 10.2.0.5 and later
Information in this document applies to any platform.

Goal

For a background, one has built an application on top of Oracle ATG that saves data directly to both switching, CatA and CatB, schemas in a single transaction, also saves to a temporary table.
They have a scheduled job creates a project in BCC, which makes entries to publishing schema using data from the temporary tables and “check in” the project.

This custom process is causing the CatA and CatB data to go out of sync and now they want to stop BCC from switching during publishing and continue publishing to only one datasource.
 

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