anchor.diff:  
   [[oracle-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, {prodname}'s Oracle connector always follows the _delete_ event with a special _tombstone_ event that has the same key but `null` value.
  -
  +The message value must be set to `null` to instruct Kafka to remove _all messages_ that share the same key.
  +To make this possible, by default, {prodname}'s Oracle connector always follows a _delete_ event with a special _tombstone_ event that has the same key but `null` value.
  +You can change the default behavior by setting the connector property xref:oracle-property-tombstones-on-delete[`tombstones.on.delete`].
  +
  +// Type: reference
  +// ModuleID: how-debezium-oracle-connectors-map-data-types
  +// Title: How {prodname} Oracle connectors map data types
   [[oracle-data-type-mappings]]
  -== Data Type mappings
  -
  -The Oracle connector represents changes to rows with events that are structured like the table in which the rows exists. The event contains a field for each column value. How that value is represented in the event depends on the Oracle data type of the column. The following sections describe how the connector maps oracle data types to a _literal type_ and a _semantic type_ in event fields.
  -
  -* _literal type_ describes how the value is literally represented using Kafka Connect schema types: `INT8`, `INT16`, `INT32`, `INT64`, `FLOAT32`, `FLOAT64`, `BOOLEAN`, `STRING`, `BYTES`, `ARRAY`, `MAP`, and `STRUCT`.
  -
  -* _semantic type_ describes how the Kafka Connect schema captures the _meaning_ of the field using the name of the Kafka Connect schema for the field.
  +== Data type mappings
  +
  +To represent changes that occur in a table rows, the {prodname} Oracle connector emits change events that are structured like the table in which the rows exists.
  +The event contains a field for each column value.
  +Column values are represented according to the Oracle data type of the column.
  +The following sections describe how the connector maps oracle data types to a _literal type_ and a _semantic type_ in event fields.
  +
  +_literal type_:: Describes how the value is literally represented using Kafka Connect schema types: `INT8`, `INT16`, `INT32`, `INT64`, `FLOAT32`, `FLOAT64`, `BOOLEAN`, `STRING`, `BYTES`, `ARRAY`, `MAP`, and `STRUCT`.
  +
  +_semantic type_:: Describes how the Kafka Connect schema captures the _meaning_ of the field using the name of the Kafka Connect schema for the field.
   
   ifdef::product[]
   Details are in the following sections:
  
positive.code: When the `decimal.handling.mode` property is set to `precise`, the connector uses Kafka Connect `org.apache.kafka.connect.data.Decimal` logical type for all `DECIMAL` and `NUMERIC` columns.
  This is the default mode.
  
  However, when the `decimal.handling.mode` property is set to `double`, the connector will represent the values as Java double values with schema type `FLOAT64`.
  
  The last possible setting for the `decimal.handling.mode` configuration property is `string`.
  In this case, the connector reprsents `DECIMAL` and `NUMERIC` values as their formatted string representation with schema type `STRING`.
  
  [id="oracle-temporal-types"]
  === Temporal types
  
  Other than Oracle's `INTERVAL`, `TIMESTAMP WITH TIME ZONE` and `TIMESTAMP WITH LOCAL TIME ZONE` data types, the other temporal types depend on the value of the `time.precision.mode` configuration property.
  
  When the `time.precision.mode` configuration property is set to `adaptive` (the default), then the connector will determine the literal and semantic type for the temporal types based on the column's data type definition so that events _exactly_ represent the values in the database:
  
  [cols="25%a,20%a,55%a",options="header"]
  |===
  
negative.code: 
  * xref:obtaining-the-oracle-jdbc-driver[]
  * xref:deploying-debezium-oracle-server-connectors[]
  * xref:descriptions-of-debezium-oracle-connector-configuration-properties[]
  endif::product[]
  
  // Type: procedure
  