You plan to bulk load data INSERT INTO . . . SELECT FROM statements.
Which two situations benefit from parallel INSERT operations on tables that have no materialized views defined on them?
A. Direct path insert of a million rows into a partitioned, index-organizedtable containing one millionrows anda conventional B*treesecondary index.
B. Direct path insert of a million rows into a partitioned, index-organized table containing 10 rows and a bitmapped secondary index.
C. Direct path insert of 10 rows into a partitioned, index-organized table containing one million rows and conventional B* tree secondary index.
D. Direct path insert of 10 rows into a partitioned, index-organized table containing10rowsand a bitmapped secondary index
E. Conventionalpath insert of a million rows into a nonpartitioned, heap-organized containing 10 rows and having a conventional B* tree index.
F. Conventional path insert of 10 rows into a nonpartitioned, heap-organized table one million rows and a bitmapped index.
Correct Answer: AB
Explanation/Reference:
Note:
*A materialized view is a database object that contains the results of a query.
*You can use the INSERT statement to insert data into a table, partition, or view in two ways: conventional INSERTand direct-path INSERT.
* With direct-path INSERT, the database appends the inserted data after existing data in the table.
Data is written directly into datafiles, bypassing the buffer cache. Free space in the existing data is not reused. This alternative enhances performance during insert operations and is similar to the functionality of the Oracle direct-path loader utility, SQL*Loader. When you insert into a table that has been created in parallel mode, direct-path INSERT is the default.
* Direct-path INSERT is not supported for an index-organized table (IOT) if it is not partitioned, if it has a mapping table, or if it is reference by a materialized view.
* When you issue a conventional INSERT statement, Oracle Database reuses free space in the table into which you are inserting and maintains referential integrity constraints
* Conventional INSERT always generates maximal redo and undo for changes to both data and metadata, regardless of the logging setting of the table and the archivelog and force logging settings of the database
|
Download Printable PDF. VALID exam to help you PASS.
|
 |
