You can initiate or terminate a replication project to manage the data replication process. Starting the project begins data transfer according to the defined configurations, while stopping it halts replication for maintenance or configuration adjustments. You can monitor the status of the replication during these operations to ensure successful execution or identify issues.
Start a replication project
Before starting a project, ensure that you have validated, committed, and deployed any configuration changes to your environment.
- You can only start one project at a time.
- If the project is currently in the deployment process, you cannot start it until the deployment finishes.
- If the project status is set to 'Ignored', you must stop ignoring it before you can start the project. For imported models, the project can be started regardless of its ignored status in Data Integration.
- Once started, the project remains continuously active until it is stopped.
To start a replication project:
- Navigate to Integration Continuous Replication.
- Click the ellipses next to the project you wish to start, then select Start from the dropdown menu. This will open start project window.
- Click Start again to confirm.Note: If the start option is unavailable, it may be due to one of the following reasons:
- The project is currently deploying.
- The project is already started.
- You have selected more than one project.
- Any project data flows that were running when the project was stopped are restarted and processing resumes at the point where it was interrupted.
- Change data capture is started for all enabled tables for Oracle databases.
- Any associated log readers that were stopped when the project was stopped are restarted.
- Data flow replication and copy processes on the runtime servers are started.
Stop a replication project
You can manually stop a replication project at any time after it has been started. It is important to stop a project before performing the following activities in your data capture and replication environment:
- Shutting down the source database: Stop the project before shutting down the source database or rebooting the host server for maintenance.
- Rebooting the kernel host server: If the kernel is running on a remote system, ensure the project is stopped before rebooting the host server.
- Changing runtime engine IP/hostname: Stop any replication project using the runtime engine prior to making changes to its primary or alternative IP address/hostname. If not stopped, you will need to edit the engine's properties to match the changes and redeploy the project.
- Clearing replication backlogs: Stop the project before clearing replication backlogs for any project's replication pipeline.
- Modifying the metabase:Stop the project if you plan to add, upgrade, or delete a metabase associated with it.
- Deleting or ignoring the project: Stop the project before deletion or when setting it to ignored.
- Running a forced deployment: Ensure the project is stopped before executing a forced deployment.
Effects of stopping a project
When you stop a replication project, the following actions occur:
- The associated kernels on the runtime servers shut down.
- Change data capture is suspended for Oracle sources.
- Replication is suspended, and copy processes on the runtime engine are stopped.
- Any active log readers are also stopped.
Steps to stop a replication project
- Navigate to Integration Continuous Replication.
- Click the ellipses next to the project you wish to start, then select Stop from the dropdown menu. This will open stop project window.
- Click Stop again to confirm.
After stopping the project, return to the projects pane to verify that all statuses are displayed as stopped.