Oracle as Target
Fivetran HVR supports integrating changes into Oracle database. This section describes the configuration requirements for integrating changes (using Integrate and Refresh) into Oracle location.
For the list of supported Oracle versions, into which HVR can integrate changes, see Integrate changes into location in Capabilities.
HVR uses the following interfaces to write data to Oracle during Refreshing Data or Integrate:
- Oracle native OCI interface, used for continuous Continuous Integrate and Row-wise Refresh.
- Oracle OCI direct-path-load interface, used for Burst Integrate and Bulk Refresh.
Grants for Integrate and Refresh
This section lists the grants required for integrating changes into Oracle.
The HVR database User must be allocated a quota on the default tablespace. For this, the HVR database user must be granted the following privilege:
alter user username quota quotalimit on tablespacename;
Alternatively, unlimited tablespace quota may be granted:
grant unlimited tablespace to username;
To Integrate changes or to Refresh data into Oracle database, the HVR database User must be granted
create session
andcreate table
privileges:grant create session to username; grant create table to username;
To create target tables using Refresh, the HVR database User must be granted
create any index
,drop any index
,create any table
,alter any table
, anddrop any table
privileges:grant create, drop any index to username; grant create, alter, drop any table to username;
To change tables which are owned by other schemas (using action TableProperties with parameter Schema), the HVR database User must be granted the following
select any table
,insert any table
,update any table
, anddelete any table
privileges:grant select, insert, update, delete any table to username;
To perform Bulk Refresh of tables which are owned by other schemas, the HVR database User must be granted the following
alter any table
,lock any table
, anddrop any table
privileges :grant alter, lock any table to username; /* Following grant is required for truncate statements */ grant drop any table to username;
To use action DbSequence with parameter Schema, the HVR database User must be granted
create any sequence
anddrop any sequence
privileges:grant create, drop any sequence to username;
To disable/re-enable triggers in target schema, the HVR database User must be granted the
create any trigger
andalter any trigger
privileges:grant create, alter any trigger to username;
Intermediate Directory
This option in the HVR UI allows you to specify a directory path for storing intermediate (temporary) files generated during Compare. These files are created during both "direct file compare" and "online compare" operations.
Using an intermediate directory can enhance performance by ensuring that temporary files are stored in a location optimized for the system's data processing needs.
This setting is particularly relevant for target file locations, as it determines where the intermediate files are placed during the Compare operation. If this option is not enabled, the intermediate files are stored by default in the integratedir/_hvr_intermediate directory, where integratedir is the replication DIRECTORY (File_Path) defined for the target file location.
This option is equivalent to the location property Intermediate_Directory.
Intermediate Directory is Local
This option in HVR UI specifies that the Intermediate Directory will be created on the local drive of the file location's server.
This setting is crucial for optimizing performance, as it reduces network latency and avoids potential permission issues associated with remote storage. By storing intermediate files locally, HVR can process data more efficiently, taking advantage of the speed and reliability of local storage.
This option is particularly beneficial when the HVR Agent has access to ample local storage, enabling it to handle large data volumes without relying on networked storage solutions.
This option is equivalent to the location property Intermediate_Directory_Is_Local.