Work with renamed 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
Language
English
Product name
Connect CDC
Title
Connect CDC Getting Started Guide
Copyright
2024
First publish date
2003
Last updated
2024-10-15
Published on
2024-10-15T20:38:41.117981

Many software backup applications allow archive logs to be renamed instead of deleted after a successful backup. Connect CDC supports renamed archive logs as a method to coordinate archive log deletion with third party backup software or a backup script. The backup and deletion of archive logs must be coordinated with Connect CDC; otherwise, data loss could result if archive logs are deleted before Connect CDC processes them.

The following steps describe how to coordinate archive log backup and deletion automatically using renamed archive logs:

  1. Modify the backup software configuration to specify that after a successful backup archive logs should be renamed in all archive destinations.

  2. Specify the delete archive files parameter using the parameter Configurator. If this was not done as part of installation, see the Installation Guide for directions on how to run the Configurator in standalone mode.

  3. Specify the rename prefix parameter using the parameter Configurator. If this was not done as part of installation, see the Installation Guide for directions on how to run the Configurator in standalone mode.

When these settings are specified, Connect CDC does not delete archive files until they have been renamed and are no longer needed for replication. The Connect CDC Kernel automatically handles coordination by running a background process that periodically checks for and deletes processed archive logs that have been renamed.

The following example demonstrates the processing events:

  1. Oracle creates archive logs with the following names:

    C:\Oracle9.2\oradata\ORCL\archive\OMNI1_3649.ARC
    C:\Oracle9.2\oradata\ORCL\archive\OMNI1_3650.ARC
    C:\Oracle9.2\oradata\ORCL\archive\OMNI1_3651.ARC
  2. Connect CDC reads and processes these files for replication, but they are not deleted because they have not been renamed. When the backup software runs, the logs listed in step 1 are backed up and then renamed with a prefix. In the example, the prefix is DT.

    C:\Oracle9.2\oradata\ORCL\archive\DT.OMNI1_3649.ARC
    C:\Oracle9.2\oradata\ORCL\archive\DT.OMNI1_3650.ARC
    C:\Oracle9.2\oradata\ORCL\archive\DT.OMNI1_3651.ARC
  3. When the logs are no longer required for replication, they are renamed, indicating that they have been successfully backed up. The next time Connect CDC looks for processed logs, the renamed logs are deleted.