Cleaning Replication Processing Information for a Configuration
Cleaning Replication Processing Information for a Configuration
In the Data Replication Console, you can use the
Clean
option to remove replication processing information for all replication tasks that are associated with a replication configuration.
A clean operation removes the following information for the configuration:
Intermediate files
The clean operation deletes intermediate files regardless of the values that are set for the Server Manager IntermediateFilesDeleteLatency and NotDeleteIntermediateFiles advanced properties. For more information about these properties, see
Editing Properties for the Main Server or a Subserver.
Checkpoint information
Information about previous configuration revisions
Internal Data Replication processing information that the replication tasks added to the configuration
Information about open transactions and processed database logs
A clean operation does not remove replication configuration settings such as the source and target connection information, the recovery table connection information, and the location of the source database logs.
When you request a clean operation on a configuration, Data Replication backs up the existing configuration SQLite database files and intermediate files before starting clean processing, by default. The following information is backed up:
All of the SQLite database files that are associated with the replication configuration
All of the intermediate files that are associated with the replication configuration
You can clear the option for creating the backups if you do not want to retain this information. Data Replication stores the backups in the directory that is specified in the
Backups
field on the
Paths
tab of the Server Manager
Properties
dialog box. Data Replication creates a subdirectory for each clean operation using the following naming pattern:
<current_timestamp>
_
<configuration_name>
. By default, Data Replication stores each backup for 30 days. Data Replication checks the backup subdirectories hourly to remove any subdirectory for which the retention period has expired. You can use the Server Manager TimeToStoreBackups advanced property to change the number of days that the Server Manager Main server stores the backups.
After a clean operation, the Extractor and Applier tasks associated with the configuration appear as if they have never run. If no open transaction exists for the mapped source tables, the Extractor Start Point is set to the last SCN
, log coordinate,
or LSN value that the Applier processed for the configuration. If an open transaction exists for the mapped source tables, the Extractor Start Point is set to the last SCN
, log coordinate,
or LSN value for the BEGIN TRANSACTION operation.
During clean processing, the Data Replication Console requires a source database connection to retrieve certain database information for the updated Extractor Start Point. If you clean a replication configuration when the source database connection is not currently available, the Data Replication Console does not update the Extractor Start Point value. In this case, you can set the Extractor Start Point value manually later.
The Applier Start Point is set to the last SCN
, log coordinate,
or LSN value that the Applier processed for the configuration.
For Kafka targets, cleaning a configuration does not affect the checkpoints for apply processing that are recorded in the checkpoint file on the system where the Applier and Queue Adapter run.