1Z0-052 · Question #200
Which statement is true about loading data using the conventional path of SQL*Loader?
The correct answer is C. No exclusive locks are acquired when the conventional path loads are performed. SQL*Loader conventional path uses the standard SQL engine with INSERT statements, so it acquires no exclusive table locks, checks all constraints, fires INSERT triggers, and generates redo.
Question
Which statement is true about loading data using the conventional path of SQL*Loader?
Options
- ARedo is not generated while performing conventional path loads
- BOnly PRIMARY KEY, UNIQUE KEY and NOT NULL constraints are checked
- CNo exclusive locks are acquired when the conventional path loads are performed
- DInstead of performing transactions, SQL*Loader directly writes data blocks to the data files
- EINSERT triggers are disabled before the conventional path load and reenabled at the end of the load
How the community answered
(44 responses)- A7% (3)
- B2% (1)
- C89% (39)
- E2% (1)
Why each option
SQL*Loader conventional path uses the standard SQL engine with INSERT statements, so it acquires no exclusive table locks, checks all constraints, fires INSERT triggers, and generates redo.
Redo IS generated during conventional path loads because they go through the standard SQL engine; it is the direct path load that can optionally bypass redo generation with the NOLOGGING option.
Conventional path loads enforce ALL active constraints on the table; it is the direct path load that checks only PRIMARY KEY, UNIQUE KEY, and NOT NULL constraints.
Conventional path loads operate through the Oracle SQL layer using standard INSERT statements, which means no exclusive locks are placed on the target table, allowing other sessions to perform concurrent DML against it during the load operation.
Writing data blocks directly to data files bypassing the buffer cache is the defining behavior of the direct path load, not the conventional path.
INSERT triggers fire normally during conventional path loads; the direct path load disables INSERT triggers before loading and re-enables them at the end.
Concept tested: SQL*Loader conventional path locking and constraint behavior
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-sql-loader-concepts.html
Topics
Community Discussion
No community discussion yet for this question.