anchor.diff:  [id="compatibility-of-the-debezium-oracle-connector-with-oracle-installation-types"]
   === Compatibility with Oracle installation types
   
  -ifdef::community[]
  +
   An Oracle database can be installed either as a standalone instance or using Oracle Real Application Cluster (RAC).
   The {prodname} Oracle connector is compatible with both types of installation.
  -endif::community[]
  +
   ifdef::product[]
  -The {prodname} Oracle connector is compatible with Oracle installed as a standalone instance.
  +[IMPORTANT]
  +====
  +Using the connector in a RAC environment is a Technology Preview feature only.
  +Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete.
  +Red Hat does not recommend using them in production.
  +These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
  +For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview[https://access.redhat.com/support/offerings/techpreview].
  +====
   endif::product[]
  -
   // Type: concept
   // Title: Schemas that the {prodname} Oracle connector excludes when capturing change events
   [id="schemas-that-the-debezium-oracle-connector-excludes-when-capturing-change-events"]
  
positive.code: <12> The name of the database history topic where the connector writes and recovers 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.
  
  
negative.code: ----
  
  endif::community[]
  ifdef::product[]
  // Type: procedure
  [id="verifying-that-the-debezium-oracle-connector-is-running"]
  