Skip to main content

Data Errors

Click the Data Errors sub-tab and then click Change to Task Policy to configure the following:

  • For a data truncation error: Click the triangle to open the list and select what happens when an truncation occurs in one or more specific records. You can select one of the following from the list:

    • Ignore record: The task continues and the error is ignored.
    • Log record to the exceptions table (default): The task continues and the error is written to the exceptions table.
    • Suspend table: The task continues but data from the table with the error record is moved into an error state and its data is not replicated
    • Stop task: The task is stopped and manual intervention is required.
Information note

Data truncation error handling is only supported in the following cases:

  • Replication is to the following target endpoints: MySQL, PostgreSQL, Oracle, Microsoft SQL Server, SAP Sybase ASE, File, Amazon Redshift, Microsoft Azure Database for PostgreSQL, Google Cloud SQL for PostgreSQL, Microsoft Azure Database for MySQL, Google Cloud SQL for MySQL, and Microsoft Azure SQL Database

  • Change Processing replication only (i.e. not Full Load)

  • For other data errors: Click the triangle to open the list and select what happens when an error occurs in one or more specific records. You can select one of the following from the list:

    • Ignore record: The task continues and the error is ignored.
    • Log record to the exceptions table (default): The task continues and the error is written to the exceptions table.
    • Suspend table: The task continues but data from the table with the error record is moved into an error state and its data is not replicated
    • Stop task: The task is stopped and manual intervention is required.
  • Escalate error handling when other data errors reach (per table): Select this check box to escalate error handling when the number of non-truncation data errors (per table) reaches the specified amount. Valid values are 1-10,000.

    Information note

    The escalation options are not available when the Apply changes using SQL MERGE task setting is enabled.

    • Escalation action: Choose what action Replicate should perform when error handling is escalated. Note that the available actions are dependent on the action selected from the For other data errors drop-down list described above.

      • Log record to the exceptions table: The task continues and the error is written to the exceptions table.
      • Suspend table (default): The task continues but data from the table with the error record is moved into an error state and its data is not replicated.

        Information note

        The behavior differs according to the Change Processing Mode:

        • In Transactional apply mode, the last changes will not be replicated

        • In Batch optimized apply mode, a situation is possible where there will be no replication of data or data replication will occur in part

      • Stop task: The task is stopped and manual intervention is required.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!