nerdexam
Oracle

1Z0-052 · Question #180

You are using flat files as the data source for one of your data warehousing applications. To optimize the application performance, you plan to move the data from the flat files to clustered tables…

The correct answer is C. Use the conventional path data load of the SQL*Loader utility. SQL*Loader conventional path is required to load flat file data into clustered tables because the direct path method explicitly does not support clusters.

Moving Data

Question

You are using flat files as the data source for one of your data warehousing applications. To optimize the application performance, you plan to move the data from the flat files to clustered tables in an Oracle database. While migrating the data, you want to have minimal impact on the database performance and optimize the data load operation. Which method would you use to load data into the Oracle database?

Options

  • AUse the external table population.
  • BUse the Oracle Data Pump export and import utility.
  • CUse the conventional path data load of the SQL*Loader utility.
  • DUse the INSERT INTO...SELECT command to load the data.

How the community answered

(56 responses)
  • A
    5% (3)
  • B
    2% (1)
  • C
    84% (47)
  • D
    9% (5)

Why each option

SQL*Loader conventional path is required to load flat file data into clustered tables because the direct path method explicitly does not support clusters.

AUse the external table population.

External table population creates a read-only Oracle view over a flat file and is not a direct loading mechanism into clustered tables; it requires additional INSERT steps and is not purpose-built for controlled bulk loads.

BUse the Oracle Data Pump export and import utility.

Oracle Data Pump operates on Oracle's proprietary binary format and is designed for database-to-database migration, not for ingesting raw flat file data sources.

CUse the conventional path data load of the SQL*Loader utility.Correct

SQL*Loader's conventional path load uses standard INSERT operations routed through the buffer cache and fully supports clustered tables, unlike the direct path method which bypasses the buffer cache and cannot write to clusters. Because the direct path restriction makes conventional path the only SQL*Loader option for clusters, it is the purpose-built, minimally invasive choice for migrating flat file data into this table structure.

DUse the INSERT INTO...SELECT command to load the data.

INSERT INTO...SELECT requires the source to already be an Oracle-accessible object such as a table or view and cannot natively read from flat files without first defining an external table over them.

Concept tested: SQL*Loader conventional path for clustered table loads

Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-sql-loader-conventional-and-direct-loads.html

Topics

#SQL*Loader conventional path#flat file migration#clustered table load#minimal database impact

Community Discussion

No community discussion yet for this question.

Full 1Z0-052 Practice