Indicates the boundary between two columns of data.

Comma
Tab
Colon
Semicolon
Non Printable. When you choose this option, the
Non-printable character
drop-down list appears. Select a non-printable character to use as the delimiter.
Other. Select this option and specify the character to use as the delimiter.
If you specify a comma, colon, or semicolon, the corresponding options are selected.
If the character specified here matches with any of the values in the
Non-printable character
drop-down list, the value appears in the
Non-printable character
drop-down list.

If you use an escape character or a quote character as the delimiter, or if you use the same character as consecutive delimiter and qualifier, you might receive unexpected results.

Character that defines the boundaries of text strings.

Character that immediately precedes a column delimiter character embedded in an unquoted string, or immediately precedes the quote character in a quoted string.

Row number from which

Data Profiling

starts to read when it imports the file. For example, if you enter

2

,

Data Profiling

skips the first row.

You must specify the schema of the source file. You can select one of the following options to specify a schema:

Character used to separate columns of data. You can configure parameters such as comma, tab, colon, semicolon, or others. To set a tab as a delimiter, you must type the tab character in any text editor. Then, copy and paste the tab character in the Delimiter field.If you specify a multibyte character as a delimiter in the source object, the mapping fails.

Character immediately preceding a column delimiter character embedded in an unquoted string, or immediately preceding the quote character in a quoted string.

Character that defines the boundaries of text strings.

UTF-8. Select for Unicode and non-Unicode data. Select the code page that the Secure Agent must use to read data.

Specify the line number that you want to use as the header when you read data from Amazon S3. You can also read data from a file that does not have a header. Default is 1.

Specify the line number from where you want the Secure Agent to read data. You must enter a value that is greater or equal to one. To read data from the header, the value of the Header Line Number and the First Data Row fields should be the same. Default is 2.

Upload a schema definition file. You cannot upload a schema file when you create a target at runtime.

Upload a schema definition file. You cannot upload a schema file when you create a target at runtime.

Specify the number of rows to read to find the best match to populate the metadata.

The default value is 2 MB.If the file size is more than 2 MB, you might encounter an error. Set the value to the file size that you want to read.

You must specify the schema of the source file. You can select one of the following options to specify a schema:

Character used to separate columns of data. You can configure parameters such as comma, tab, colon, semicolon, or others.

Character immediately preceding a column delimiter character embedded in an unquoted string, or immediately preceding the quote character in a quoted string.

Character that defines the boundaries of text strings.

Microsoft Azure Data Lake Storage Gen2 Connector supports only UTF-8. Ignore rest of the code pages.

Specify the line number that you want to use as the header when you read data from Microsoft Azure Data Lake Storage Gen2. You can also read a data from a file that does not have a header. To read data from a file with no header, specify the value of the

Header Line Number

field as 0.

Specify the line number from where you want the Secure Agent to read data. You must enter a value that is greater or equal to one. To read data from the header, the value of the

Header Line Number

and the

First Data Row

fields should be the same. Default is 2.

Upload a schema definition file. You cannot upload a schema file when you create a target at runtime.

Upload a schema definition file. You cannot upload a schema file when you create a target at runtime.

Specify the number of rows to read to find the best match to populate the metadata.

The default value is 2 MB.If the file size is more than 2 MB, you might encounter an error. Set the value to the file size that you want to read.

You must specify the schema of the source file. You can select one of the following options to specify a schema:

Character used to separate columns of data. You can configure parameters such as comma, tab, colon, semicolon, or others. To set a tab as a delimiter, you must type the tab character in any text editor. Then, copy and paste the tab character in the Delimiter field.

Character immediately preceding a column delimiter character embedded in an unquoted string, or immediately preceding the quote character in a quoted string.

Character that defines the boundaries of text strings.

Specify the qualifier behavior for the target object. You can select one of the following options:

Minimal. Default mode. Applies qualifier to data enclosed within a delimiter value or a special character.
All. Applies qualifier to all data.
Non_Numeric. Not applicable.
All_Non_Null. Not applicable.

Select the code page that the Secure Agent must use to read or write data.Google Cloud Storage V2 Connector supports the following code pages:

To read data from a file with no header, specify the value of the Header Line Number field as 0. To read data from a file with a header, set the value of the Header Line Number field to a value that is greater than or equal to one. Ensure that the value of the Header Line Number field is lesser than or equal to the value of the First Data Row field. This property is applicable during runtime and data preview to read a file. When you create a mapping in advanced mode, set the value of the header line number to 0, 1, or empty to run the mapping successfully.

To read data from the header, the value of the Header Line Number and the First Data Row fields should be the same. Default is 1.

Not applicable.

Upload a schema definition file. You cannot upload a schema file when you create a target at runtime.

Upload a schema definition file. You cannot upload a schema file when you create a target at runtime.

Specify the number of rows to read to find the best match to populate the metadata.

The default value is 2 MB.If the file size is more than 2 MB, you might encounter an error. Set the value to the file size that you want to read.

Not applicable.

You must specify the schema of the source file. You can select one of the following options to specify a schema:

Character used to separate columns of data. You can configure parameters such as comma, tab, colon, semicolon, or others.

Character immediately preceding a column delimiter character embedded in an unquoted string, or immediately preceding the quote character in a quoted string.

Character that defines the boundaries of text strings.

Oracle Cloud Object Storage Connector supports only UTF-8. Ignore rest of the code pages.

Specify the line number that you want to use as the header when you read data from Oracle Cloud Object Storage. You can also read a data from a file that does not have a header. To read data from a file with no header, specify the value of the

Header Line Number

field as 0.

Specify the line number from where you want the Secure Agent to read data. You must enter a value that is greater or equal to one. To read data from the header, the value of the

Header Line Number

and the

First Data Row

fields should be the same. Default is 2.