Capture partitions - connect_cdc_sqdata - Latest

Connect CDC (SQData) Change Data Capture

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (SQData)
Version
Latest
Language
English
Product name
Connect CDC (SQData)
Title
Connect CDC (SQData) Change Data Capture
Copyright
2024
First publish date
2000
ft:lastEdition
2024-09-05
ft:lastPublication
2024-09-05T15:00:09.754973

Partitioned Oracle tables will by default not be captured. Three options are provided for capturing changes to partitioned tables. First, the default behavior can be changed by toggling the default using the -- no-sql-filter option via a modify command to the capture .cab configuration file:

Syntax
sqdconf modify <cab_file_name> --sql-filter | –-no-sql-filter

Alternatively, an entry for each possible "table, partition" can be specified in the capture .cab file, see Create Oracle Capture CAB file specifications. Then when a change is captured for a partitioned table, if an entry is found the table will be captured and published to the specified subscriptions. If it is not found the record will not be captured or published.

Finally, if only some of the "table, partitions" have been specified, the --no-sql-filter option can be used to send remaining partitions to desired subscriptions. The capture will first scan the capture .cab file for the captured "table, partition" and If not found, a look-up will performed for just the "table" name in the .cab and if it is found, the record will be captured and published to the specified subscriptions.

The current state of sql filtering can be determined using the display command:

Syntax
sqdconf display <cab_file_name>

SQDF913I Fix Flags : RETRY,NO_SQL_FILTER

Finally, if sql-filter is enabled, it can be overridden for a single execution of the capture using only the start command:

Syntax
sqdconf start <cab_file_name> –-no-sql-filter