anchor.diff:  |Specifies the mode that the connector uses to take snapshots of a captured table.
   You can set the following values:
   
  -`initial`:: The snapshot includes the structure and data of captured tables.
  +`initial`:: The snapshot includes the structure and data of a captured table.
   Specify this value to populate topics with a complete representation of the data from the captured tables.
  +
  +`initial_only`:: The snapshot includes the structure and data of captured tables.
  +The connector performs an initial snapshot and then stops, without processing any subsequent changes.
   
   `schema_only`:: The snapshot includes only the structure of captured tables.
   Specify this value if you want the connector to capture data only for changes that occur after the snapshot.
  
positive.code: |`initial`
  |The connector performs a database snapshot as described in the xref:default-workflow-for-performing-an-initial-snapshot[default workflow for creating an initial snapshot].
  After the snapshot completes, the connector begins to stream event records for subsequent database changes.
  
  |`schema_only`
  |The connector captures the structure of all relevant tables, performing all of the steps described in the xref:default-workflow-for-performing-an-initial-snapshot[default snapshot workflow], except that it does not create `READ` events to represent the data set at the point of the connector's start-up (Step 6).
  
negative.code: Database history topics require infinite retention.
  Note this mode is only safe to be used when it is guaranteed that no schema changes happened since the point in time the connector was shut down before and the point in time the snapshot is taken.
  
  After the snapshot is complete, the connector continues to read change events from the database's redo logs except in case of initial_only snapshot mode.
  
  |[[oracle-property-snapshot-locking-mode]]<<oracle-property-snapshot-locking-mode, `+snapshot.locking.mode+`>>
  |_shared_
  