anchor.diff:  ----
   
   endif::community[]
  -
  -For the complete list of the configuration properties that you can set for the {prodname} Oracle connector, see xref:{link-oracle-connector}#oracle-connector-properties[Oracle connector properties].
  -
  -ifdef::community[]
  -You can send this configuration with a `POST` command to a running Kafka Connect service.
  -The service records the configuration and starts a connector task that performs the following operations:
  -
  -* Connects to the Oracle database.
  -* Reads the redo log.
  -* Records change events to Kafka topics.
  -
  -[[oracle-adding-connector-configuration]]
  -=== Adding connector configuration
  -
  -To start running a {prodname} Oracle connector, create a connector configuration, and add the configuration to your Kafka Connect cluster.
  -
  -.Prerequisites
  -
  -* xref:{link-oracle-connector}#setting-up-oracle[Oracle is configured for use with {prodname}].
  -* The {prodname} Oracle connector is installed.
  -
  -.Procedure
  -
  -. Create a xref:{link-oracle-connector}#oracle-example-configuration[configuration] for the Oracle connector.
  -
  -. Use the link:{link-kafka-docs}/#connect_rest[Kafka Connect REST API] to add that connector configuration to your Kafka Connect cluster.
  -endif::community[]
  -
  -.Results
  -
  -After the connector starts, it xref:{link-oracle-connector}#oracle-snapshots[performs a consistent snapshot] of the Oracle databases that the connector is configured for.
  -The connector then starts generating data change events for row-level operations and streaming the change event records to Kafka topics.
  -
   ifdef::product[]
   // Type: procedure
   [id="verifying-that-the-debezium-oracle-connector-is-running"]
  
positive.code: |[[oracle-property-database-url]]<<oracle-property-database-url, `+database.url+`>>
  |No default
  |Specifies the raw database JDBC URL. Use this property to provide flexibility in defining that database connection.
  ifdef::community[]
  Valid values include raw TNS names and RAC connection strings.
  endif::community[]
  ifdef::product[]
  Valid values include raw TNS names connection strings.
  endif::product[]
  
  |[[oracle-property-database-pdb-name]]<<oracle-property-database-pdb-name, `+database.pdb.name+`>>
  
negative.code: |[[oracle-property-column-include-list]]<<oracle-property-column-include-list, `+column.include.list+`>>
  |No default
  |An optional comma-separated list of regular expressions that match the fully-qualified names of columns that want to include in the change event message values.
  Fully-qualified names for columns use the following format: +
   +
  `_<Schema_name>.<table_name>.<column_name>_` +
   +
  The primary key column is always included in an event's key, even if you do not use this property to explicitly include its value.
  If you include this property in the configuration, do not also set the `column.exclude.list` property.
  