2.6 Parallel Direct Path Load

Table of Contents Previous Next


2 EDB*Loader : 2.6 Parallel Direct Path Load

In addition, the APPEND clause must be specified in the control file used by each EDB*Loader session.
Note: In a parallel direct path load, each EDB*Loader session reserves a fixed number of blocks in the target table in a round-robin fashion. Some of the blocks in the last allocated chunk may not be used, and those blocks remain uninitialized. A subsequent use of the VACUUM command on the target table may show warnings regarding these uninitialized blocks such as the following:
Note: If you attempt a parallel direct path load on the sample emp table provided with Advanced Server, you must first remove the triggers and constraints referencing the emp table. In addition the primary key column, empno, was expanded from NUMBER(4) to NUMBER in this example to allow for the insertion of a larger number of rows.
The APPEND clause must be specified in the control file for a parallel direct path load.
The following shows the invocation of EDB*Loader in the first session. The DIRECT=TRUE and PARALLEL=TRUE parameters must be specified.
The following query shows that the index on the emp table has been marked as INVALID:
Note: user_indexes is the view of indexes compatible with Oracle databases owned by the current user.
Queries on the emp table will not utilize the index unless it is rebuilt using the REINDEX command as shown by the following:
A subsequent query on user_indexes shows that the index is now marked as VALID:

2 EDB*Loader : 2.6 Parallel Direct Path Load

Table of Contents Previous Next