Direct SQL Deployment Could Clear Closeness Qualifiers Relationship

(Doc ID 2322921.1)

Last updated on NOVEMBER 01, 2017

Applies to:

Oracle Commerce Merchandising - Version 11.2 and later
Information in this document applies to any platform.
Reported OC version:


Configured Direct SQL Replication per Content Administration Programming Guide > Configuring Repository Replication but having some data inconsistencies related to bidirectional mappings in repositories.

The creation of the assets occurs successfully but when performing an update the relationship table becomes empty in Cat A and B schemas.
An example of the problem can be verified in the closenessQualifiers property in the item descriptor promotion of the repository /atg/commerce/catalog/ProductCatalog.  When creating a promotion with items in the closenessQualifiers and deployment runs successfully, however when editing the same promotion later (e.g. edit the description) and publish the project, the reference table becomes empty.

Following are SQL queries executed before and after deployment of the project to change the description of the promotion.

After publishing project that created promotion with closenessQualifier in closenessQualifiers property:

4. Update the promotion created in Step 1 (e.g. change promo name).

5. Run incremental deployment.

6. Repeat Step 3 --> No records found in dcs_prm_cls_qlf table in CatA and B for the promotion.




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