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 and create 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, and drop 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, and delete 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, and drop 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 and drop 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 and alter any trigger privileges:
```
grant create, alter any trigger to username;
```