High-Volume Agent Oracle Setup Guide

1. Create folder structure:

   i. As the root user, create the HVA installation directory (for example, /opt/fivetran) and set the appropriate owner (for example, oracle) and group (for example, oinstall) for it.

   mkdir /opt/fivetran
   chown -R oracle:oinstall /opt/fivetran
   

   NOTE: If you are using Oracle RAC with shared storage (for example, ACFS), ensure that the /opt/fivetran folder is created on the shared storage and mounted on all nodes in the cluster. If you are not using the shared storage, the /opt/fivetran folder must be created on all nodes in the cluster.

   ii. In the /opt/fivetran directory, create three key subdirectories hvr_home, hvr_config, and hvr_tmp:

   mkdir -p /opt/fivetran/hvr_home
   mkdir -p -m 01775 /opt/fivetran/hvr_config/etc /opt/fivetran/hvr_tmp
   

2. Configure environment:

   NOTE: If using Oracle RAC, ensure this step is performed on all nodes in the cluster.

   i. Configure the HVR_HOME, HVR_CONFIG, and HVR_TMP environment variables to point to the relevant HVA installation subdirectories:

   HVR_HOME=/opt/fivetran/hvr_home
   HVR_CONFIG=/opt/fivetran/hvr_config
   HVR_TMP=/opt/fivetran/hvr_tmp
   

   ii. Add the $HVR_HOME/bin executable directory path to the environment variable PATH:

   export PATH=$PATH:$HVR_HOME/bin
   

   iii. Add the environment variables and the executable directory path into the startup file (for example, .profile or .bash_profile):

   export HVR_HOME=/opt/fivetran/hvr_home
   export HVR_CONFIG=/opt/fivetran/hvr_config
   export HVR_TMP=/opt/fivetran/hvr_tmp
   export PATH=$PATH:$HVR_HOME/bin
   

3. Install agent:

   NOTE: If you are using Oracle RAC with the /opt/fivetran folder created on shared storage, you need to perform this step only once. If you are not using shared storage, you must repeat this step for all nodes in the cluster.

   Navigate into the $HVR_HOME location and extract the contents of the HVA installation file (for example, fivetran-6.1.0_26-hub_and_agent-linux_glibc2.12-x64-64bit_ga_patch.tar.gz):

   cd $HVR_HOME
   tar xzf /tmp/fivetran-6.1.0_26-hub_and_agent-linux_glibc2.12-x64-64bit_ga_patch.tar.gz
   

   Once complete, the agent and all required components are installed into the $HVR_HOME location (/opt/fivetran/hvr_home).

1. Create folder structure:

   i. Create the HVA installation base directory (for example, /opt/fivetran) and set the appropriate owner, group, and permissions on it by running the following command as user root:

   mkdir /opt/fivetran
   chown -R oracle:oinstall /opt/fivetran
   

   NOTE: If you are using Oracle RAC with shared storage (for example, ACFS), ensure that the /opt/fivetran folder is created on the shared storage and mounted on all the nodes in the cluster. If you are not using shared storage, the /opt/fivetran folder must be created on all the nodes in the cluster.

   ii. Within the /opt/fivetran directory, create three key subdirectories: hvr_home, hvr_config, and hvr_tmp:

   mkdir -p /opt/fivetran/hvr_home
   mkdir -p -m 01775 /opt/fivetran/hvr_config /opt/fivetran/hvr_tmp
   

2. Configure environment:

   NOTE: If you are using Oracle RAC, make sure you perform this step on all the nodes in the cluster.

   i. Configure the environment variables HVR_HOME, HVR_CONFIG, and HVR_TMP:

   export HVR_HOME=/opt/fivetran/hvr_home
   export HVR_CONFIG=/opt/fivetran/hvr_config
   export HVR_TMP=/opt/fivetran/hvr_tmp
   

   ii. Add the $HVR_HOME/bin executable directory path to the environment variable PATH:

   export PATH=$PATH:$HVR_HOME/bin
   

   iii. Add the HVR environment variables and the executable directory path to the startup file (for example, .profile or .bash_profile):

   export HVR_HOME=/opt/fivetran/hvr_home
   export HVR_CONFIG=/opt/fivetran/hvr_config
   export HVR_TMP=/opt/fivetran/hvr_tmp
   export PATH=$PATH:$HVR_HOME/bin
   

3. Install agent:

   NOTE: If you are using Oracle RAC with the /opt/fivetran folder created on shared storage, you must perform this step only once. If you are not using shared storage, you must perform this step for all nodes in the cluster.

   Go to the $HVR_HOME location and extract the installer file to install HVA and all the other required components:

   cd $HVR_HOME
   gzip -dc /tmp/hvr-*-agent_only-*.tar.gz | tar xf -
   

NOTE: The size of the installer is less than 150 MB. After you install HVA, you can delete the installer file as you no longer need them.

NOTE: The HVA installation file for Windows is available in the .exe and .zip formats. The compressed file (.zip) distribution is normally used as an alternative for the Windows executable based (.exe) distribution. The steps to install the HVA are also different for both formats.

1. Create folder structure:

   As the Administrator user, create an HVA installation directory (for example, C:\hvr) with three subdirectories hvr_home, hvr_config, and hvr_tmp:

   mkdir C:\hvr\hvr_home
   mkdir C:\hvr\hvr_config
   mkdir C:\hvr\hvr_tmp
   

2. Configure environment:

   1. Configure the HVR_HOME, HVR_CONFIG, and HVR_TMP environment variables, each pointing to the relevant HVA installation directories hvr_home, hvr_config, and hvr_temp:

      NOTE: The following instructions assume that the directories are created inside the C:\hvr directory. Use your installation directory if it differs from C:\hvr.

      i. Navigate to Control Panel ▶ System and Security ▶ System ▶ Advanced system settings.

      ii. Under the Advanced tab, click Environment Variables....

      

      iii. In the System variables or User Variables for user_name section, click New.

      iv. Enter Variable name (e.g, HVR_HOME) and Variable value (e.g, C:\hvr\hvr_home).

      

      v. Click OK. Repeat the above steps iii and iv for environment variables HVR_CONFIG and HVR_TMP.

   2. Add the HVR executable directory path to the environment variable Path:

      i. In the System variables or User Variables for user_name section, from the list of variables, select Path and click Edit....

      

      ii. In the Edit environment variable dialog, click New and enter the path for the HVA executable. Click OK.

      

3. Install HVA:

   Navigate to the $HVR_HOME directory (C:\hvr\hvr_home) and extract the contents of the downloaded .zip file.

   

   Once completed, the HVA and all required components are installed into the $HVR_HOME directory (C:\hvr\hvr_home).

NOTE: The HVA installation file for Windows is available in the .exe and .zip formats. The compressed file (.zip) distribution is normally used as an alternative for the Windows executable based (.exe) distribution. The steps to install the HVA are also different for both formats.

1. Run the downloaded .exe file (for example, hvr-6.1.0_10-hub_and_agent-windows-x64-64bit_ga_patch-setup.exe).

2. In the setup wizard dialog, click Next.

   

3. Read the License Agreement, select I accept the agreement and then click Next.

   

4. Specify the HVA installation directories and click Next.

   

5. Click Next to create a program folder for the HVA.

   

6. Select High-Volume Agent (HVA) and click Next.

   

7. Enter a value for Agent Listener Port and click Next.

   

8. Select the user account to run the HVA service.

   • If you select Specified user, enter the values for User, Password, Confirm Password and click Next.

     NOTE: For user with Windows authentication (if applicable), specify your Active Directory domain and username in the format <domain>\<username>.

     

   • If you select Local System account, click Next.

     

9. Select Add HVR_HOME, HVR_CONFIG, and HVR_TMP (if required) and click Next.

   This is to set the environment variables HVR_HOME, HVR_CONFIG, and HVR_TMP in your operating system. These variables point to the corresponding directories created in step 4 above.

   

10. Click Next to initiate the installation.

    

11. Click Finish to start the HVA service.

    

    Once the installation is complete, the HVA and all required components are installed into the $HVR_HOME directory (C:\hvr\hvr_home).

On Linux, there are two key options:

• For Oracle non-RAC, add agent to systemd

  Expand for instructions

  To configure systemd, perform the following steps as user root:

  1. Create a service file called agentListener.service in the /etc/systemd/system directory. The agentListener.service should contain the following:

     NOTE: Change the User=<your_linux_username> field to the Linux user that installed the HVA.

     [Unit]
     Description=Fivetran Agent Listener
     
     [Service]
     # The process start-up type 'forking' allows this service to spawn new processes
     Type=forking
     Environment="HVR_HOME=/opt/fivetran/hvr_home"
     Environment="HVR_CONFIG=/opt/fivetran/hvr_config"
     Environment="HVR_TMP=/opt/fivetran/hvr_tmp"
     # The user that owns HVR_HOME, HVR_CONFIG, etc.
     User=<your_linux_username>
     ExecStart=/opt/fivetran/hvr_home/bin/hvragentlistener -d 4343
     # Restart this service after a crash
     Restart=always
     # The number of seconds to wait before attempting a restart
     RestartSec=5s
     
     [Install]
     WantedBy=multi-user.target
     

  2. To enable and start the service, execute the following commands:

     sudo systemctl enable agentListener.service
     sudo systemctl start agentListener.service
     

  3. To verify whether the service is active, execute the following command:

     sudo systemctl status agentListener.service
     

  The output should show active (running) in green.

• For Oracle RAC, add agent as a cluster resource

  Expand for instructions

  If you are using Oracle RAC, review the Oracle ASM Configuration section.

  To add the High-Volume Agent to an Oracle RAC cluster as a cluster resource, follow the steps below.

  In the examples provided, we use the following naming:

  • Virtual IP Name: fivetran-vip
  • Oracle RAC node names: racnode1 and racnode2
  • Installation path for agent software: /opt/fivetran
  • Owner of the agent software: the Oracle software owner, referred to as oracle

  
  

  Step 1: Create a Virtual IP

  The Virtual IP (VIP) is designated for exclusive use by the High-Volume Agent. This IP will will only be active on one node at a time within the cluster, ideally on the node where the agent listener is running, using a shared storage system such as an ACFS file system.

  Commands to create the Virtual IP:

  NOTE: The IP address 10.1.1.159 is an example. You must use an IP address from your Oracle RAC public network subnet.

  appvipcfg create -network=1 -ip=10.1.1.159 -vipname=fivetran-vip -user=root
  crsctl setperm resource fivetran-vip -u user:oracle:r-x
  crsctl setperm resource fivetran-vip -u user:grid:r-x
  crsctl start resource fivetran-vip -n racnode1
  

  Step 2: Agent Action Script

  To add the agent as a resource in Oracle Clusterware, use an action script.

  Example of the action script

    #!/bin/bash
    #
    # Description:
    #  A sample Fivetran High-Volume Agent action script
    #
    # set following to ensure oraenv is picked up from /usr/local/bin
    # set -x
    
    export PATH=/usr/local/bin:$PATH
    
    # set Fivetran-specific environment
    export HVR_HOME=/opt/fivetran/hvr_home
    export HVR_CONFIG=/opt/fivetran/hvr_config
    export HVR_TMP=/opt/fivetran/hvr_tmp
    export FTAGENT_BASE=/opt/fivetran
    
    # update agent port if different
    export AGENT_PORT=4343
    
    
    ###########
    # Function to set the oracle environment
    # Note that it is making use of /etc/oratab
    # Your database must be listed on all nodes in the cluster
    ###########
    set_env ()
    {
      export ORAENV_ASK=NO
      export ORACLE_SID=$1
      . oraenv >> /dev/null
      export ORAENV_ASK=YES
    }
    
    
    ###########
    # Helper function to rename logfiles to keep clean history
    ###########
    rename_log () {
      utcdate=`date -u +"%Y-%m-%dT%H.%M.%SZ"`
      if [ -f $HVR_CONFIG/logs/hvragentlistener${AGENT_PORT}.log ]; then
        mv $HVR_CONFIG/logs/hvragentlistener${AGENT_PORT}.log $HVR_CONFIG/logs/hvragentlistener${AGENT_PORT}.log.${utcdate}
      fi
    }
    
    
    ###########
    ## Main
    ###########
    
    # This is logged to CRSD agent log file
    echo "`date` Action script '$_CRS_ACTION_SCRIPT' for resource [$_CRS_NAME] called for action $1"
    
    # Note that you must update the value for the current_host below to match your environment.
    # in the setup below the rac node 1 is called "racnode1"
    current_host=`hostname -s`
    if [ "$current_host" == "racnode1" ]; then
      set_env DEV1
    else
      set_env DEV2
    fi
    
    
    cd $HVR_HOME/bin
    
    
    case "$1" in
         'start')
               NUM=`ps -ef | grep hvragentlistener | egrep -v 'grep|action-script|resource' | wc -l`
               if [ $NUM != 0 ]; then
                 echo "Agent still running, stop first"
             RET=1
           else
                 rename_log
                 ./hvragentlistener -d ${AGENT_PORT}
                 RET=0
                 echo "Start fivetran agent (hvragentlistener) resource with return code $RET"
               fi
         ;;
    
         'stop')
               NUM=`ps -ef | grep hvragentlistener | egrep -v 'grep|action-script|resource' | wc -l`
               if [ $NUM = 0 ]; then
                 ## do a cleanup of pid
                 ./hvragentlistener -k $AGENT_PORT >> $FTAGENT_BASE/ftagent.out 2>&1
             rename_log
                 RET=0
               else
                 ## now stop the agent
                 ./hvragentlistener -k $AGENT_PORT >> $FTAGENT_BASE/ftagent.out 2>&1
                 rename_log
                 NUM=`ps -ef | grep hvragentlistener | grep -v grep | wc -l`
                 if [ $NUM = 0 ]; then
                   RET=0
                 else
                   RET=1
                 fi
               fi
               echo "Stop fivetran agent (hvragentlistener) resource with return code $RET"
         ;;
    
         'check')
               NUM=`ps -ef | grep hvragentlistener | egrep -v 'grep|action-script|resource' | wc -l`
               if [ $NUM = 0 ]; then
                 ## return code 1 for check means OFFLINE
                 RET=1
               else
                 ## return code 0 for check means ONLINE
                 RET=0
               fi
               echo "Running check fivetran agent (hvragentlistener) resource with return code $RET"
         ;;
    
         'clean')
               for c1 in `ps -ef|grep hvragentlistener |egrep -v 'grep|action-script|resource'| awk '{print $2}'` ;
               do
                 echo "...force kill fivetran agent (hvragentlistener) pid $c1"
                 kill -9 $c1
               done
               ## do some cleanup
               ./hvragentlistener -k $AGENT_PORT >> $FTAGENT_BASE/ftagent.out 2>&1
               rename_log
               RET=0
               echo "Running clean fivetran agent (hvragentlistener) resource with return code $RET"
         ;;
    esac
    
    if [ $RET -eq 0 ]; then
      exit 0
    else
      exit 1
    fi
  

  
  

  Step 3: Create cluster resource

  Once the action script is in place, use it to create the cluster resource. Store the script in a shared location accessible to all nodes (we recommend using ACFS), for example /opt/fivetran/hvr_config/action-script.scr.

  The cluster resource created will support the agent and is configured to depend on the VIP created in Step 1 above. If this VIP moves between nodes, the agent will automatically move with it.

  Command to run as the grid user:

  crsctl add resource ftagent -type cluster_resource \
  -attr "ACTION_SCRIPT=/opt/fivetran/hvr_config/action-script.scr, RESTART_ATTEMPTS=3, START_TIMEOUT=60, STOP_TIMEOUT=60, CHECK_INTERVAL=10, \
  START_DEPENDENCIES='hard(fivetran-vip) pullup(fivetran-vip)', STOP_DEPENDENCIES='hard(fivetran-vip)', \
  ACL='owner:oracle:rwx,pgrp:oinstall:rwx,other::r--', PLACEMENT='favored', HOSTING_MEMBERS='racnode1 racnode2'"
  

  Step 4: Start and stop cluster resource

  To effectively manage cluster resources, see the Oracle Clusterware Administration and Deployment Guide.

  Commands to monitor and control the agent:

  crsctl status resource ftagent
  crsctl start resource ftagent -n <rac-node> -f
  crsctl stop resource ftagent -f
  

  The following command relocates the Virtual IP (fivetran-vip) to another node in the cluster. This will also stop the agent and move it along with the Virtual IP:

  crsctl relocate resource fivetran-vip -n <rac-node> -f
  

  The following command moves the Virtual IP from racnode1 to racnode2:

  root@rac1 ~ : crsctl relocate resource fivetran-vip -n racnode2 -f
  CRS-2673: Attempting to stop 'ftagent' on 'racnode1'
  CRS-2677: Stop of 'ftagent' on 'racnode1' succeeded
  CRS-2673: Attempting to stop 'fivetran-vip' on 'racnode1'
  CRS-2677: Stop of 'fivetran-vip' on 'racnode1' succeeded
  CRS-2672: Attempting to start 'fivetran-vip' on 'racnode2'
  CRS-2676: Start of 'fivetran-vip' on 'racnode2' succeeded
  CRS-2672: Attempting to start 'ftagent' on 'racnode2'
  CRS-2676: Start of 'ftagent' on 'racnode2' succeeded
  

INFO: In Solaris 10 and higher, the /etc/inetd.conf file has been replaced by SMF manifests. All inetd services are now configured/controlled under the SMF.

To configure the SMF service, perform the following steps as user root:

1. In the /etc/services file, add the following line specifying the name (for example, hva) and the TCP/IP port number of the agent:

   hva 4343/tcp 
   

2. Create a temporary file (for example, /tmp/inet.hvr) containing the following inetd.conf-style entry for the agent:

   TIP: Option -E defines the environment variables.

   hva stream tcp nowait oracle /opt/fivetran/hvr_home/bin/hvragent hvragent -EHVR_HOME=/opt/fivetran/hvr_home -EHVR_CONFIG=/opt/fivetran/hvr_config -EHVR_TMP=/opt/fivetran/hvr_tmp
   

   NOTE: The user must be set to the user (for example, oracle) under which the HVA is installed/running. The service name (for example, hva) specified in this temporary file must match with the name specified (step #1) in the /etc/services file. The above configuration should be defined in a single line (without manual line break).

3. Import the temporary file (for example, /tmp/inet.hvr) into System Management Facility (SMF) using the inetconv command.

   For example:

   inetconv -i /tmp/inet.hvr
   

4. Enable the service using the inetadm command.

   For example:

   inetadm -e svc:/network/hvr/tcp:default
   

5. Refresh the service using the svcadm command:

   svcadm refresh inetd
   

To configure the inetd service, perform the following steps as user root:

1. In the /etc/services file, add the following line specifying the name (for example, hva) and the TCP/IP port number of the agent:

   hva 4343/tcp
   

2. Add the following line to the /etc/inetd.conf file:

   TIP: Option -E defines the environment variables.

   hva stream tcp nowait oracle /opt/fivetran/hvr_home/bin/hvragent hvragent -EHVR_HOME=/opt/fivetran/hvr_home -EHVR_CONFIG=/opt/fivetran/hvr_config -EHVR_TMP=/opt/fivetran/hvr_tmp
   

   NOTE: The user must be set to the user (for example, oracle) under which the agent is installed/running. The service name (for example, hva) specified in the inetd.conf file must match with the name specified (step #1) in the /etc/services file. The above configuration should be defined in a single line (without manual line break).

3. Reload or restart the inetd service to apply the changes. For information about restarting the inetd service, refer to the operating system documentation.

IMPORTANT: Your database version must be 12.2 or above to connect directly. If your database version is 12.1 or below, connect using SSH.

Fivetran connects directly to the High-Volume Agent installed on the database host. All communication between Fivetran and the HVA is encrypted. The HVA has a direct connection to your Oracle database.

To connect directly, configure your firewall and/or other access control systems to allow incoming connections to your Oracle database host where the agent is installed. Restrict access to the database port (usually 1521) and the agent port (usually 4343) from Fivetran's IPs for your database's region. How you do this varies based on how your Oracle database is hosted, whether on a cloud platform, on-premises, or otherwise.

Fivetran connects to your database through an SSH tunnel, providing secure communication between Fivetran processes and your database host. This connection method can be used when direct access to your database port isn’t possible or if you require a more secure connection. It allows Fivetran to securely access your database while maintaining your network’s integrity.

Once the SSH tunnel is configured, Fivetran connects to the SSH server using the specified SSH host, port, and user credentials. The SSH server then forwards the connection to the database host through HVA, which listens on a specific port (default 4343). The SSH server must be configured to accept connections from the Fivetran's IP.

You may need to configure your firewall or any relevant access control systems to allow incoming connections to your Oracle database port (usually port 1521) from the IP address of your SSH tunnel server.

To connect using SSH, follow our SSH connection setup instructions.

To connect using reverse SSH, follow our Reverse SSH connection setup instructions.

NOTE: If you want Fivetran to tunnel SSH over TLS, you must first enable TLS on your database.

IMPORTANT: You must have a Business Critical plan to use private networking.

Private networking enables communication between private networks and services without exposing traffic to the public internet. Private networking is the most secure connection method.

We support the following providers:

• AWS PrivateLink – used for VPCs and AWS-hosted or on-premises services. See our AWS PrivateLink setup guide for details.
• Azure PrivateLink – used for Virtual Networks (VNets) and Azure-hosted or on-premises services. See our Azure PrivateLink setup guide for details.
• Google Cloud Private Service Connect – used for VPCs and Google-hosted or on-premises services. See our Google Cloud Private Service Connect setup guide for details.

Fivetran connects to the HVA through the Proxy Agent, providing secure communication between Fivetran processes and your database host. The Fivetran Proxy Agent should be installed in your network to create an outbound connection to Fivetran's cloud. To connect using Proxy Agent, follow our Proxy Agent documentation.

1. Connect to your Oracle database as an Admin user.

2. Create a user for Fivetran's exclusive use and grant the user permission to connect to your database. Replace <username> and <password> with a username and password of your choice:

    CREATE USER <username> IDENTIFIED BY <password>;
    GRANT CREATE SESSION TO <username>;
   

3. Ensure the Fivetran user has the appropriate number of sessions available. You must have at least 15 sessions if the profile name of the Fivetran user is set to DEFAULT. Otherwise, you must have at least 5 sessions.

   i. Verify the profile name associated with your Fivetran user by executing the following command:

    SELECT USERNAME, PROFILE FROM DBA_USERS WHERE USERNAME='<username>'
   

   ii. Note the profile name from the query results.

   iii. If the Fivetran user's profile is DEFAULT, set the session limit to at least 15 sessions:

    ALTER PROFILE DEFAULT LIMIT SESSIONS_PER_USER 15;
   

   iv. If the user has a different profile, replace DEFAULT in the command above with the actual profile name obtained from the query. Adjust the session limit according to your specific requirements, ensuring a minimum of 5 sessions for non-default profiles.

4. Grant read-only access permissions on the specific schema and table you want to sync:

   NOTE: Oracle databases default to storing all object names, such as table names and column names, in uppercase. If you wish to use mixed case or maintain the case sensitivity of your identifiers, you must enclose the names in double quotes. This applies to any SQL identifiers, including table names, column names, and other database object names.

    GRANT SELECT ON "<schemaA>"."<tableA>" TO <username>;
    GRANT SELECT ON "<schemaA>"."<tableB>" TO <username>;
    GRANT SELECT ON "<schemaB>"."<tableC>" TO <username>;
   
   

   Alternatively, grant access to all tables.

   GRANT SELECT ANY TABLE TO <username>;
   

1. Connect to your Oracle database as an admin user.

2. Create a common user at the container level. Create the user with the container as the active session and grant the following permissions:

    ALTER SESSION SET CONTAINER=CDB$ROOT;
    CREATE USER <username> IDENTIFIED BY <password> CONTAINER=ALL;
    GRANT CREATE SESSION, ALTER SESSION, SET CONTAINER TO <username> CONTAINER=ALL;
    ALTER USER <username> SET CONTAINER_DATA=ALL CONTAINER=CURRENT;
   

3. Ensure your Fivetran user has at least 15 sessions per user in both a constant database and a pluggable database. Run the following command at the container level and the pluggable level to check the parameter:

    col username for a12
    col profile for a19
    col limit for a12
    set lines 299
    select a.username,b.PROFILE,b.RESOURCE_NAME,b.limit from dba_users a , dba_profiles b where a.profile=b.profile
    and b.RESOURCE_NAME='SESSIONS_PER_USER' and a.username='<username>';
   

4. Switch to the desired pluggable database (<PDB>) and grant read-only access permissions on the specific schema and table you want to sync.

   NOTE: Oracle databases default to storing all object names, such as table names and column names, in uppercase. If you wish to use mixed case or maintain the case sensitivity of your identifiers, you must enclose the names in double quotes.

   ALTER SESSION SET CONTAINER=<PDB>;
   

    GRANT SELECT ON "<schemaA>"."<tableA>" TO <username>;
    GRANT SELECT ON "<schemaA>"."<tableB>" TO <username>;
    GRANT SELECT ON "<schemaB>"."<tableC>" TO <username>;
   

   Alternatively, you can grant access to all tables.

    GRANT SELECT ANY TABLE TO <username>;
   

To check the status of supplemental logging at database-level:

SELECT supplemental_log_data_min, supplemental_log_data_pk, supplemental_log_data_all FROM v$database;

To check the status of supplemental logging at table-level:

SELECT log_group_type FROM all_log_groups WHERE table_name='<schema>.<table>';

To disable supplemental logging at database-level:

 ALTER DATABASE DROP SUPPLEMENTAL LOG DATA;

To disable supplemental logging at table-level:

• For a table with a primary key:

   ALTER TABLE "<schema>"."<table>" DROP SUPPLEMENTAL LOG DATA (PRIMARY KEY) COLUMNS;
  

• For a table without a primary key or unique index:

   ALTER TABLE "<schema>"."<table>" DROP SUPPLEMENTAL LOG DATA (ALL) COLUMNS;
  

• For a table without a primary key but with a unique index:

   ALTER TABLE "<schema>"."<table>" DROP SUPPLEMENTAL LOG GROUP "<group_name>";
  

1. Connect to the ASM instance using the SYS account with SYSASM role.

2. Create a new ASM user and grant the SYSASM privilege to this user:

   CREATE USER <asm_user> IDENTIFIED by <asm_user_password>;
   GRANT SYSASM TO <asm_user>;
   

3. Grant the following privileges to the Fivetran user. These permissions allow Fivetran to query the status of ASM diskgroups and client information:

   GRANT SELECT ON sys.v_$asm_diskgroup_stat TO <username>;
   GRANT SELECT ON sys.v_$asm_client TO <username>;
   

To enable direct access to ASM, HVA requires a TNS entry to connect to the ASM instance using a bequeath connection. You need to create a TNSNAMES.ora entry for each ASM instance on every cluster node.

In an Oracle RAC setup, ASM is managed by Oracle Grid Infrastructure (Clusterware). The Grid Infrastructure has its own TNSNAMES.ORA file, located in the Grid Infrastructure Oracle Home ($GRID_HOME/network/admin/), distinct from the database Oracle Home ($DB_HOME/network/admin/). To avoid connection issues, add the TNS entry for the ASM instance (FASM in the below example) to the TNSNAMES.ORA file in both the Grid Infrastructure home and the database home.

For example, on a two-node Oracle RAC with +ASM1 on node 1 and +ASM2 on node 2, add the following entry in both locations:

TNS Entry Example on Node 1:

FASM =
   (DESCRIPTION =
      (ADDRESS = (PROTOCOL = BEQ)
      (PROGRAM = /u01/app/19.0.0/grid/bin/oracle)
      (ARGV0 = oracle+ASM1)
      (ARGS = '(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=BEQ)))')
      (ENVS = 'ORACLE_HOME=/u01/app/19.0.0/grid,ORACLE_SID=+ASM1'))
      (CONNECT_DATA =
         (SERVICE_NAME = +ASM)
         (INSTANCE_NAME = +ASM1)
      )
   )

TNS Entry Example on Node 2:

FASM =
   (DESCRIPTION =
      (ADDRESS = (PROTOCOL = BEQ)
      (PROGRAM = /u01/app/19.0.0/grid/bin/oracle)
      (ARGV0 = oracle+ASM2)
      (ARGS = '(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=BEQ)))')
      (ENVS = 'ORACLE_HOME=/u01/app/19.0.0/grid,ORACLE_SID=+ASM2'))
      (CONNECT_DATA =
         (SERVICE_NAME = +ASM)
         (INSTANCE_NAME = +ASM2)
      )
   )

When entering ASM instance details in the connector setup form, use the ASM TNS value as 'FASM'.

NOTE: Ensure that the TNSNAMES.ORA entry is consistent across all required Oracle homes ($GRID_HOME and $DB_HOME) to avoid potential connection errors when HVA attempts to access the ASM instance.