anchor.diff:  ----
   
   [[oracle-xstreams-connector-properties]]
  -=== Connector properties
  +=== XStream connector properties
   
   The following configuration properties are _required_ when using XStreams unless a default value is available.
   
  
positive.code: == XStreams support
  
  The {prodname} Oracle connector by default ingests changes using native Oracle LogMiner.
  The connector can be toggled to use Oracle XStream instead and to do so specific database and connector configurations must be used that differ from that of LogMiner.
  In order to use the XStream API, you need to have a license for the GoldenGate product
  (though it is not required that GoldenGate itself is installed).
  
  === Preparing the Database
  
  
negative.code: }
  ----
  
  The transaction events are written to the topic named `_<database.server.name>_.transaction`.
  
  //Type: concept
  //ModuleID: debezium-oracle-connector-change-data-event-enrichment
  ==== Change data event enrichment
  
  When transaction metadata is enabled, the data message `Envelope` is enriched with a new `transaction` field.
  This field provides information about every event in the form of a composite of fields:
  
  `id`:: String representation of unique transaction identifier.
  `total_order`:: The absolute position of the event among all events generated by the transaction.
  `data_collection_order`:: The per-data collection position of the event among all events that were emitted by the transaction.
  
  The following example shows a typical transaction event message:
  
  [source,json,indent=0,subs="attributes"]
  ----
  