# Import Oracle query results through a file

Coordinator DB does not query Oracle through an ODBC table function. Use an Oracle client or export tool to produce a file, then import it through Coordinator DB's native or HTTP interface. The source tool owns its driver, connection settings and credentials.

## Review the exported values

Select explicit columns and a known source boundary. Establish how the export encodes exact numeric scale, date and timestamp values, empty strings, nulls and large text or binary fields. CSV quoting must match the destination input format; a database-specific display format is not necessarily an interchange format.

Create a destination table with intended native declarations and load a representative sample. Use `csv_with_names` when the file includes a header, or convert the export to a supported row-oriented JSON format if that makes null and nested values clearer.

## Verify the result

Compare the same source range's row count and representative values after import. Include values with delimiters, quotes, Unicode and boundary numbers. Preserve the source export and its identifier long enough to reconcile an interrupted transfer.

For repeated import jobs, record completed batches outside the SQL request and check the destination before replaying a batch with an unknown outcome.

See [CSV exchange](https://coordinatordb.com/docs/guides/clickhouse/data-formats/csv-tsv), [data types](https://coordinatordb.com/docs/reference/data-types) and [batch inserts](https://coordinatordb.com/docs/concepts/features/operations/insert/bulkinserts).