About continuous replication

Data Integrity Suite

Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

The continuous replication pipeline enables real-time replication of data between systems. It automates the synchronization of data, ensuring that changes made in the source system are immediately reflected in the target system, which is crucial for maintaining data consistency and integrity.

Note: You must have the Replication Designer role to configure and manage replication pipelines. A workspace manager can assign the role from the Manage User page.

Replication project list

The main section of the continuous replication page contains a list of all configured replication project. For each project, you can see details like:

  • Health: Displays a status icon that represents the status across the replication pipeline. This indicator serves as a quick reference to understand the overall health of the system.
  • Project: Displays the name of the project associated with the replication pipeline. This identifies which specific project is being monitored or managed.
  • Engine Processes: Reflects the status of processes running on all runtime servers involved in the replication project. This status provides insight into the operational health of the underlying processes.
    • Partial: Indicates that one or more engine processes are stopped, suggesting that the replication pipeline may not be functioning at full capacity.
    • Stopped: Indicates that the kernel processes on the source server are not running. Projects that have been committed but not deployed will also appear as stopped, indicating a lack of activity.
    • In progress: Indicates a deployment change is actively taking place.
      Note: This status takes precedence over others, except for "Action Required," until the process completes.
    • Unknown: Indicates temporary communication issues between components in the replication pipeline.
    • Ok: Indicates that all server kernel processes are operational and running without issues.
    • Ignored: Displayed when the project is marked as ignored, meaning that its status and processes are not being actively monitored.
  • Replication: Represents the status of replication processes across all runtime servers in the project, reflecting any issues or statuses that may affect data replication.
    • Action Required: Indicates that errors have occurred within the replication pipeline, and immediate attention to resolve issues in one or more replication pipelines related to the project is needed.
      Note: Email notifications are sent to replication designers when the status changes to 'Action Required' for a project, to stay informed and address issues promptly.
    • Partial: Indicates that one or more replication processes are stopped.
    • Stopped: Indicates that replication processes for the pipeline are not running, similar to the Stopped status for engine processes.
    • In progress: Indicates that configuration changes are currently being applied to the replication processes.
      Note: This status overrides all others except "Action Required" until the changes are finalized.
    • Attention: Relevant only to copy-type replication pipelines, this status indicates that copying is ongoing but not all tables are being replicated, suggesting partial activity.
    • Unknown: Indicates temporary communication issues between components in the replication pipeline.
    • Ok: Indicates that all server kernel processes are operational and running without issues.
    • Ignored: Displayed when the project is marked as ignored, meaning that its status and processes are not being actively monitored.
  • Capture: Displays the status of table capturing across all data connections in a replication project, indicating how effectively data is being captured from the source.
    • In progress: Displayed when configuration changes are actively being applied to the table capturing processes
    • Unknown: Indicates that the project is stopped, except in cases where the source connections are exclusively Oracle type.
    • Attention: Indicates that not all selected tables are enabled for capture, suggesting a need for configuration review.
    • Disabled: Indicates that all selected tables have capture disabled, meaning no data is being captured from those tables
    • Ignored: Displayed when the project is marked as ignored, meaning that its status and processes are not being actively monitored.
  • Log Reader: Displays the overall status of the log reader component of the replication project, which is crucial for tracking changes in data.
    • Action required: Displayed when there is a failure or time-out when attempting to start the log reader, requiring immediate attention.
      Note: Email notifications are sent to replication designers when the status changes to 'Action Required' for a project, to stay informed and address issues promptly.
    • Stopped Log reader: Indicates that the log reader has ceased capturing changes, which may disrupt the replication process.
    • In progress: Displayed when configuration changes are being made active for the log reader.
      Note: This overrides all other statuses, except action required, until the configuration changes are active.
    • Unknown: Indicates a temporary communication issue or that the associated runtime server processes are stopped, leading to uncertainty in the status.
    • OK: Indicates that the log reader is active and successfully capturing changes, reflecting a normal operational state
    • Ignored: Displayed when the project is marked as ignored, meaning that its status and processes are not being actively monitored.
      Note: Imported models that are ignored can be started using MonCon. When this happens, the ignored status will be replaced with the actual status of the project.
  • Backlog Rows: Displays the number of rows queued in the source server that are pending replication to the target server. This metric helps in assessing replication workload.
  • Longest Current Latency: Represents the longest time taken from when data is captured on the source server to when it is applied on the target server. This measure helps identify delays in data replication.
  • Last Updated: Displays the time-stamp of the last update for the portlet, indicating the recency of the displayed status information.
    Note: The portlet automatically refreshes every 5 seconds to ensure that the status indicators reflect the most current state of the replication pipeline.

Additional Information

Pipeline Status Indicators: Labels such as Update and No Pipelines provide additional context about the project's status.