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