Try OpenEdge Now

Database Administration

Maintaining and Monitoring Your Database : Change Data Capture : CDC and other RDBMS features

CDC and other RDBMS features

In the sections that follow, the interactions of CDC with RDBMS features and utilities is described.

RDMBS Features

The interaction of CDC with other database features is described in the table that follows.

Feature	Behavior
Auditing	Both Auditing and CDC can be configured for the same data tables, however: Auditing of CDC data tables is not supported. CDC of audit policy tables is not supported.
Replication	CDC can be enabled and configured on a Replication target database, however, the Replication source database(s) must have the areas that CDC uses, or the replication of the CDC enablement will fail. If the database structures match, Replication sends all CDC updates to the target database(s). Because Replication targets are read only, no CDC activity originates on the target. When the source database is enabled at the feature level and the Change Tracking Table is created by the enable utility, notes are written to the recovery logs. The notes are communicated to the target database via the replication process and the target is then enabled for CDC feature. When tables are enabled for change capture and their change tables are created on the source database, recovery notes are logged and communicated to the replication target. The notes recreate the change tables for each CDC table on the target.
Encryption	OpenEdge TDE Encryption can occur on the area or table level. If encryption is desired for a CDC change table, CDC change tables must be created in an encrypted area if the source data table is already encrypted. Encryption must also allow CDC change tables to be encrypted to the same table level of encryption as the source data table.
Multi-tenancy	CDC and Multi-tenancy coexist in a database without issue.
Table partitioning	CDC and Table Partitioning coexist in a database without issue.
Security	Security roles for CDC are not necessary and are not provided. However, if the Change Tracking table and Change table(s) need additional security, you can add CAN constraints to these tables.

International databases

The Change Tables are writeen in the code page of the database, so as long as any extraction process retrieves the data with a related client code page there will be no issue with support. It is expected that the extraction application will use the same code page as used when accessing the source table.

Database utilities not impacted by CDC triggers

The interaction of CDC with utilities that are known to change rowid, tenant Id, and partition Id is described in the table that follows. These utilities do not change the data they manage, however certain utility operations will generate Change Tracking and Change Records by the nature of their changes.

Utility	Utility can run on CDC tables	Behavior when the Source Table is Enabled for CDC	Change tracking data generation¹
Tablemove	Yes	Movement of records from one area or partition to another does not write Change Table records. In addition, rowid changes when the record is moved to the new location. No special Change record is recorded for this change.	No CTR, No CR
Datamove	No	Movement of records from one database to another do not write Change Table records.	No CTR, No CR
Partition Copy	No	Movement of records of one partition and database to another do not write Change Table records.	No CTR, No CR
Schema mover	No	Changes the area of source data records that previously resided in the schema area. It does not move source data records, so no Change Table records are written.	No CTR, No CR
Backup/Restore	No	Utility operates at Block level, so no CDC activity is necessary.	No CTR, No CR
AuditReconfig	No	Schema records, such as audit schema, cannot be enabled for CDC, so no Change data is generated by this utility.	No CTR, No CR
Partition Split	No	Partition Split can change partition Id, but does not generate a Change record to record the event.	No CTR, No CR
Partition Merge	No	Partition Merge causes a drop partition. there is a change tracking record created.	CTR
Partition Rename	No	The partition name changes and not generate a Change Tracking or a Change Tracking record. Changing a partition name does not affect the partition Id or the record Id.	No CTR, No CR
Table Rename, Field Rename (Language Only)	No	The languages’ changing of the Table name or a field name does not generate a Change Tracking record or Change Table record.	No CTR, No CR
Binary Load, Bulkload	No	Could cause rowid, partition id changes and does generate a Change Tracking and Change Record. Note: Loading Change Table schema and data does not produce a CDC enabled Change Table.	CTR, CR
Dictionary Load, SQL Load	Yes	Could cause rowid, partition id changes and generates a Change Tracking and Change Record. Note: Loading Change Table schema and data does not produce a CDC enabled Change Table.	CTR, CR
Binary Dump	No	Could cause rowid, partition id changes but does not generate a Change record.	No CTR, No CR
Data Dictionary Dump,SQL Dump	Yes	Could cause rowid, partition id changes but does not generate a Change record.	No CTR, No CR
Area Truncate	No	Deallocated records do not generate Change records. The Change Tracking Table is not allowed to participate in an area truncate operation because it contains records for all tables participating in CDC.	No CTR, No CR
Convchar	No	The data is not changing, its encoding is changing, but it is still the same data, so there is no change to reflect.	No CTR, No CR

¹ For values in this column, CTR indicates Change Tracking Record, and CR indicates Change Table.

Database utilities impacted by CDC triggers

The interaction of CDC with utilities that are known to change data in CDC source tables is described in the table that follows.

Utility	Behavior when the Source Table is Enabled for CDC	Change tracking data generation¹
Idxfix Option 6 delete recid	Record deletion is captured.	CTR, CR
MT Table Deallocate	A de-allocate Change Tracking record is generated. This operation occurs for a tenant and records are de-allocated as a storage object for the tenant. Multiple delete records are not called for this operation.	CTR
Partition Truncate	A de-allocate Change Tracking record is generated. This operation occurs at the partition level and records are de-allocated as a storage object for the partition. Multiple delete records are not called for this operation.	CTR
Tenant Delete/Drop	A drop tenant Change Tracking record is generated. MT tenant drop is a ABL/SQL operation. The operation can be called on allocated/de-allocated partitions. Group partitions also generate a Change Tracking Record when they deleted.	CTR
Partition Drop (Language action only)	A partition drop causes a Change Tracking record to be generated when the languages execute this action. This also works for a composite partition.	CTR

¹ For values in this column, CTR indicates Change Tracking Record, and CR indicates Change Table.

Database utilities that process CDC Tables

The utilities listed in the table that follows can execute on CDC schema for maintenance or reporting. None of the utilities generate Change Tracking or Change Table records.

Utility	Behavior when the Source Table is Enabled for CDC
Idxbuild, idxcheck	Can rebuild indexes for Change Schema, Change Table
Idxfix	Can fix indexes for Change Schema, Change Table
Idxactivate	Can active the Change Tracking Table indexes. Indexes in the Change Table cannot be deactivated by a DBA.
Dbtool	Record format fixups – physical changes allowed
Dbanalys (all analysis types)	Includes all CDC related tables
Tablemove	Can move the Change Table only