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.
CD
http://docs.oracle.com/cd/B19306_01/server.102/b14215/ldr_concepts.htm
C D
A is incorrect, external tables are better for transforms than SQL Loader
http://docs.oracle.com/cd/B28359_01/server.111/b28319/ldr_concepts.htm
so CD as others have said