Monitor Multiple Replication Projects

Replication projects run in your test or production environment to capture data changes on sources, retrieve the changed data, and apply target stream. See Manage Replication Pipeline.

View Replication Alerts

View alerts for a replication project active in Data Integration to help identify important issues, track anomalies, and see what action may need to be taken on one or more runtime servers. For example, if a replication project encounters interruptions, view the alerts to determine whether any source or target systems have shut down.
  1. To open a replication project, click from the top of the menu and select Alerts. The Alerts page opens.
  2. Filter the Alerts by selecting a component from the dropdown list.
  3. Click Close.

Start All Replication Projects

When you stop a project to perform maintenance in your production environment, you can then manually restart it again. Before you start a project, you must always validate, commit, and deploy configuration changes to your environment.
  • You start one project at a time.
  • If the project is currently deploying, you cannot start it until deployment finishes.
  • If the project status is set to ignored, you must stop ignoring the project before you can start it. If the ignored project is an imported director model, it can be started in Director regardless of its ignored status in Data Integration.
  • When you start the project it remains continuously active until it is stopped.
Note: You do not need to deploy when starting a project for the first time.
When you start a replication project, the following occurs, depending on whether you start a project for the first time or restart a project previously stopped:
  • Starting new projects:
    • The associated kernels are started on the runtime servers, if not already started. Starting the kernel activates the processes for replicating changed data to your Kafka target.
    • When a log reader is associated with the project, if the log reader is stopped when the project is started for the first time and there are data tables enabled for capture, the log reader will automatically start warm.
  • Restarting previously stopped projects:
    • 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.
  1. To open a replication project, click from the top of the menu and select Start All. The Start Replication Pipeline page opens.
  2. Filter the Replication Projects portlet to locate the project you want to start.
  3. Select the project and click Start. The Start Project window opens.
    Note: If the Start button is unavailable, the project is currently deploying and cannot be started, the project is already started, or you selected more than one project.
  4. Do one of the following:
    • Click Start to start the project. One of the following occurs:
      • If there are no errors, the window closes. The start process may take a few seconds to finish, after which the statuses for the project (except for Capture) show as OK.
      • If there are problems with the starting the project, an error message displays alerting you to the problems.
    • Click Cancel to close the window without starting the project.

Stop All Replication Projects

After you start a project, you can manually stop it at any time.
You must stop a project before you perform the following activities in your data capture and replication environment:
  • Shutting down the source database, or rebooting the host server where the database is running to perform database or operating system maintenance.
  • If the kernel is running on a remote system, rebooting the host server where the kernel is running.
  • Making changes to the runtime server's primary or alternative IP address/hostname. You must first stop any replication project using the runtime server to avoid problems connecting to the server. If you do not stop the projects, afterward you will need to edit the server properties in Connect portal to match the changes and redeploy the project. For imported Connect CDC Director models, you will need to remove the model and then re-import it. As a best practice, it is recommended that you avoid changing IP addresses on any runtime servers used by Connect portal projects.
  • Clearing replication backlogs for any project data flows.
  • Adding, upgrading, or deleting a metabase associated with the project.
  • Deleting the project.
  • Ignoring the project.
  • Running a Forced deployment.
When you stop a replication project, the following occurs:
  • The associated kernels on the runtime servers shut down.
  • Change data capture is suspended for Oracle sources.
  • Replication is suspended and copy processes are stopped on the runtime servers.
  • Any associated log readers that were started are stopped.

You stop one project at a time. If the project is currently deploying, you cannot stop it until deployment finishes.

  1. To open a replication project, click from the top of the menu and select Stop All The Stop Replication page opens.
  2. Select the project and click Stop. The Stop Project window opens.
    Note: If the Stop button is unavailable, the project is currently deploying and cannot be stopped, the project is already stopped, the project is ignored, or you selected more than one project.
  3. Do one of the following:
    • Click Stop to stop the project. The window closes. On the Replication Projects portlet, all statuses should show as Stopped for the project.
    • Click Cancel to close the window without stopping the project.

Validate Replication Projects Configurations

Validation generates results which include details about problems found, prioritized by severity, and the number of errors and warnings that would occur if you committed the configuration. If the results are not what you expected, you can modify the configuration and validate again.

After you make changes to the configuration of your replication project, or before you start your project, validate the project properties to check for possible problems before committing the changes to the runtime servers. Validation checks project details like whether the metabase is installed and the version is correct, all data flow tables and column mapping information is correct, the data connections are valid, and the source database is online and running.
  1. To open a replication project, click from the top of the menu and select Validate. The Validate Configuration page opens with the name and description of the project being validated.
  2. Review the text in the Validation Results section.

    If you cannot commit the project due to errors, this section includes information to help you resolve problems that need attention.

  3. Click Copy to Clipboard icon to copy the text and paste into another application to share.
  4. Click Close.

Apply Configuration Changes

Deploying activates the latest committed configuration on all runtime servers in the project. The deployment process enables you to deploy changes when it is convenient. For example, you may save and commit multiple configuration changes over the course of a few days then decide to deploy those changes during off hours, such as over the weekend.
  1. To open a replication project, click from the top of the context menu and select Apply Configuration Changes. The Apply Configuration Changes page opens.
  2. Select one or all of the following options:
    OptionDescription
    Stage configuration changes

    Commit the configuration changes for all replication pipelines.
    Make Configuration Changes Active

    Deploy the configuration changes for all replication pipelines.
    Display alerts to monitor progress

    Displays the Alerts dialog once the Deploy action is clicked.
    Force making configuration changes active

    Forces the configuration changes to be active
  3. If the option Force making configuration changes active is selected, the following are required fields:
    OptionDescription
    Backlog is empty

    The backlog must empty within this time or the deployment will not start.

    The default value is: 4 minutes.
    Table capture is disabled

    Time allowed for the table capture status to be disabled for the deployment to start.

    The default value is: 8 minutes.
    Replication is stopped

    Replication processes must be stopped within this time or the deployment will not start.

    The default value is: 4 minutes.
  4. Click Apply.
    Note: Apply is enabled only if Stage Configuration Changes and/or Make Configuration Changes Active are selected.

Debug Replication Project

When you enable debugging, project and SQL statement warnings, errors, and other details are collected for all kernel and listener processes on all runtime servers used by the project or for a single runtime server in the project, depending on how you configure debugging. The details are written to kernel logs, which are text files located in the software install kernel subdirectory on the runtime engine.
  1. To open a replication project, click from the top of the context menu and select Debug. The Debug Project page opens with the project name, description, and additional information about the runtime engine.
  2. Select one or all of the following options:
    OptionDescription
    Standard

    View general replication project information.
    SQL

    View specific information about SQL statements.
    Both

    View debugging information about Standard and SQL.
    None No debugging information is written to the kernel logs.
    Note: None is the default value.
  3. Do one of the following:
    • Click Cancel to close the window without saving your selection.
    • Click OKto save your debug selection and close the window.
      Note: If any runtime engine and/or kernels are not active, an error displays showing which engines are not running. Check the kernels, start them as needed, and run this procedure again.
      .

Manage Diagnostic Bundles

Displays a list of the diagnostic bundles created for any project in the current workspace. All users with permissions to view pipelines/projects will have the ability to create and view bundles.

Create Diagnostic Bundles

  1. To open a replication project, click from the top of the context menu and select Manage Diagnostic Bundles. The Diagnostic Bundles page opens.
  2. Click Create Bundle. The Create Diagnostic Bundle page opens with information about bundle name, replication agent, and files collected for the bundle.
  3. Enter a description for the bundle.
  4. Click Create.

Stop Diagnostic Bundles

Stops the selected diagnostic bundles that are in progress. Files already retrieved are kept, a zip file is created and the status of the bundle is set to 'partial'.
  1. From the Diagnostic Bundles screen, click to open the Stop Diagnostic Bundle page.
  2. Click Stop.

Delete Diagnostic Bundles

Stops the selected diagnostic bundles that are in progress. Files already retrieved are kept, a zip file is created and the status of the bundle is set to 'partial'.
  1. From the Diagnostic Bundles screen, click Delete to open the Delete Diagnostic Bundle page with information about bundles.
  2. Click Delete.

View Diagnostic Bundles Details

Displays information about one diagonostic bundle such as status, creation date/time, user who created it, and the location of the file itself.
  1. From the Diagnostic Bundles screen, click a link of diagnostic bundle to open the Diagnostic Bundle Details page with information about bundles.
  2. Click Close.