Click each component to explore its role and constraints in an EBR CDC environment.

Source

Oracle DB + EBR

Physical tables, editioning views, editions

Extractor

LogMiner

Redo log reader, dictionary strategy

Processor

Debezium

DDL parser, schema history, CDC events

Oracle DB + EBR

How EBR works

Tables are non-editioned: one physical table shared by all editions. All DML hits the base table.
Editioning views are editioned: each edition defines its own column projection of the base table.
PL/SQL, synonyms are editioned: packages, triggers, and synonyms can have per-edition definitions.
Editions are isolated namespaces (e.g., ORA$BASE, V1, V2). Sessions target a specific edition.

CDC implication

LogMiner reads redo logs generated by physical base tables. It does not capture which edition a session was in when it ran the DML.

Debezium must infer the correct column schema from the DDL history of editioning views, not from session metadata. This is the core constraint.

LogMiner in an EBR environment

Dictionary strategy comparison

Strategy	EBR suitability
redo_log_catalog	RequiredCaptures editioning view DDL from redo stream; reconstructs schema at any SCN
online_catalog	AvoidReads current dictionary only; misses historical DDL for past editions
hybrid	AvoidLOB/XML/JSON unsupported; EBR DDL behavior is untested

V$LOGMNR_CONTENTS has no edition column

LogMiner exposes PDB context via SRC_CON_NAME but has no equivalent for editions. There is no per-transaction EDITION_NAME column. This is the root cause of the concurrent edition problem.

Feasibility assessment

Conditional feasibility is constrained by concurrent edition schema ambiguity and DDL parser coverage.

Verdict and key actions

Technically feasible under specific conditions. Success depends on DDL parser robustness, short concurrent edition overlap windows, and downstream schema awareness.

MUST Set log.mining.strategy=redo_log_catalog
MUST Target base tables in table.include.list, not editioning views
TEST Start with event.processing.failure.handling.mode=fail to surface unparseable EBR DDL
PLAN Downstream consumers may receive one edition's schema applied to another edition's DML during concurrent overlap periods

Configuration reference

Property	Value	Notes
log.mining.strategy	redo_log_catalog	Required for editioning view DDL tracking
table.include.list	SCHEMA.BASE_TABLE	Base tables only; do not list editioning views
schema.history.internal. store.only.captured.tables.ddl	false	Processes editioning view DDL for schema context
event.processing.failure. handling.mode	fail	Start here; change only after testing
schema.history.internal. skip.unparseable.ddl	false	Enable only for non-schema DDL (e.g. CREATE EDITION)
log.mining.transaction. retention.ms	app-specific	Set above longest expected transaction duration
database.query.timeout.ms	1800000	Prevents LogMiner query timeouts; default is 600000

Debezium Oracle CDC with Edition-Based Redefinition

Oracle DB + EBR

How EBR works

CDC implication

LogMiner in an EBR environment

Dictionary strategy comparison

V$LOGMNR_CONTENTS has no edition column

Debezium processing in an EBR environment

Schema ambiguity with concurrent editions

Key configuration points

Column type change via EBR

Feasibility assessment

Verdict and key actions

Configuration reference