Siebel Replication: Custom Extension (CX_) Table Data Is Not Replicated From HQ To Regional Node (Doc ID 2913170.1)

Last updated on DECEMBER 19, 2022

Applies to:

Symptoms

On a Production environment, the Siebel Replication was not working for a Custom Extension table (CX_* table).
Changes to the data records from this table were not reflecting on the Regional Node (RN) database despite the fact that all the Remote and Replication components were running with no errors.


The expected behaviour was here that normally, all the business data changes from the HQ (Headquarters) Server Database for the 'Full Copy' routing model should be reflecting in the Regional Server Database as well.

That could be reproduced at will in that specific environment by using the following steps:
1. (optional, if not already in place) Create and Deploy such a Custom Extension (CX*) table on both databases (HQ and RN);
2. Make some changes to data records in this table via Siebel UI (insert / update some records);
3. Check for the changes after Replication Agent (RepAgent) component runs for some time - and compare the table contents on each database.

The impact for the end-users would be that they may not see consistent data on that table in both HQ and RN Databases as long as these changes are not replicated.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.