Which statement is true about loading data using the conventional path of SQL*Loader?
A.
Redo is not generated while performing conventional path loads
B.
Only PRIMARY KEY, UNIQUE KEY and NOT NULL constraints are checked
C.
No exclusive locks are acquired when the conventional path loads are performed
D.
Instead of performing transactions, SQL*Loader directly writes data blocks to the data files
E.
INSERT triggers are disabled before the conventional path load and reenabled at the end of the
load
C is correct, as conventional path loads means normal INSERT statements, as as with any normal INSERT you can have concurrent transactions running against the table hence “No exclusive locks are acquired”
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. 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.
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.
Conventional path loads (the default) use the SQL command INSERT and a bind array buffer to load data into database tables. This method is used by all Oracle tools and applications.
When SQL*Loader performs a conventional path load, it competes equally with all other processes for buffer resources. This can slow the load significantly. Extra overhead is added as SQL commands are generated, passed to Oracle, and processed.
SQL*Loader – NO LOCK