anchor.diff:  
   The {prodname} Oracle connector supports both deployment practices of pluggable databases (CDB mode) as well as non-pluggable databases (non-CDB mode).
   
  -==== Non-Pluggable Databases
  -
  -In order to deploy the connector in non-pluggable database mode, the the `database.pdb.name` configuration option must **not** be supplied.
  -An example configuration for pluggable databases would be:
  -
  +.Example configuration using non-CDB (Non Pluggable Database) installations
   [source,json,indent=0]
   ----
   {
  
positive.code: }
  ----
  
  ==== Pluggable Databases
  
  In order to deploy the connector in pluggable database mode (CDB), the `database.pdb.name` configuration option *must* be supplied.
  An example configuration when using pluggable databases would be:
  
  [source,json,indent=0]
  ----
  {
  
negative.code: 
  If the connector fails, is rebalanced, or stops after step 1 begins but before step 7 completes,
  upon restart the connector will begin a new snapshot.
  After the connector completes its initial snapshot, the {prodname} connector continues streaming from the position that it read in step 3.
  This ensures that the connector does not miss any updates.
  If the connector stops again for any reason, upon restart, the connector continues streaming changes from where it previously left off.
  
  .Settings for `snapshot.mode` connector configuration property
  [cols="30%a,70%a",options="header"]
  |===
  |Setting |Description
  
  |`initial`
  |The connector performs a database snapshot after which it will transition to streaming changes.
  
  |`schema_only`
  |The connector captures the structure of all relevant tables, performing all the steps described above, except it does not create any `READ` events representing the dataset at the point of the connector's start-up.
  
  |===
  
  [[oracle-topic-names]]
  === Topics Names
  