which two scenarios do you use SQL* Loader to load data?

In which two scenarios do you use SQL* Loader to load data?

In which two scenarios do you use SQL* Loader to load data?

A.
Transform the data while it is being loaded into the database.

B.
Use transparent parallel processing without having to split the external data first.

C.
Load data into multiple tables during the same load statement.

D.
Generate unique sequential key values in specified columns.

Explanation:
You can use SQL*Loader to do the following:
/ (A) Manipulate the data before loading it, using SQL functions.
/ (D) Generate unique sequential key values in specified columns.
etc:
/ Load data into multiple tables during the same load session.
/ Load data across a network. This means that you can run the SQL*Loader client on a different
system from the one that is running the SQL*Loader server.
/ Load data from multiple datafiles during the same load session.
/Specify the character set of the data.
/ Selectively load data (you can load records based on the records’ values).
/Use the operating system’s file system to access the datafiles.
/ Load data from disk, tape, or named pipe.
/ Generate sophisticated error reports, which greatly aid troubleshooting.
/ Load arbitrarily complex object-relational data.
/ Use secondary datafiles for loading LOBs and collections.
/ Use either conventional or direct path loading. While conventional path loading is very flexible,
direct path loading provides superior loading performance.
Note:
* SQL*Loader loads data from external files into tables of an Oracle database. It has a powerful
data parsing engine that puts little limitation on the format of the data in the datafile.

Show Hint

Leave a Reply 8

Your email address will not be published. Required fields are marked *

H*T*H

H*T*H

The given answer, AD is wrong. This is because there are actually 3 scenarios listed in which you could use SQL*Loader. A summary of SQL*Loader’s functionality is presented here: http://docs.oracle.com/database/121/SUTIL/ldr_concepts.htm#SUTIL978.

A is correct. Data can be transformed/manipulated using SQL functions before being loaded into a database table.
C is correct since it is possible to load data into multiple tables during the same load session.
D is also correct because SQL*Loader can generate unique sequential key values for specified columns. SQL*Loader supports the new IDENTITY column feature.

B is not correct because you would typically split a large data file into several smaller files then load them in parallel in order to perform “parallel processing”. That wouldn’t be transparent.

H*T*H

Reply

Kaustav

Kaustav

C, D.

Choosing External Tables Versus SQL*Loader
——————————————–
The record parsing of external tables and SQL*Loader is very similar, so normally there is not a major performance difference for the same record format. However, due to the different architecture of external tables and SQL*Loader, there are situations in which one method is more appropriate than the other.

In the following situations, use external tables for the best load performance:

1) You want to transform the data as it is being loaded into the database.
2) You want to use transparent parallel processing without having to split the external data first.

Reply

Sylvain

Sylvain

http://docs.oracle.com/cloud/latest/db112/SUTIL/ldr_concepts.htm#SUTIL3316

C is possible
Case Study 5: Loading Data into Multiple Tables – Loads data into multiple tables in one run.

B seems also possible

Parallel Direct Path

A parallel direct path load allows multiple direct path load sessions to concurrently load the same data segments (allows intrasegment parallelism). Parallel direct path is more restrictive than direct path.

I am confused…

Reply