High-Volume Agent SAP ECC on Oracle Setup Guide Beta

Follow the instructions listed here to replicate data from SAP ECC on Oracle to your destination using Fivetran.

The Fivetran connector setup form lets you specify essential information for creating an Oracle connection, such as database credentials, connection method, High-Volume Agent (HVA) connection credentials, and other database-specific parameters. You need to set up your infrastructure, including network and database configurations, to obtain the parameter values required for this setup form.

Before entering details into the setup form, you must perform the following configurations:

• Ensure the prerequisites are in place
• Install and configure HVA
• Configure your network
• Configure database access and permissions:
  • Create a user with read-only access
  • Configure ARCHIVELOG mode
  • Enable supplemental logging
  • Configuring Direct Capture

For detailed instructions, refer to the relevant sections below.

Prerequisites

To connect your Oracle database to Fivetran using the HVA, you need:

• A Fivetran account with an Enterprise or Business Critical plan
• Oracle 11g R2 or above
• Your database host IP address:
  • If using Oracle RAC, either an Application Virtual IP (VIP) or the public IP of a node
  • The IP address must be accessible from Fivetran directly, using an SSH tunnel, private networking, or Proxy Agent
• Your database port (usually 1521)
• Connection string for the agent to use to connect to your database:
  • For a single instance, specify Oracle SID
  • If using Oracle RAC or Multitenant (pluggable) databases, specify a Service Name (it must have an entry in your local tnsnames.ora)
• High-Volume Agent (HVA) installed on your Oracle database host
  • The HVA IP address and port number (usually 4343)
• Supplemental logging enabled in your database
• ARCHIVELOG mode enabled in your database
• Oracle database schema name under which the SAP tables reside, for example, SAPSR3

HVA installation and configuration

This section guides you through the process of installing the HVA on various operating systems, as well as configuring and starting the HVA. You will find information on compatibility checks, disk space requirements, and system permissions necessary for installation. Additionally, you will learn how to integrate the HVA into your system's startup to ensure it runs automatically upon boot.

HVA requirements

Before proceeding with the HVA installation, ensure that you have the following prerequisites in place:

• Compatibility: Verify that the HVA version is compatible with your operating system and DBMS. Refer to the COMPATIBILITY section in the relevant release notes on the Downloads page of your Fivetran dashboard.

• Sufficient disk space: Ensure that the machine where you want to install the HVA has ample disk space. We recommend a minimum of 10 GB of available disk space.

• HVA installation: Download the HVA installation file from the Downloads page of your Fivetran dashboard. Select the installation file for your database server's operating system.

  IMPORTANT: You must install HVA on the host where your Oracle database is running, or on a host that has access to the database.

• Oracle RAC: You have the following options:

  • Install the agent on one node. This does not provide High-Availability (HA) if the node goes down.
  • Install the agent on all the nodes in the Oracle RAC.
  • Install the agent on a shared storage system that is visible in all nodes. For example, we recommend this approach for ACFS file system.

• Oracle Active Data Guard: Install the agent on the standby nodes.

• System permissions: HVA requires permission to read Oracle's redo and archive files at the operating system-level. You can achieve this in one of the following ways:

  • Install and run the agent under the database owner user account (for example, oracle).
  • Install and run the agent under a different user account (for example, fivetran_user) that must be a member of Oracle's default operating system group. Typically, this is either oinstall or dba on Unix-based systems and ora_dba on Windows.

Install HVA

Follow the instructions below to install the HVA.

Configure HVA

Follow the instructions below to configure the HVA:

1. Create an HVA user to set up your Fivetran connector. Enter and confirm the password when prompted.

   NOTE: The password must be at least 10 characters long and must not contain any special characters.

   hvragentuserconfig -c <username>  
   

2. Make a note of the username and password. You will need them to configure your connector in the Fivetran dashboard.

3. Run the following command to disable the setup mode:

   hvragentconfig Setup_Mode_Timed_Until=
   

4. Run the following command to extract the HVA public certificate:

   hvragentconfig Agent_Server_Public_Certificate
   

5. Save the output value of the Agent_Server_Public_Certificate. You will need it to configure your connector in the Fivetran dashboard.

Start HVA

Perform the following steps as the user who runs HVA.

To start the agent, you need to run the hvragentlistener command with the -d flag followed by the port number that you want to run on. In the example, the default port is 4343.

hvragentlistener -d 4343

NOTE: For Oracle RAC, configuration using shared storage is highly recommended. Running the agent as a cluster resource and only on one node at a time is the preferred setup. If you do not want to follow this approach, you can run the agent only on one of the nodes in the cluster. If this node fails, you will need to start the agent on one of the other nodes in the cluster.

Add HVA to system autostart (Linux only)

After completing the initial HVA setup, you must add the agent to your system’s startup and shutdown procedures.

Network connection

This section outlines the methods available for connecting Fivetran to your SAP ECC on Oracle system.

Choose connection method

Decide on your preferred method for connecting Fivetran to your SAP ECC on Oracle system, and then configure the necessary settings for that method.

Database access and configuration

This section provides instructions for creating a dedicated database user for Fivetran and configuring the necessary user permissions. It also includes steps to configure ARCHIVELOG mode, enable supplemental logging, and configure Direct Capture.

Create user and grant read-only access

This section guides you through creating a dedicated user for Fivetran in your Oracle database and granting read-only access to the user. Separate instructions are provided for standalone databases and multitenant container databases.

Check the following important considerations before proceeding:

• Minimum database sessions: The Fivetran database user requires a minimum of eight concurrent database sessions. By default, Oracle allows unlimited sessions per user. If you wish to limit the number of concurrent sessions for the Fivetran user, ensure it is set to at least eight.
• Case-sensitive usernames: Oracle usernames are case-sensitive. For example, fivetran is a different user than FIVETRAN.
• Multitenant container databases: Usernames in multitenant container databases must begin with C## as they are considered common users.

Configure ARCHIVELOG mode

It is required to have your Oracle database in the ARCHIVELOG mode. This mode is typically the default for most production systems because it enables online backups and point-in-time recovery. Additionally, having the database in the ARCHIVELOG mode ensures that Fivetran can access all the required redo information.

TIP: We recommend that you keep at least 24 hours' worth of archive logs available.

The following section provides an overview of how to enable archive logging. We also recommend reviewing the Oracle documentation for more details.

1. Enable the ARCHIVELOG mode, if not enabled yet.

   IMPORTANT: If your database is not in the ARCHIVELOG mode, you must restart the database to place it in the ARCHIVELOG mode.

   • For single instance databases:

     NOTE: Enabling the ARCHIVELOG mode requires the Oracle instance to be briefly taken offline. To learn more, see Oracle's archived redo log file documentation.

     shutdown immediate;
     startup mount;
     alter database archivelog;
     alter database open;
     

   • For Oracle RAC:

     NOTE: Enabling the ARCHIVELOG mode requires the Oracle instance to be briefly taken offline. To learn more, see Oracle's archived redo log file documentation.

     i. Shut down all database instances.

     srvctl stop database -d <db_unique_name>
     

     ii. Start the database in mount mode.

     srvctl start database -d <db_unique_name> -o mount
     

     iii. Enable archive logging.

     sqlplus / as sysdba
     sql> alter database archivelog;
     sql> alter system set LOG_ARCHIVE_DEST_1='LOCATION=<SHARED_LOCATION>' scope=SPFILE;
     sql> EXIT;
     

     NOTE: <SHARED_LOCATION> if using Oracle RAC will be a specific ASM disk group, for example, +FRA.

     iv. Stop the database.

     srvctl stop database -d <db_unique_name>
     

     v. Restart all database instances.

     srvctl start database -d <db_unique_name>
     

     vi. Verify that archiving is enabled.

     sql> archive log list;
     

     IMPORTANT: The connector's database host must have access to the archived logs on all other nodes in the cluster.

2. Configure Oracle RMAN to retain backups and archive logs for at least 24 hours. We recommend that you retain data for seven days.

   IMPORTANT: To sync your data, Fivetran must have a minimum of 3 hours' worth of log data to analyze. You cannot finish setting up your connector until 3 hours after you configure RMAN to retain archive logs.

   RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
   

3. (Recommended) Set the DB_RECOVERY_FILE_DEST_SIZE parameter to a value that matches your available disk space, because expired and obsolete log and backup files can quickly fill your disk. For more information, see Oracle's DB_RECOVERY_FILE_DEST_SIZE documentation.

Enable supplemental logging

The HVA requires the Oracle supplemental logging feature to be enabled on tables it replicates. Without this feature, Oracle logs only the columns that are changed. The agent, however, needs additional data (for example, key columns) to generate a full update statement for the target destination.

Oracle supplemental logging can be set at both the database level and for specific tables.

To enable supplemental logging, use the following SQL commands:

1. Enable database-level minimal supplemental logging:

    ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
   

2. Enable additional table-level supplemental logging depending on the table type:

   • For a table with a primary key, enable primary key supplemental logging:

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

   • For a table without a primary key or unique index, or for a table with any type of compression enabled (regardless of whether they have a primary key and/or unique indexes), enable logging for all columns:

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

     NOTE: Enabling supplemental logging for all table columns ensures that any row change captures the values of all columns. This method allows the replication process to identify changes based on the entire row's data, which is especially beneficial for tables without a primary key.

     NOTE: For tables without a primary key, any update operation may incur additional MAR if it causes row movement. Oracle generates three log events for row movement — UPDATE (to an existing row), DELETE (of the row from its current partition), and INSERT (of the row into a new partition). Fivetran counts these as two MAR.

   • For a table without a primary key but with a unique index, enable conditional supplemental logging:

      ALTER TABLE "<schema>"."<table>" ADD SUPPLEMENTAL LOG GROUP "<group_name>" ("<column_name>", ...) ALWAYS;
     

     NOTE: This command creates a user-defined supplemental log group for specific column(s) within a table, offering a precise control over which column changes are logged. When using a unique index, ensure each table has its own unique log group.

SELECT supplemental_log_data_min, supplemental_log_data_pk, supplemental_log_data_all FROM v$database;

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

 ALTER DATABASE DROP SUPPLEMENTAL LOG DATA;

Configure Direct Capture

To enable Direct Capture, do the following:

1. Create a temporary table and grant read/write access to the Fivetran database user:

   NOTE: HVA uses the temporary table to make its queries more efficient during replication. Since this is a temporary table, there is no database logging on this table, and no rows remain at the end of the session. Storage for this table goes into the temporary tablespace.

   CREATE GLOBAL TEMPORARY TABLE HVR_SYS_TABLE (TABLE_NAME VARCHAR(128), TABLE_OWNER VARCHAR(128));
   GRANT SELECT, INSERT, UPDATE, DELETE ON HVR_SYS_TABLE TO <database_user>;
   

2. Grant the Fivetran database user permission to select any dictionary. We need to read the data dictionaries in Oracle's SYS schema to run Direct Capture. Follow the instructions below for your database type:

   For standalone databases:

   GRANT SELECT ANY DICTIONARY TO <database_user>;
   

   For multitenant container databasesBeta:

   GRANT SELECT ANY DICTIONARY TO <database_user> CONTAINER=ALL;
   

   IMPORTANT: In Oracle 12, you must grant the Fivetran database user explicit select privileges on the SYS.USER$ and sys.enc$ tables to replicate the following encrypted columns:

   • GRANT SELECT ON SYS.USER$ TO ;
   • GRANT SELECT ON SYS.ENC$ TO ;

   Alternatively, you may grant the read access of the following views individually.

   Click for detailed instructions

   NOTE: Use the GRANT SELECT <view_name> TO <username> format for standalone databases and GRANT SELECT <view_name> TO <username> CONTAINER=ALL for multitenant container databases.

    GRANT SELECT ON SYS.V_$ARCHIVE_DEST TO <username>;
    GRANT SELECT ON SYS.V_$ARCHIVED_LOG TO <username>;
    GRANT SELECT ON SYS.V_$DATABASE TO <username>;
    GRANT SELECT ON SYS.V_$DATABASE_INCARNATION TO <username>;
   
    /* The following grant (sys.v_$dnfs_files) is required for identifying the redo files located on DirectNFS */
    GRANT SELECT ON SYS.V_$DNFS_FILES TO <username>;
   
    /* The following grant (sys.v_$encryption_wallet) is required for decryption */
    GRANT SELECT ON SYS.V_$ENCRYPTION_WALLET TO <username>;
   
    GRANT SELECT ON SYS.V_$LOG TO <username>;
    GRANT SELECT ON SYS.V_$LOGFILE TO <username>;
   
    GRANT SELECT ON SYS.V_$NLS_PARAMETERS TO <username>;
    GRANT SELECT ON SYS.V_$PARAMETER TO <username>;
    GRANT SELECT ON SYS.V_$PDBS TO <username>;
   
    /* The following grant (sys.v_$system_parameter) is required for reading the value of 'filesystemio_options' parameter which in turn is used for reading the redo logs */
    GRANT SELECT ON SYS.V_$SYSTEM_PARAMETER TO <username>;
   
    GRANT SELECT ON SYS.ALL_CONS_COLUMNS TO <username>;
    GRANT SELECT ON SYS.ALL_CONSTRAINTS TO <username>;
    GRANT SELECT ON SYS.ALL_IND_COLUMNS TO <username>;
    GRANT SELECT ON SYS.ALL_INDEXES TO <username>;
    GRANT SELECT ON SYS.ALL_LOBS TO <username>;
    GRANT SELECT ON SYS.ALL_LOG_GROUPS TO <username>;
    GRANT SELECT ON SYS.ALL_OBJECTS TO <username>;
    GRANT SELECT ON SYS.ALL_TAB_COLS TO <username>;
    GRANT SELECT ON SYS.ALL_TABLES TO <username>;
    GRANT SELECT ON SYS.ALL_ENCRYPTED_COLUMNS TO <username>;
    GRANT SELECT ON SYS.DBA_TABLESPACES TO <username>;
    GRANT SELECT ON SYS.OBJ$ TO <username>;
   
    /* The following grant (sys.ecol$) is required for Oracle Database 11.2 and above since default values for added columns are stored differently. */
    GRANT SELECT ON SYS.ECOL$ TO <username>;
   
    GRANT SELECT ON SYS.USER$ TO <username>;
    GRANT SELECT ON SYS.COL$ TO <username>;
    GRANT SELECT ON SYS.ENC$ TO <username>;
    GRANT SELECT ON SYS.INDPART$ TO <username>;
    GRANT SELECT ON SYS.TABPART$ TO <username>;
    GRANT SELECT ON SYS.TABSUBPART$ TO <username>;
   
    /* The following three grants are required for the initial sync */
    GRANT SELECT ON SYS.V_$LOCKED_OBJECT TO <username>;
    GRANT SELECT ON SYS.V_$TRANSACTION TO <username>;
    GRANT SELECT ON SYS.DBA_OBJECTS TO <username>;
   

3. (Optional) Grant permissions to additional system tables to Fivetran database user. We recommend that you grant these permissions to optimize the connector's performance and reliability.

   For standalone databases:

   GRANT SELECT ON DBA_FREE_SPACE TO <database_user>;
   GRANT SELECT ON SYS.V_$TEMPFILE TO <database_user>;
   GRANT SELECT ON SYS.V_$DATAFILE TO <database_user>;
   

   For multitenant container databasesBeta:

   Execute the following command before granting access.

   ALTER SESSION SET CONTAINER=CDB$ROOT;
   

   GRANT SELECT ON DBA_FREE_SPACE TO <database_user>;
   GRANT SELECT ON SYS.V_$LOG TO <database_user>;
   GRANT SELECT ON SYS.V_$TEMPFILE TO <database_user>;
   GRANT SELECT ON SYS.V_$DATAFILE TO <database_user>;
   

4. (Optional) If you are implementing Direct Capture with ASM, do the following to finish your configuration:

   i. Create an ASM user with SYSASM privilege. Connect to the ASM instance using the SYS account with SYSASM role.

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

   IMPORTANT: If the ASM is only reachable through a TNS connection, you must specify the connection string in the ASM TNS property.

   ii. Allow the following grants to the Fivetran database user for ASM access:

   GRANT SELECT ON SYS.V_$ASM_DISKGROUP_STAT TO <username>;
   GRANT SELECT ON SYS.V_$ASM_CLIENT TO <username>;
   

Configure Oracle ASM (optional)

If you are using Oracle RAC configuration, we recommend that you configure HVA to run as a cluster resource.

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)
      )
   )

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)
      )
   )

Finish Fivetran configuration

This section outlines the steps to configure the HVA connector using the connector setup form within the Fivetran dashboard.

Configure connector in Fivetran dashboard

1. Enter a Destination schema prefix of your choice. This prefix applies to each replicated schema and cannot be changed once your connector is created.

2. In the Host field, enter the following information:

   • If you are using a single instance database, specify the hostname or IP address of your database. Set the value to localhost if the HVA and the database are on the same server.
   • If you are using Oracle RAC, specify an Application Virtual IP (VIP) address associated with the HVA.

     NOTE: The VIP address must be part of the cluster configuration and will move between nodes in case of node failure or restarts. This provides you with the option to run the agent on a specific node in the cluster. For this approach, we recommend using shared storage for the HVA.

   • If you are using Active Data Guard, enter the IP address where your standby database is running.

3. Enter the Port number your database server listens on for incoming connections. The default port number is 1521.

4. Enter the Fivetran-specific User you created.

   TIP: In Oracle, usernames are case-sensitive. Make sure to enter the exact username.

5. Enter the Password for the Fivetran-specific User.

6. Enter your database's SID or Service Name.

   • If you are using Oracle RAC, enter a Service Name. You can create the Service name using the Oracle srvctl command on RAC, for example, srvctl add service -db DEV -service FSRVC -preferred DEV1. For more details on using the srvctl command and services, refer to Oracle Documentation.

7. (Multitenant container databases only) Enter your database's PDB Name.

   • If you are using Oracle RAC, you can specify the Service Name that points to your pluggable database.

8. Enter the database's TNS or SID for the agent to use.

   NOTE: TNS is required for pluggable databases and RAC. TNS should be in the form of <hostname>:<port>/<Service> or <SID>.

9. Enter the name of the SAP Schema. SAP tables reside under this Oracle schema, for example, SAPSR3.

   NOTE: You cannot modify this field once it is saved.

10. Select your chosen Connection Method:

    • If you selected Connect via an SSH tunnel (this option is applicable for both standard SSH connections and reverse SSH connections), copy or make a note of the Public Key and add it to the authorized_keys file while configuring the SSH tunnel, and provide the following information:

      • SSH Host: Enter the hostname or IP address of your SSH server. Do not use a load balancer's IP address/hostname.
      • SSH Port: Enter the port number of your SSH server. The default port number is 22.
      • SSH User: Enter the username for SSH access.

    • If you selected Connect via proxy agent, choose the necessary proxy agent from the Proxy agents drop-down list (if available) or configure a new proxy agent.

11. (TDE-encrypted database only) If you want to use TDE encryption, set the Use TDE Encryption toggle to ON.

12. (Optional) Enter TDE Wallet Password if your database is configured with a Password-Based keystore. Leave the field blank if your database is configured with Auto-Login keystore.

13. (Optional) If the database is using Oracle RAC, set the Using Oracle RAC? toggle to ON and provide the following information:

    • ASM User: Enter the username for accessing the Oracle ASM.
    • ASM Password: Enter the password associated with the ASM user account.
    • (optional) ASM Oracle Home: Specify the directory path where the Oracle ASM software is installed on your system. This is only required if the ASM instance is not using the default installation path.
    • (optional) ASM TNS: Enter the Transparent Network Substrate (TNS) entry that corresponds to your ASM configuration. This should be used if you need to specify network details for connecting to the ASM instance.

14. (Optional) If the database is using ASM, set the Using ASM? toggle to ON and provide the following information:

    • ASM User: Enter the username for accessing the Oracle ASM.
    • ASM Password: Enter the password associated with the ASM user account.
    • (optional) ASM Oracle Home: Specify the directory path where the Oracle ASM software is installed on your system. This is only required if the ASM instance is not using the default installation path.
    • (optional) ASM TNS: Enter the Transparent Network Substrate (TNS) entry that corresponds to your ASM configuration. This should be used if you need to specify network details for connecting to the ASM instance.

15. In the Agent Host field, enter the HVA's hostname or IP address depending on the connection method you have chosen and your database configuration.

    • Connection method:
      • Direct: Enter the database hostname or IP address.
      • SSH: Enter the hostname or private IP address within your internal network, accessible by Fivetran through the SSH tunnel. For reverse SSH, set the value to localhost.
      • Private networking: Enter the hostname or private IP address within your VPC, accessible by Fivetran through a private endpoint.
      • Proxy Agent: Enter the hostname or private IP address within your internal network, accessible through the Proxy Agent. Use localhost if the Proxy Agent and HVA are installed on the same host.
    • Oracle RAC:
      • For Oracle RAC where the High-Volume Agent is configured on a node, the HVA's IP address is the Virtual IP (VIP) of the RAC node where the agent is running.
      • For Oracle RAC where the High-Volume Agent is configured as a cluster resource on a shared storage system, the HVA's IP address is the Virtual IP (VIP) created and dedicated to the agent.

16. In the Agent Port field, enter the HVA's port number. The default port number is 4343. For reverse SSH, use the value of <SSH_HIGH_PORT> (Linux) or Source port (Windows).

17. In the Agent User ID field, enter the name of the HVA user you created.

18. In the Agent User Password, enter the password of the HVA user you created.

19. In the Agent Public Cert, enter the HVA's Server Public Certificate you obtained.

20. In the Oracle Home field, enter the directory path where your Oracle database is installed.

21. Safelist the specified Fivetran's IPs for your selected cloud service provider and region in your firewall or security group.

22. Click Save & Test. Fivetran tests and validates our connection to your Oracle database. Upon successful completion of the setup tests, you can sync your data using Fivetran.

Setup tests

Fivetran performs the following tests to ensure that we can connect to your generic Oracle database and that it is properly configured:

• The Connecting to SSH Tunnel Test validates the SSH tunnel details you provided in the setup form. It then checks that we can connect to your database using the SSH tunnel. (We skip this test if you aren't connecting using an SSH tunnel.)
• The Connecting to Host Test validates the database credentials you provided in the setup form. It then verifies that the database host is not private and checks that we can connect to the host.
• The Validating Certificate Test generates a pop-up window where you must choose which certificate you want Fivetran to use. It then validates that certificate and checks that we can connect to your database using TLS. (We skip this test if you selected an indirect connection method and then disabled the Require TLS through Tunnel toggle.)
• The Validating Database Version Test checks your database version. The test passes if your database version is 12.2 or above or if your database version is 12.1 or below, and you are connecting using an SSH tunnel.
• The Validating Access to PDB Test checks that we have access to your pluggable database. We skip this test if your database is not a multitenant container database.
• The Validating System View Permission Test checks that we have permission to access the DBA_EXTENTS, DBA_TABLESPACES, and DBA_SEGMENTS system views.
• The Validating Archive Log Access Test checks that we can access your archive log.
• The Validating Archive Log Retention Period Test verifies that your archive log is set to retain at least 24 hours' worth of changes.
• The Access to Database-Level Supplemental Logging Test verifies that supplemental logging is enabled on your database. If supplemental logging is not enabled, the test passes but generates a warning message in your dashboard.
• The Validating Permissions to Run Direct Capture Test checks that we have permission to either all system views or selective system views required to run Direct Capture.
• The Validating Agent Setup Test checks that we can connect to the high-volume agent and whether it operates correctly.
• The Oracle Log Accessibility Test checks that the high-volume agent can access the database redo log and archived log files.
• The Validating Speed Setup Test checks how quickly Fivetran can fetch data from your source database. The test will show a warning if the speed is less than 5 MBps.

NOTE: The tests may take a few minutes to finish running.

Related articles

description Connector Overview

account_tree Schema Information

assignment Release Notes

settings API Connector Configuration

home Documentation Home