anchor.diff:  |The number of hours in the past from SYSDATE to mine archive logs.
   Using the default `0` will mine all archive logs.
   
  +|[[oracle-property-log-mining-transaction-retention-hours]]<<oracle-property-log-mining-transaction-retention-hours, `log.mining.transaction.retention.hours`>>
  +|`0`
  +|Positive integer value that specifies the number of hours to retain long running transactions between redo log switches.
  +When set to `0`, transactions are retained until a commit or rollback is detected.
  +
  +The LogMiner adapter maintains an in-memory buffer of all running transactions.
  +As all DML operations that are part of a transaction will be buffered until a commit or rollback is detected,
  +long-running transactions should be avoided in order to not overflow that buffer.
  +Any transaction that exceeds this configured value will be discarded entirely and no messages emitted for the operations that were part of the transaction.
  +
  +While this option allows the behavior to be configured on a case-by-case basis,
  +we have plans to enhance this behavior in a future release by means of adding a scalable transaction buffer, (see {link-prefix}:{jira-url}/browse/DBZ-3123[DBZ-3123]).
  +
   |[[oracle-property-database-history-retention-hours]]<<oracle-property-database-history-retention-hours, `+database.history.retention.hours+`>>
   |`0`
   |The number of hours to retain entries in log mining history table.
   When set to `0`, log mining history is is disabled.
   
  -|[[oracle-property-log-mining-transaction-retention-hours]]<<oracle-property-log-mining-transaction-retention-hours, `log.mining.transaction.retention.hours`>>
  -|`0`
  -|Positive integer value that specifies the number of hours to retain long running transactions between redo log switches.
  -When set to `0`, transactions are retained until a commit or rollback is detected.
  -
  -The LogMiner adapter maintains an in-memory buffer of all running transactions.
  -As all DML operations that are part of a transaction will be buffered until a commit or rollback is detected,
  -long-running transactions should be avoided in order to not overflow that buffer.
  -Any transaction that exceeds this configured value will be discarded entirely and no messages emitted for the operations that were part of the transaction.
  -
  -While this option allows the behavior to be configured on a case-by-case basis,
  -we have plans to enhance this behavior in a future release by means of adding a scalable transaction buffer, (see {link-prefix}:{jira-url}/browse/DBZ-3123[DBZ-3123]).
  +|[[oracle-property-rac-nodes]]<<oracle-property-rac-nodes, `+rac.nodes+`>>
  +|
  +|A comma-separated list of RAC node host names or addresses.
  +This field is required to enable Oracle RAC support.
   
   |===
   
  
positive.code: 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.
  
  |[[oracle-property-message-key-columns]]<<oracle-property-message-key-columns, `+message.key.columns+`>>
  |_n/a_
  | 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_.
  
  |[[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_.
  
  |[[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_.
  
  |[[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 _tableName_._columnName_, or _schemaName_._tableName_._columnName_.
  
  |[[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.
  Useful to properly size corresponding columns in sink databases.
  Fully-qualified data type names are of the form _tableName_._typeName_, or _schemaName_._tableName_._typeName_.
  See the {link-prefix}:{link-oracle-connector}#oracle-data-types[list of Oracle-specific data type names].
  
  |[[oracle-property-heartbeat-interval-ms]]<<oracle-property-heartbeat-interval-ms, `+heartbeat.interval.ms+`>>
  |`0`
  
negative.code: |An optional, comma-separated list of regular expressions that match names of schemas for which you *do not* want to capture changes. Any schema whose name is not included in `schema.exclude.list` has its changes captured, with the exception of system schemas. Do not also set the `schema.include.list` property.  When using LogMiner, only POSIX regular expressions are supported.
  
  |[[oracle-property-table-include-list]]<<oracle-property-table-include-list, `+table.include.list+`>>
  |
  |An optional comma-separated list of regular expressions that match fully-qualified table identifiers for tables to be monitored; any table not included in the include list will be excluded from monitoring. Each identifier is of the form _schemaName_._tableName_. By default the connector will monitor every non-system table in each monitored database. May not be used with `table.exclude.list`.  When using LogMiner, only POSIX regular expressions are supported.
  
  |[[oracle-property-table-exclude-list]]<<oracle-property-table-exclude-list, `+table.exclude.list+`>>
  |
  |An optional comma-separated list of regular expressions that match fully-qualified table identifiers for tables to be excluded from monitoring; any table not included in the exclude list will be monitored. Each identifier is of the form _schemaName_._tableName_. May not be used with `table.include.list`.  When using LogMiner, only POSIX regular expressions are supported.
  
  |[[oracle-property-column-include-list]]<<oracle-property-column-include-list, `+column.include.list+`>>
  |
  |An optional comma-separated list of regular expressions that match the fully-qualified names of columns that should be included in the change event message values.
  Fully-qualified names for columns are of the form _schemaName_._tableName_._columnName_.
  Note that primary key columns are always included in the event's key, even if not included in the value.
  Do not also set the `column.exclude.list` property.
  
  |[[oracle-property-column-exclude-list]]<<oracle-property-column-exclude-list, `+column.exclude.list+`>>
  |
  |An optional comma-separated list of regular expressions that match the fully-qualified names of columns that should be excluded from change event message values.
  Fully-qualified names for columns are of the form _schemaName_._tableName_._columnName_.
  Note that primary key columns are always included in the event's key, also if excluded from the value.
  Do not also set the `column.include.list` property.
  
  |[[oracle-property-column-mask-hash]]<<oracle-property-column-mask-hash, `+column.mask.hash._hashAlgorithm_.with.salt._salt_+`>>
  |
  |An optional comma-separated list of regular expressions that match the fully-qualified names of character-based columns whose values should be pseudonyms in the change event message values with a field value consisting of the hashed value using the algorithm `_hashAlgorithm_` and salt `_salt_`.
  Based on the used hash function referential integrity is kept while data is pseudonymized. Supported hash functions are described in the {link-java7-standard-names}[MessageDigest section] of the Java Cryptography Architecture Standard Algorithm Name Documentation.
  The hash is automatically shortened to the length of the column.
  
  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_.
  
  Example:
  