anchor.diff:      }
   }
   ----
  -
  +endif::community[]
  +
  +// Type: concept
  +// ModuleID: configuration-of-container-databases-and-non-container-databases
  +// Title: Configuration of container databases and non-container-databases
  +[[pluggable-vs-non-pluggable-databases]]
  +=== Pluggable vs Non-Pluggable databases
   [[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
  +
  +
  +Oracle Database supports the following deployment types:
  +
  +Container database (CDB):: A database that can contain multiple pluggable databases (PDBs).
  +Database clients connect to each PDB as if it were a standard, non-CDB database.
  +
  +Non-container database (non-CDB):: A standard Oracle database, which does not support the creation of pluggable databases.
  +
  +
  +ifdef::community[]
  +
  +
  +.Example: {prodname} connector configuration for CDB deployments
   [source,json,indent=0]
   ----
   {
  
positive.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 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]
  
negative.code: // Category: debezium-using
  // Type: assembly
  [id="debezium-connector-for-oracle"]
  = {prodname} Connector for Oracle
  
  