Use the processed views - 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

Several methods are available to determine which archive logs are safe to be deleted. When Connect CDC is installed, two views are created to help determine which logs have been processed:

  • The <rpuser>_v_processed_logs view, where <rpuser> is the metabase name, joins v$archived_log with internal Connect CDC tables to determine which logs have been processed and are no longer required for replication. The <rpuser>_v_processed_logs view lists all archive logs for the first active destination id.

  • If multiple archive destinations are used, the <rpuser>_v_all_processed_logs view lists information for all archive logs for all active destinations.

The rows returned from these views are in ascending order by log sequence number. The views are derived from v$archived_log. Therefore, all of the columns from v$archived_log are available to be queried from the Connect CDC views.

Note: The Oracle Change Selector is able to handle gaps in the numbering of the log sequence