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.
Answer C and D is correct
http://docs.oracle.com/cd/E16655_01/server.121/e17639/ldr_concepts.htm#SUTIL978
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 data file. You can use SQL*Loader to do the following:
Load data across a network if your data files are on a different system than the database.
Load data from multiple data files during the same load session.
Load data into multiple tables during the same load session.
Specify the character set of the data.
Selectively load data (you can load records based on the records’ values).
Manipulate the data before loading it, using SQL functions.
Generate unique sequential key values in specified columns.
Use the operating system’s file system to access the data files.
Load data from disk, tape, or named pipe.
Generate sophisticated error reports, which greatly aid troubleshooting.
Load arbitrarily complex object-relational data.
Use secondary data files for loading LOBs and collections.
A and D.
Why C is incorrect. One can “Load data into multiple tables during the same load session” but not statement.
A is incorrect because you can transform data, but you can manipulate using sql functions
C – is correct because you define control file to load into more than one table and execute with one statement (also same session)
Transform exist in DataPump in SQLLoader exist Manipulate the data !!!???
C – TRUE
http://www.dba-oracle.com/t_sql_loader_multiple_tables_sqlldr.htm
LOAD DATA
INFILE /u01/app/oracle/load.dat
REPLACE
INTO TABLE emp
WHEN empno != ‘ ‘
( empno POSITION(1:4) INTEGER EXTERNAL,
ename POSITION(6:15) CHAR
)
INTO TABLE proj
WHEN projno != ‘ ‘
( projno POSITION(25:27) INTEGER EXTERNAL,
empno POSITION(1:4) INTEGER EXTERNAL
)
answer is C & D
A & B are recommended for external tables:
http://docs.oracle.com/cd/B28359_01/server.111/b28319/ldr_concepts.htm
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:
•You want to transform the data as it is being loaded into the database
•You want to use transparent parallel processing without having to split the external data first
However, in the following situations, use SQL*Loader for the best load performance:
•You want to load data remotely
•Transformations are not required on the data, and the data does not need to be loaded in parallel
SQL*Loader Features
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. You can use SQL*Loader to do the following:
•Load data across a network if your data files are on a different system than the database.
•Load data from multiple datafiles during the same load session.
•Load data into multiple tables during the same load session.
•Specify the character set of the data.
•Selectively load data (you can load records based on the records’ values).
•Manipulate the data before loading it, using SQL functions.
•Generate unique sequential key values in specified columns.
•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. See Chapter 11.
A typical SQL*Loader session takes as input a control file, which controls the behavior of SQL*Loader, and one or more datafiles. The output of SQL*Loader is an Oracle database (where the data is loaded), a log file, a bad file, and potentially, a discard file. An example of the flow of a SQL*Loader session is shown in Figure 6-1.
C and D
CD
CD
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.
Load data into multiple tables during the same load session. C is correct.
Specify the character set of the data.
Selectively load data (you can load records based on the records’ values).
Manipulate the data before loading it, using SQL functions. A is correct.
Generate unique sequential key values in specified columns. D is correct.
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.
A, C, D are all correct.
Agree with you it seem A, C and D the correct answer.
You´ll find the 3 answers in this link:
http://docs.oracle.com/cd/B28359_01/server.111/b28319/ldr_concepts.htm
C – could have been correct if it stated “same load session”. But choose said “same load statement”
What do you think?
C – could have been correct if it stated “same load session”. But choice said “same load statement”
What do you think?
CD
CD
Question C is: “..during the same load statement”, but sqlldr can load data into multiple tables “during the same load session”.
Therefore the answer is A, D
In the following situations, use external tables for the best load performance:
You want to transform the data as it is being loaded into the database
You want to use transparent parallel processing without having to split the external data first
However, in the following situations, use SQL*Loader for the best load performance:
You want to load data remotely
Transformations are not required on the data, and the data does not need to be loaded in parallel
C,D
C and D are correct and see below
D is obviously true as you can see from the list of concept document
C here is the proof
https://docs.oracle.com/cd/A97630_01/server.920/a96652/ch10.htm#1007219
cd
http://docs.oracle.com/cd/B28359_01/server.111/b28319/ldr_concepts.htm#i1004619
A – “Manipulate the data before loading it, using SQL functions.”
C – “Load data into multiple tables during the same load session.”
D – “Generate unique sequential key values in specified columns.”
From: https://docs.oracle.com/database/122/SUTIL/oracle-sql-loader-concepts.htm#SUTIL978
How we choose only “two scenarios”??