Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Installing Data Replication
  4. Preparing Source and Target Systems
  5. Replication Basic Concepts
  6. InitialSync Processing
  7. Extractor and Applier Processing
  8. DDL Replication
  9. Recovery and Checkpoint Processing
  10. Configuring the Server Manager
  11. Creating Replication Configurations in the Data Replication Console
  12. Managing Replication Configurations
  13. Running Data Replications
  14. Configuring Selected Replication Types
  15. Monitoring Data Replication
  16. Maintaining the Replication Environment
  17. Troubleshooting
  18. Data Replication Files and Subdirectories
  19. Data Replication Runtime Parameters
  20. InitialSync, Extractor, and Applier Command Line Parameters
  21. Server Manager Command Line Parameters
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

Skipped Transaction Records

Skipped Transaction Records

By default, when the Extractor cannot parse a record in the source transaction logs, the Extractor logs an error and stops processing to avoid data integrity issues. You can use the extract.stop_on_parsing_error runtime parameter to have the Extractor skip the damaged log record and continue processing, by default.
For Oracle sources, when a parsing error occurs, the Extractor also creates an SQLite database file that contains the unparsed transaction record and additional troubleshooting information in the
DataReplication_installation
/dump subdirectory. If you set the
extract.stop_on_parsing_error
parameter to 0 to skip damaged log records, you must periodically check if the
DataReplication_installation
/dump subdirectory is empty or contains files. If the dump subdirectory contains files, the Extractor skipped some records and the target database might have data integrity issues.
For source databases other than Oracle, the Extractor logs errors but does not create SQLite database files that contain unparsed transaction records in the
DataReplication_installation
/dump subdirectory.

0 COMMENTS

We’d like to hear from you!