anchor.diff:  }
   ----
   
  -[WARNING]
  -====
  -When using CDB installations, specify `database.pdb.name`. +
  -When using a non-CDB installation, do *not* specify the `database.pdb.name`.
  -====
  +[IMPORTANT]
  +====
  +When you configure a {prodname} Oracle connector for use with an Oracle CDB, you must specify a value for the property `database.pdb.name`, which names the PDB that you want the connector to capture changes from.
  +For non-CDB installation, do *not* specify the `database.pdb.name` property.
  +====
  +
  +.Example: {prodname} Oracle connector configuration for non-CDB deployments
  +[source,json,indent=0]
  +----
  +{
  +    "config": {
  +        "connector.class" : "io.debezium.connector.oracle.OracleConnector",
  +        "tasks.max" : "1",
  +        "database.server.name" : "server1",
  +        "database.hostname" : "<oracle ip>",
  +        "database.port" : "1521",
  +        "database.user" : "c##dbzuser",
  +        "database.password" : "dbz",
  +        "database.dbname" : "ORCLCDB",
  +        "database.history.kafka.bootstrap.servers" : "kafka:9092",
  +        "database.history.kafka.topic": "schema-changes.inventory"
  +    }
  +}
  +----
  +
   endif::community[]
   
   For the complete list of the configuration properties that you can set for the {prodname} Oracle connector, see {link-prefix}:{link-oracle-connector}#oracle-connector-properties[Oracle connector properties].
  
positive.code:     }
  }
  ----
  
  [[oracle-database-mode]]
  === Pluggable vs Non-Pluggable databases
  
  The {prodname} Oracle connector supports both deployment practices of pluggable databases (CDB mode) as well as non-pluggable databases (non-CDB mode).
  
  .Example: {prodname} Oracle connector configuration for non-CDB (Non Pluggable Database) installations
  [source,json,indent=0]
  ----
  {
    "config": {
      "connector.class" : "io.debezium.connector.oracle.OracleConnector",
      "tasks.max" : "1",
      "database.server.name" : "server1",
      "database.hostname" : "<oracle ip>",
      "database.port" : "1521",
      "database.user" : "c##dbzuser",
      "database.password" : "dbz",
      "database.dbname" : "ORCLCDB",
      "database.history.kafka.bootstrap.servers" : "kafka:9092",
      "database.history.kafka.topic": "schema-changes.inventory"
    }
  }
  ----
  
  .Example: {prodname} connector configuration for CDB (Pluggable Database) installations
  [source,json,indent=0]
  ----
  {
  
negative.code: <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 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]
  