Oracle DB
Learn the required and optional properties of creating an Oracle DB Connection, Credential, Read Connector, and Write Connector.
Prerequisites
- Access Credentials
- Database name, Host, and Port
- Oracle SID
Connection Properties
The following table describes the fields available when creating a new Oracle DB Connection. Create a connection using the information below and these step-by-step instructions.
Field | Required | Description |
---|---|---|
Access Type | Required | This connection type is Read-Only, Write-Only, or Read-Write. |
Connection Name | Required | Input your desired name. |
Host | Required | IP or the hostname of the OracleDB Server. |
Port | Optional | Host server port number. |
Oracle SID | Required | Oracle site identifier. |
Requires Credentials | Optional | Check this box to create a new credential or select an existing credential. |
Credential Properties
The following table describes the fields available when creating a new Oracle DB credential.
Field | Required | Description |
---|---|---|
Credential Name | Required | The name to identify this credential with. This credential will be available as a selection for future use. |
Credential Type | Required | This field will automatically populate with Oracle . |
User | Required | OracleDB username to connect with. |
Password | Optional | OracleDB password to connect with. |
Read Connector Properties
The following table describes the fields available when creating a new Oracle Read Connector. Create a new Read Connector using the information below and these step-by-step instructions.
Field | Required | Description |
---|---|---|
Name | Required | Provide a name for your connector. We recommend using lowercase with underscores in place of spaces. |
Description | Optional | Describes the connector. We recommend providing a description if you are ingesting information from the same source multiple times for different reasons. |
Table Name | Required | Name of the table to ingest. The table name is case-sensitive. Enclose it in double quotes if the table name is not all upper case. |
Schema Name | Optional | The name of the Snowflake Schema. |
Replication Strategy | Optional | Full Resync, Filter by column range, or Incremental column name. See Database Reading Strategies for more information. |
Data Version | Optional | A change to Data Version results in no longer using data previously ingested by this Connector, and a complete ingest of new data. |
Write Connector Properties
The following table describes the fields available when creating a new Oracle DB Write Connector. Create a new Write Connector using the information below and these step-by-step instructions.
Field | Required | Description |
---|---|---|
Name | Required | Provide a name for your connector. We recommend using lowercase with underscores in place of spaces. |
Description | Optional | Describes the connector. We recommend providing a description if you are ingesting information from the same source multiple times for different reasons. |
Upstream | Required | The name of the previous connector to pull data from. |
Table Name | Required | The name of the table to write to in Oracle |
Write Strategy | Required | The strategy to copy data into AWS. The Full Load strategy will replace the entire tables contents each time that the upstream transform has changed. If the upstream data set contains multiple Ascend partitions and not all partitions are expected to change on each update, then the Incremental By Partition strategy allows for Ascend to only update/insert/delete the partitions of the Amazon Redshift table that have changed in Ascend. |
A SQL Statement for Ascend to Execute Before Writing | Optional | Execute a pre-processing script before writing to final table. |
A SQL Statement for Ascend to Execute After Writing | Optional | Execute a pre-processing script after writing to final table. |
Schema Name | Optional | The name of the schema. |
On Schema Mismatch | Optional | Select how you want Ascend to handle writing data if the schema indicated above does not match the schema of the table in Snowflake. Options are as follows: - Skip schema check - Stop and display error - Recreate table - Alter table |
Data Version | Optional | A change to Data Version results in no longer using data previously ingested by this Connector, and a complete ingest of new data. |
Updated over 1 year ago