Add and manage replication project - Precisely Data Integrity Suite

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

A replication project consists of multiple pipelines that capture data changes from tables in your dataset. These projects operate in test or production environments, retrieving changed data and applying it to target sources.

What's changed: In the new user experience, Create appears as Add Project when you create a replication project. Some project details, alert filters, action labels, and options have also changed, including Project name, Replication engine, Pipeline, Backlog and Latency, Create Bundle, Debug, and Export selected. For more information on the new experience, see About the new user experience.

Add, edit, and view replication project

Add replication project

  1. Navigate to Integration > Continuous Replication and click + Add Project.
  2. Enter a unique name for the project.
    Note: The project name cannot be changed once created. Modifications can only be made through import or export.
  3. Enter a brief description (optional).
  4. Click Create. The new project appears in the projects pane.

Edit replication project

  1. Click the ellipsis next to the project and select Edit.
  2. Modify the description as needed.
  3. Click Save.
    Note: If the project has been committed at least once, saving creates a new configuration file. To implement changes, commit to the server(s) and redeploy the project.

View replication project details

Click the ellipsis next to the project and select Details to view:

  • Project Name: The unique name of the project.
  • Description: Brief overview of the project.
  • Replication Engine: Details of the associated replication engine.
  • Created By: User who created the project.
  • Last Refreshed: Timestamp of the last refresh.

    To view alerts, click Alerts. Click Cancel to close.

  • Statuses: Current statuses of engine processes, replication, and capture.

On the same page, navigate to the Backlog tab to view the number of data rows waiting to be processed.

Start and stop replication project

Start a replication project

Before starting, ensure you have validated, committed, and deployed any configuration changes.

Note:
  • You can only start one project at a time.
  • If the project is currently deploying, wait for deployment to finish.
  • If the project status is Ignored, you must stop ignoring it first. For imported models, the project can be started regardless of its ignored status.
  • Once started, the project remains active until stopped.
  1. Navigate to Integration > Continuous Replication.
  2. Click the ellipsis next to the project and select Start.
  3. Click Start again to confirm.
    Note: If Start is unavailable, the project may be deploying, already started, or more than one project is selected.

When restarting a previously stopped project:

  • Data flows resume from where they were interrupted.
  • Change data capture starts for all enabled tables (Oracle databases).
  • Log readers that were stopped are restarted.
  • Data flow replication and copy processes on the runtime servers are started.

Stop a replication project

Stop a project before any of the following activities:

  1. Shutting down the source database or rebooting the host server for maintenance.
  2. Rebooting the kernel host server when the kernel runs on a remote system.
  3. Changing the runtime engine IP/hostname: If not stopped first, edit the engine properties to match the changes and redeploy.
  4. Clearing replication backlogs for any pipeline.
  5. Modifying the metabase (add, upgrade, or delete).
  6. Deleting or ignoring the project.
  7. Running a forced deployment.

When a project is stopped:

  • The associated kernels on the runtime servers shut down.
  • Change data capture is suspended for Oracle sources.
  • Replication and copy processes on the runtime engine are stopped.
  • Active log readers are stopped.
Note: You can only stop one project at a time. If the project is deploying, wait for deployment to finish.
  1. Navigate to Integration > Continuous Replication.
  2. Click the ellipsis next to the project and select Stop.
  3. Click Stop again to confirm.

After stopping, verify that all statuses show as stopped in the projects pane.

View replication project alerts

View alerts to identify issues, track anomalies, and determine what action may be needed on runtime servers. Alert icons indicate severity:

  • Yellow exclamation: Warning — does not affect replication (for example, duplicate kernel entries).
  • Blue information: Informational — events during normal kernel operation.
  • Red cross: Error — critical issues requiring immediate attention.
  1. Navigate to Integration > Continuous Replication.
  2. Click the ellipsis next to the project and select Alerts. The Alerts window opens with the following filters:
    • Message type: Filter by warning, error, informational, etc.
    • Runtime engine: Filter alerts by engine.
    • Pipeline Name: Filter alerts by pipeline.
    • Search: Search by pipeline name, message type, or other criteria.

    The alerts table shows:

    • Message: Alert message details.
    • Replication Engine: Engine associated with the alert.
    • Pipeline Name: Pipeline affected by the alert.
    • Logged: Timestamp when the alert was logged.
    • Refresh / Last refreshed: Manually refresh the grid; shows the time of the last refresh.
    • Close: Closes the alerts window.
    Note: If CDC is down, you will see: An unexpected error occurred. Try the request again. If the problem persists, contact support. Latest alerts will not be available.

Validate replication project configuration

Validation checks for errors and inconsistencies before committing to runtime servers. Results are prioritized by severity and include error and warning counts. Checks include: metabase installation and version, table and column mapping accuracy, data connection validity, and source database availability.

  1. Navigate to Integration > Continuous Replication.
  2. Click the ellipsis next to the project and select Validate.
  3. Review the Validation Results section. If errors prevent commitment, use the details to resolve them.
  4. Click Copy to Clipboard to copy results for sharing.
  5. Click Close.

Apply configuration changes

Deploying activates the latest committed configuration on all runtime servers. You can batch configuration changes over several days and deploy at a convenient time, such as off hours.

  1. Navigate to Integration > Continuous Replication.
  2. Click the ellipsis next to the project and select Apply Configuration Changes.
  3. Select one or more options:
    • Stage configuration changes: Commit changes for all replication pipelines.
    • Make Configuration Changes Active: Deploy changes for all replication pipelines.
    • Display alerts to monitor progress: Opens the Alerts dialog after clicking Apply.
    • Force making configuration changes active: Forces changes to become active.
  4. If Force making configuration changes active is selected, configure the timeout fields:
    • Backlog is empty: Time for backlog to clear before deployment starts (default: 4 minutes).
    • Dataset capture is disabled: Time for capture to disable (default: 8 minutes).
    • Replication is stopped: Time for replication to stop (default: 4 minutes).
  5. Click Apply.
    Note: Apply is enabled only if Stage Configuration Changes and/or Make Configuration Changes Active are selected.

Manage diagnostic bundles

Diagnostic bundles collect logs, configuration, and connection information for a project across all runtime engines. Use bundles for troubleshooting or to share with Support.

  1. Navigate to Integration > Continuous Replication.
  2. Click the ellipsis next to the project and select Manage Diagnostic Bundle. The Diagnostic Bundles page opens listing all bundles in the current workspace.

Create a diagnostic bundle

  1. Click + Create Bundle.
  2. Enter a name and description. For the list of collected log files, see Relevant log files for support.
  3. Click Create.
    Note: The bundle is created at the path shown in Location of bundle and written to a zip file.

View a diagnostic bundle

Click a bundle link on the Diagnostic Bundles page to open the Diagnostic Bundle Details view (status, creation date/time, creator, and file location).

Stop a diagnostic bundle

  1. Select one or more in-progress bundles from the Diagnostic Bundles page.
  2. Click Stop and confirm. Already-retrieved files are kept and a partial zip is created with status set to partial.

Delete a diagnostic bundle

  1. Select one or more bundles that are not in progress.
  2. Click Delete and confirm.

Debug and export replication project

Debug a replication project

When debugging is enabled, warnings, errors, and details for all kernel and listener processes are written to kernel logs on the runtime engine.

  1. Navigate to Integration > Continuous Replication.
  2. Click the ellipsis next to the project and select Debug.
  3. Select a debug mode:
    • Standard: General replication project information.
    • SQL: SQL statement details.
    • Both: Standard and SQL combined.
    • None: No debug output (default).
  4. Click OK.

Export project

  1. Navigate to Integration > Continuous Replication.
  2. Select the checkboxes for the projects to export.
  3. Click Export selected projects.
  4. Choose All projects or Selected projects.
  5. Check Export user names if needed.
  6. Choose a zip file location and click Export.
    Note: Default filename: <ProjectName>-MMDDYYYY-HHMMSS for a single project; ConnectConfiguration-MMDDYYYY-HHMMSS for multiple projects.
    Warning: You cannot export if the filename field is blank.