anchor.diff:  Fully-qualified data type names are of the form _databaseName_._tableName_._typeName_, or _databaseName_._schemaName_._tableName_._typeName_.
   See xref:data-types[] for the list of Oracle-specific data type names.
   
  -|[[connector-property-heartbeat-interval-ms]]<<connector-property-heartbeat-interval-ms, `heartbeat.interval.ms`>>
  +|[[oracle-property-heartbeat-interval-ms]]<<oracle-property-heartbeat-interval-ms, `heartbeat.interval.ms`>>
   |`0`
   |Controls how frequently heartbeat messages are sent. +
   This property contains an interval in milli-seconds that defines how frequently the connector sends messages into a heartbeat topic.
  
positive.code: If the application needs to track changes in the source database there is the public-facing schema change topic.
  The topic name is the same as the logical server name configured in connector configuration.
  
  Debezium emits a new message to this topic whenever a new table is streamed from or when the structure of the table is altered ({link-prefix}:{link-oracle-connector}#schema-evolution[schema evolution procedure must be followed]).
  The message contains a logical representation of the table schema.
  
  The example of the message is:
  
negative.code: 
  [NOTE]
  ====
  When the columns for a row's primary/unique key are updated, the value of the row's key has changed so Debezium will output _three_ events: a `DELETE` event and a {link-prefix}:{link-oracle-connector}#oracle-tombstone-events[tombstone event] with the old key for the row, followed by an `INSERT` event with the new key for the row.
  ====
  
  [[oracle-delete-events]]
  ===== Delete events
  
  So far we've seen samples of _create_ and _update_ events.
  