anchor.diff:  By default, change events have large object columns, but the columns contain no values.
   There is a certain amount of overhead in processing and managing large object column types and payloads.
   To capture large object values and serialized them in change events, set this option to `true`.
  +
  +NOTE: Use of large object data types is a Technology Preview feature.
   
   |[[oracle-property-unavailable-value-placeholder]]<<oracle-property-unavailable-value-placeholder, `+unavailable.value.placeholder+`>>
   |`__debezium_unavailable_value`
  
positive.code: Please let us know if you encounter any problems while using these data types.
  ====
  endif::community[]
  The following table describes how the connector maps binary and character large object (LOB) data types.
  
  .Mappings for Oracle binary and character LOB types
  
negative.code: 
  In the case of a logical standby, the standby is not an exact copy of the production database, so the SCN offsets in the standby differ from those in the production database.
  If you use a logical standby, to help ensure that {prodname} does not miss any change events, after the database is open, configure a new connector and perform a new database snapshot.
  endif::community[]
  // Type: assembly
  // ModuleID: deployment-of-debezium-oracle-connectors
  // Title: Deployment of {prodname} Oracle connectors
  