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 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:
  +In the previous example, the `database.hostname` and `database.port` properties are used to define the connection to the database host.
  +However, in more complex Oracle deployments, or in deployments that use TNS names, you can use an alternative method in which you specify a JDBC URL.
  +
  +The following JSON example shows the same configuration as in the preceding example, except that it uses a JDBC URL to connect to the database.
   
   .Example: {prodname} Oracle connector configuration that uses a JDBC URL to connect to the database
   [source,json,indent=0]
  
positive.code: 
  |[[oracle-property-database-pdb-name]]<<oracle-property-database-pdb-name, `+database.pdb.name+`>>
  |
  |Name of the PDB to connect to, when working with the CDB + PDB model.
  
  |[[oracle-property-database-server-name]]<<oracle-property-database-server-name, `+database.server.name+`>>
  |
  
negative.code: // Category: debezium-using
  // Type: assembly
  [id="debezium-connector-for-oracle"]
  = {prodname} Connector for Oracle
  
  