Oracle Requirements

This section describes the requirements, access privileges, and other features of Fivetran HVR when using Oracle for replication.

Supported Platforms

• Learn about the Oracle versions compatible with HVR on our Platform Support Matrix page (6.1.0, 6.1.5, 6.2.0, and 6.2.5).

Supported Capabilities

• Discover what HVR offers for Oracle on our Capabilities for Oracle page (6.1.0, 6.1.5, 6.2.0, and 6.2.5).

Data Management

• Learn how HVR maps data types between source and target DBMSes or file systems on the Data Type Mapping page. For the list of supported Oracle data types and their mapping, see Data Type Mapping for Oracle.

• Understand the character encodings HVR supports for Oracle on the Supported Character Encodings page.

Connecting to Oracle Database or ASM Instance

This section describes how HVR connects to an Oracle Database or ASM instance. HVR uses Oracle’s native TNS connection libraries to establish the connection and supports two connection types: Local connections and TNS connections.

Local connections

A local connection uses the bequeath protocol to establish a direct connection, which bypasses the listener and provides higher performance. It uses an Oracle SID to identify the Oracle Database or ASM instance. To use this connection type, HVR must run on the same machine as the Oracle Database or ASM instance, and you must set ORACLE_HOME to the Oracle home for that instance.

In the HVR UI, to use this method, select the Local connect to database option and enter the SID in the SID field. For CLI and REST API configurations, use the Oracle_SID location property.

TNS connections

A TNS connection uses the Oracle listener to establish the connection. You can use this connection type regardless of whether HVR runs on the same machine as the Oracle instance or on a remote machine. This connection type supports all TNS features, including mTLS. HVR supports the following methods for establishing a TNS connection:

• Connection string
  Connect using a simple host-based connection string in the form HOST[:PORT]/SERVICE_NAME.

• TNS alias
  Connect using a TNS alias that resolves to the Oracle Database or ASM instance. To use this method, you must include TNSNAMES in NAMES.DIRECTORY_PATH in the sqlnet.ora file used for the connection.

• EZCONNECT
  Connect using the EZCONNECT naming method, with a connection identifier in the form ``HOST[:PORT]/SERVICE_NAME_or_SID. To use this method, you must include EZCONNECTinNAMES.DIRECTORY_PATHin thesqlnet.ora` file used for the connection. For more information about EZCONNECT, see Oracle’s Configuring the Easy Connect Naming Method documentation.

In the HVR UI, to use this method, select the Oracle TNS option and enter either a TNS alias or a connect string in the Oracle TNS field. For CLI and REST API configurations, use the Oracle_TNS location property.

Oracle Database Client

HVR requires the full Oracle Database Client to be installed on the machine from which it connects to the Oracle database, except when HVR is installed on the Oracle database server machine. For detailed instructions on downloading and installing the Oracle Database Client, refer to Oracle’s documentation for Linux (also see OS Requirements) and Windows.

The requirement to install the Oracle Database Client depends on how the HVR Hub connects to the Oracle database.

• Connects directly without HVR Agent:

  • When the HVR Hub installed on the Oracle database server connects directly to the Oracle database, you don’t need to install the Oracle Database Client, assuming the full Oracle Database Client was pre-installed with Oracle.
  • When the HVR Hub installed on a separate machine (not the Oracle database server) connects directly to the Oracle database, you must install the full Oracle Database Client on the machine hosting the HVR Hub.

• Connects via HVR Agent:

  • When the HVR Hub connects to the Oracle database through an HVR Agent installed on the Oracle database server, you don’t need to install the Oracle Database Client, assuming the full Oracle Database Client was pre-installed with Oracle.
  • When the HVR Hub connects to the Oracle database through an HVR Agent installed on a separate machine (not the Oracle database server), you must install the full Oracle Database Client on the machine hosting the HVR Agent.

Supported Editions

HVR supports the following Oracle editions:

• Enterprise edition
• Standard edition

Related Articles

• Oracle as Source
  • Capture from Oracle using Direct Redo Access
    • Capture from Oracle ASM
    • Capture from Oracle Data Guard
  • Capture from Oracle using Archive Only
  • Capture from Oracle using LogMiner
    • Capture from Amazon RDS for Oracle
  • Capture from Oracle using BFile
  • Capture from Oracle TDE
  • Capture from Oracle Pluggable Database
  • Capture from Oracle RAC
• Oracle as Target
• Location Connection for Oracle