Striim 3.9.7 documentation

Including DDL operations in OracleReader output

Reading DDL transactions requires Oracle 11g and LogMiner. It is enabled by setting OracleReader's DictionaryMode property to OfflineCatalog.

DDL events are output only for those tables, functions,  indexes, packages,  procedures, and views specified in OracleReader's Tables property value. Wildcards may be used, in which case DDL for new objects with names that match the wildcard pattern will be included in the output. See Handling DDL events when replicating Oracle data for a list of supported targets. Bidirectional replication of DDL is not supported.

Reading from tables containing XMLType columns is not supported when DictionaryMode is OfflineCatalog.

Supported DDL operations

The following DDL operations will be read for those tables, functions,  indexes, packages,  procedures, and views specified in OracleReader's Tables property value:

operation

function

index

package

procedure

table

view

ALTER ... ADD <column> 

x

ALTER ... ADD PRIMARY KEY

x

ALTER ... DROP <column>

x

ALTER ... MODIFY <column> <type>

x

ALTER ... RENAME

x

x

x

ALTER ... RENAME <column>

x

CREATE

x

x

x

x

x

x

CREATE OR REPLACE

x

x

x

x

DROP

x

x

x

x

x

x

TRUNCATE

x

In addition, the following operations are passed through to the target:

  • ANALYZE TABLE <table> VALIDATE STRUCTURE

  • GRANT <privilege(s)> ON <table> ...

  • REVOKE <privilege(s)> ON <table> ...

ALTER TABLE ... DROP / ENABLE / DISABLE <constraint name>; and operations on materialized views are not supported. If OracleReader encounters unsupported DDL (such as CREATE, ALTER, or DROP on a user, role, or trigger), it will write a warning to the log and continue.