anchor.diff:  <11> The list of Kafka brokers that this connector will use to write and recover DDL statements to the database history topic.
   <12> The name of the database history topic where the connector will write and recover DDL statements. This topic is for internal use only and should not be used by consumers.
   
  -In more complex Oracle deployments, and those that use TNS names, you can provide a raw JDBC URL instead of a single hostname and port pair.
  -The following JSON example describes a configuration that is similar to the preceding example, but that passes a raw JDBC URL rather than a hostname and port:
  -
  +In more complex Oracle deployments, and those that use TNS names, you can provide a raw JDBC URL in place of the hostname and port pair in the preceding example.
  +The following JSON example describes a configuration that is similar to the preceding one, except that it passes a raw JDBC URL instead of a hostname and port:
  +
  +.Example: {prodname} Oracle connector configuration that uses a JDBC URL to connect to the database
   [source,json,indent=0]
   ----
   {
  
positive.code: 
  The {prodname} Oracle connector supports both deployment practices of pluggable databases (CDB mode) as well as non-pluggable databases (non-CDB mode).
  
  .Example configuration using non-CDB (Non Pluggable Database) installations
  [source,json,indent=0]
  ----
  {
  
negative.code: }
  ----
  
  .Example: {prodname} connector configuration for CDB (Pluggable Database) installations
  [source,json,indent=0]
  ----
  {
  