Work with archive logs - Connect_CDC - connect_cdc_mimix_share - 6.x

Connect CDC Getting Started Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
6.x
ft:locale
en-US
Product name
Connect CDC
ft:title
Connect CDC Getting Started Guide
Copyright
2025
First publish date
2003
ft:lastEdition
2026-02-25
ft:lastPublication
2026-02-25T19:01:02.274000
L1_Product_Gateway
Integrate
L2_Product_Segment
Data Integration
L3_Product_Brand
Precisely Connect
L4_Investment_Segment
Application Data Integration
L5_Product_Group
ADI - Connect
L6_Product_Name
Connect CDC

During installation, you set up whether archive logs should be deleted. Archive logs must be kept until all rows from the log have been replicated.

If you have Connect CDC delete the archive logs, the Change Selector automatically determines when archived logs are no longer needed for replication. The user must have the privileges necessary to delete an archive log file for this action to take place.

Note: If you choose to delete archive logs through Connect CDC, specify the option to rename the processed archive logs (see the Installation Guide for directions on setting the rename option).

If you choose to retain archive logs, they are deleted outside of Connect CDC and you must ensure that archive logs required for replication are not deleted. Deleting logs before Connect CDC has read them can result in data loss. If you use the Oracle Recovery Manager utility to delete archive logs, commands that delete all archive logs, such as the following, may cause conflicts with Connect CDC.

BACKUP ARCHIVELOG ALL DELETE INPUT;