anchor.diff:  In messages that the connector sends to the schema change topic, the key is the name of the database that contains the schema change.
   In the following example, the `payload` field contains the key:
   
  -[source,json,indent=0,subs="attributes"]
  +[source,json,indent=0,subs="+attributes"]
   ----
   {
     "schema": {
  
positive.code: [[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 _litearl 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`.
  
  
negative.code: 
  toc::[]
  
  [[oracle-overview]]
  == Overview
  
  {prodname} ingests change events from Oracle using the native LogMiner database package or the https://docs.oracle.com/database/121/XSTRM/xstrm_intro.htm#XSTRM72647[XStream API].
  Oracle versions 11, 12, and 19 are supported.
  
  [[how-the-oracle-connector-works]]
  == How the Oracle Connector Works
  