Exadata connection reference
Learn about the fields used to create an Exadata connection with ThoughtSpot DataFlow. Here is a list of the fields for an Exadata connection in ThoughtSpot DataFlow. You need specific information to establish a seamless and secure connection.
Connection properties
- Connection name
-
Name your connection. Mandatory field.
- Example:
-
ExadataConnection
- Connection type
-
Choose the Exadata connection type. Mandatory field.
- Example:
-
Exadata
- Host
-
Specify the hostname or the IP address of the Exadata system. Mandatory field.
- Example:
-
www.example.com
- Port
-
Specify the port associated to the Exadata system. Mandatory field.
- Example:
-
1234
- User
-
Specify the user id that will be used to connect to the Exadata system. This user should have necessary privileges to access the data in the databases. Mandatory field.
- Example:
-
userdi
- Password
-
Specify the password for the User. Mandatory field.
- Example:
-
pswrd234%!
- Service name
-
Service name is the TNS alias that you give when you remotely connect to your database and this Service name is recorded in Tnsnames.ora file on your clients and it can be the same as SID and you can also give it any other name you want. Mandatory field.
- Example:
-
idxdb03
- Version
-
Specify the Exadata version being connected to. Optional field.
- Example:
-
11.x
- Other notes:
-
Advanced configuration
- JDBC options
-
Specify the options associated with the JDBC URL. Optional field.
- Example:
-
jdbc:sqlserver://[serverName[\instanceName][:portNumber]] - Other notes:
-
Advanced configuration
Sync properties
- Data extraction mode
-
Specify the extraction type. Optional field.
- Example:
-
JDBC
- Valid Values:
-
JDBC, OCI
- Default:
-
JDBC
- Column delimiter
-
Specify the column delimiter character. Mandatory field.
- Example:
-
1
- Valid Values:
-
Any printable ASCII character or decimal value for ASCII character
- Default:
-
1
- Null Value
-
Specifies the string literal that should indicate the null value in the extracted data. During the data load the column value matching this string will be loaded as null in the target. Optional field.
- Example:
-
NULL
- Valid Values:
-
Any string literal
- Default:
-
NULL
- Other notes:
-
Specific only to OCI data extraction mode
- Escape character
-
Specify this if the text qualifier is mentioned. This should be the character which escapes the text qualifier character in the source data. Optional field.
- Example:
-
"
- Valid Values:
-
Any ASCII character
- Default:
-
"
- Enclosing character
-
Specify if the text columns in the source data needs to be enclosed in quotes. Optional field.
- Example:
-
DOUBLE
- Valid Values:
-
SINGLE, DOUBLE
- Default:
-
DOUBLE
- Other notes:
-
This is required if the text data has newline character or delimiter character.
- Max ignored rows
-
Abort the transaction after encountering 'n' ignored rows. Optional field.
- Example:
-
0 - Valid Values:
-
Any numeric value
- Default:
-
0
- Fetch size
-
Specify the number of rows to be fetched at a time and processed in memory.If the value specified is zero then, all rows are extracted at once. Optional field.
- Example:
-
1000
- Valid Values:
-
Any numeric value
- Default:
-
1000
- TS load options
-
Specifies the parameters passed with the
tsloadcommand, in addition to the commands already included by the application. The format for these parameters is:--<param_1_name> <optional_param_1_value>--<param_2_name> <optional_param_2_value>Optional field.
- Example:
-
--max_ignored_rows 0
- Valid Values:
-
--user "dbuser" --password "$DIWD" --target_database "ditest" --target_schema "falcon_schema"
- Default:
-
--max_ignored_rows 0
- Reference:
Related information
