anchor.diff:  Without these grants, the connector cannot operate.
   
   |===
  -
   === Standby databases
  -
  +ifdef::product[]
  +The {prodname} Oracle connector cannot be used with Oracle physical or logical standby databases.
  +endif::product[]
  +ifdef::community[]
   An Oracle database can be configured with either a physical or a logical standby environment to provide for recovery after of a production failure.
   At this time, the {prodname} Oracle connector cannot use a physical or logical standby database as the change event source.
   There is an open https://issues.redhat.com/browse/DBZ-3866[Jira issue] to investigate this support.
  
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
  