My Oracle Support Banner

Siebel Replication: Replication Agent (RepAgent) comp is not running after Regional Node Initialization (Doc ID 2081816.1)

Last updated on JUNE 06, 2023

Applies to:

Siebel CRM - Version 8.1.1.14.3 [IP2014] and later
Information in this document applies to any platform.

Symptoms

On : 8.1.1.14.3 [IP2014] version, Remote / Replication / Anywhere


The actual problem reported: After a Full Copy extraction and initialization was done for the Regional Node (RN) but the replication is not working both ways without any errors.

The expected behaviour would be: Once extraction and initialization were completed, the Replication Agent (RepAgent) comp should send and pull the changes to and from the HQ node.


The issue has the following business impact:
Due to this issue, there will be no interchange of data between the HQ and Regional Node(s). The users on RN or HQ will not be able to access most recent data changed on the other node.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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