Striim 3.10.3 documentation

Handling DDL events when replicating Oracle data

Reading DDL transactions requires Oracle 18c or earlier and LogMiner. It is enabled by setting OracleReader's DictionaryMode property to OfflineCatalog.

DDL events may be replayed in another Oracle instance, subject to the limitations discussed in Replicating Oracle data to another Oracle database. DDL cannot be replayed in non-Oracle databases.

KafkaWriter can use DDL events to track evolution of Oracle tables. See Using the Confluent or Hortonworks schema registry.

AzureBlobWriter, FileWriter, GCSWriter, HDFSWriter, and S3Writer automatically roll over to a new file when a DDL event is received. This default behavior may be disabled using the RolloverOnDDL property.