The Airbyte Oracle destination allows you to sync data to Oracle.
Each stream will be output into its own table in Oracle. Each table will contain 3 columns:
_AIRBYTE_AB_ID: a uuid assigned by Airbyte to each event that is processed. The column type in Oracle is
_AIRBYTE_EMITTED_AT: a timestamp representing when the event was pulled from the data source. The column type in Oracle is
TIMESTAMP WITH TIME ZONE.
_AIRBYTE_DATA: a json blob representing with the event data. The column type in Oracles is
Full Refresh Sync
Incremental - Append Sync
Incremental - Deduped History
Only for raw tables, doesn't support for nested json yet
To use the Oracle destination, you'll need:
An Oracle server version 18 or above
It's possible to use Oracle 12+ but you need to configure the table name length to 120 chars.
Make sure your Oracle database can be accessed by Airbyte. If your database is within a VPC, you may need to allow access from the IP you're using to expose Airbyte.
As Airbyte namespaces allows us to store data into different schemas, we have different scenarios and list of required permissions:
Same user as login
Create, drop and write table, create session
Any existing user
Create, drop and write ANY table, create session
Grants can be provided on a system level by DBA or by target user directly
Not existing user
Create, drop and write ANY table, create user, create session
Grants should be provided on a system level by DBA
We highly recommend creating an Airbyte-specific user for this purpose.
You should now have all the requirements needed to configure Oracle as a destination in the UI. You'll need the following information to configure the Oracle destination:
Use default column name for raw tables
Remove support for Oracle 11g to allow normalization
🐛 Destination Oracle: Fix destination check for users without dba role
Partial Success in BufferedStreamConsumer