anchor.diff:  
   Note: Depending on the `_hashAlgorithm_` used, the `_salt_` selected and the actual data set, the resulting masked data set may not be completely anonymized.
   
  -|[[connector-property-decimal-handling-mode]]<<connector-property-decimal-handling-mode, `decimal.handling.mode`>>
  +|[[oracle-property-decimal-handling-mode]]<<oracle-property-decimal-handling-mode, `decimal.handling.mode`>>
   |`precise`
   | Specifies how the connector should handle floating point values for `NUMBER`, `DECIMAL` and `NUMERIC` columns: `precise` (the default) represents them precisely using `java.math.BigDecimal` values represented in change events in a binary form; or `double` represents them using `double` values, which may result in a loss of precision but will be far easier to use. `string` option encodes values as formatted string which is easy to consume but a semantic information about the real type is lost. See <<decimal-values>>.
   
  -|[[connector-property-event-processing-failure-handling-mode]]<<connector-property-event-processing-failure-handling-mode, `event.processing{zwsp}.failure.handling.mode`>>
  +|[[oracle-property-event-processing-failure-handling-mode]]<<oracle-property-event-processing-failure-handling-mode, `event.processing{zwsp}.failure.handling.mode`>>
   |`fail`
   | Specifies how the connector should react to exceptions during processing of events.
   `fail` will propagate the exception (indicating the offset of the problematic event), causing the connector to stop. +
   `warn` will cause the problematic event to be skipped and the offset of the problematic event to be logged. +
   `skip` will cause the problematic event to be skipped.
   
  -|[[connector-property-max-queue-size]]<<connector-property-max-queue-size, `max.queue.size`>>
  +|[[oracle-property-max-queue-size]]<<oracle-property-max-queue-size, `max.queue.size`>>
   |`8192`
   |Positive integer value that specifies the maximum size of the blocking queue into which change events read from the database log are placed before they are written to Kafka. This queue can provide backpressure to the binlog reader when, for example, writes to Kafka are slower or if Kafka is not available. Events that appear in the queue are not included in the offsets periodically recorded by this connector. Defaults to 8192, and should always be larger than the maximum batch size specified in the `max.batch.size` property.
   
  -|[[connector-property-max-batch-size]]<<connector-property-max-batch-size, `max.batch.size`>>
  +|[[oracle-property-max-batch-size]]<<oracle-property-max-batch-size, `max.batch.size`>>
   |`2048`
   |Positive integer value that specifies the maximum size of each batch of events that should be processed during each iteration of this connector. Defaults to 2048.
   
  -|[[connector-property-poll-interval-ms]]<<connector-property-poll-interval-ms, `poll.interval.ms`>>
  +|[[oracle-property-poll-interval-ms]]<<oracle-property-poll-interval-ms, `poll.interval.ms`>>
   |`1000`
   |Positive integer value that specifies the number of milliseconds the connector should wait during each iteration for new change events to appear. Defaults to 1000 milliseconds, or 1 second.
   
  -|[[connector-property-tombstones-on-delete]]<<connector-property-tombstones-on-delete, `tombstones.on.delete`>>
  +|[[oracle-property-tombstones-on-delete]]<<oracle-property-tombstones-on-delete, `tombstones.on.delete`>>
   |`true`
   | Controls whether a tombstone event should be generated after a delete event. +
   When `true` the delete operations are represented by a delete event and a subsequent tombstone event. When `false` only a delete event is sent. +
   Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted.
   
  -|[[connector-property-message-key-columns]]<<connector-property-message-key-columns, `message.key.columns`>>
  +|[[oracle-property-message-key-columns]]<<oracle-property-message-key-columns, `message.key.columns`>>
   |_empty string_
   | A semi-colon list of regular expressions that match fully-qualified tables and columns to map a primary key. +
   Each item (regular expression) must match the `<fully-qualified table>:<a comma-separated list of columns>` representing the custom key. +
   Fully-qualified tables could be defined as _pdbName_._schemaName_._tableName_.
   
  -|[[connector-property-column-truncate-to-length-chars]]<<connector-property-column-truncate-to-length-chars, `column.truncate.to._length_.chars`>>
  +|[[oracle-property-column-truncate-to-length-chars]]<<oracle-property-column-truncate-to-length-chars, `column.truncate.to._length_.chars`>>
   |_n/a_
   |An optional comma-separated list of regular expressions that match the fully-qualified names of character-based columns whose values should be truncated in the change event message values if the field values are longer than the specified number of characters. Multiple properties with different lengths can be used in a single configuration, although in each the length must be a positive integer. Fully-qualified names for columns are of the form _pdbName_._schemaName_._tableName_._columnName_.
   
  -|[[connector-property-column-mask-with-length-chars]]<<connector-property-column-mask-with-length-chars, `column.mask.with._length_.chars`>>
  +|[[oracle-property-column-mask-with-length-chars]]<<oracle-property-column-mask-with-length-chars, `column.mask.with._length_.chars`>>
   |_n/a_
   |An optional comma-separated list of regular expressions that match the fully-qualified names of character-based columns whose values should be replaced in the change event message values with a field value consisting of the specified number of asterisk (`*`) characters. Multiple properties with different lengths can be used in a single configuration, although in each the length must be a positive integer or zero. Fully-qualified names for columns are of the form _pdbName_._schemaName_._tableName_._columnName_.
   
  -|[[connector-property-column-propagate-source-type]]<<connector-property-column-propagate-source-type, `column.propagate.source.type`>>
  +|[[oracle-property-column-propagate-source-type]]<<oracle-property-column-propagate-source-type, `column.propagate.source.type`>>
   |_n/a_
   |An optional comma-separated list of regular expressions that match the fully-qualified names of columns whose original type and length should be added as a parameter to the corresponding field schemas in the emitted change messages.
   The schema parameters `pass:[_]pass:[_]debezium.source.column.type`, `pass:[_]pass:[_]debezium.source.column.length` and `pass:[_]pass:[_]debezium.source.column.scale` will be used to propagate the original type name and length (for variable-width types), respectively.
   Useful to properly size corresponding columns in sink databases.
   Fully-qualified names for columns are of the form _databaseName_._tableName_._columnName_, or _databaseName_._schemaName_._tableName_._columnName_.
   
  -|[[connector-property-datatype-propagate-source-type]]<<connector-property-datatype-propagate-source-type, `datatype.propagate.source.type`>>
  +|[[oracle-property-datatype-propagate-source-type]]<<oracle-property-datatype-propagate-source-type, `datatype.propagate.source.type`>>
   |_n/a_
   |An optional comma-separated list of regular expressions that match the database-specific data type name of columns whose original type and length should be added as a parameter to the corresponding field schemas in the emitted change messages.
   The schema parameters `pass:[_]pass:[_]debezium.source.column.type`, `pass:[_]pass:[_]debezium.source.column.length` and `pass:[_]pass:[_]debezium.source.column.scale` will be used to propagate the original type name and length (for variable-width types), respectively.
  
positive.code: which allows for the removal of some older messages as long as at least the most recent message for every key is kept.
  This allows Kafka to reclaim storage space while ensuring the topic contains a complete dataset and can be used for reloading key-based state.
  
  [[tombstone-events]]
  When a row is deleted, the _delete_ event value listed above still works with log compaction, since Kafka can still remove all earlier messages with that same key.
  But only if the message value is `null` will Kafka know that it can remove _all messages_ with that same key.
  To make this possible, Debezium's Oracle connector always follows the _delete_ event with a special _tombstone_ event that has the same key but `null` value.
  
  [[transaction-metadata]]
  === Transaction Metadata
  
  [NOTE]
  
negative.code: It is supported though to capture tables newly added while the connector is running
  (provided the new table's name matches the connector's filter configuration).
  
  [[oracle-overview]]
  == Overview
  
  Debezium ingests change events from Oracle using the https://docs.oracle.com/database/121/XSTRM/xstrm_intro.htm#XSTRM72647[XStream API].
  