Re: Drawbacks for direct path

From: Mark Bole <makbo_at_pacbell.net>
Date: Mon, 13 Dec 2004 22:21:01 GMT
Message-ID: <hBovd.33593$zx1.29168@newssvr13.news.prodigy.com>

Sybrand Bakker wrote:

> On Mon, 13 Dec 2004 21:34:07 +0100, "zeb" <spam_at_nowhere.com> wrote:
> 
> 

>>Hi,
>>
>>It seems direct path for export and SQL Loader is always
>>quicker than conventional path ...
>>
>>What are the drawbacks for direct path ?
>>Why not to use always direct path ?
>>When it is better to use diret path and
>>when it is better to use conventional path ?
>>
>>Thanks for your lights ...
>>
>>Oracle 8i, 9i
>>HP-UX 11.0 AIX 5L
>>

> 
> direct path means 
> - data is inserted after the high water mark of a table
> - constraints are not checked and triggers do not fire
> - indexes become invalid as a result of the operation and you'll need
> to rebuild them.
> 
> Obviously you could look this up in the documentation.
> 
> 
> 
> --
> Sybrand Bakker, Senior Oracle DBA

Just to clarify, there are two different scenarios - import of direct path export, and direct path SQL Loader.

An import of a direct path export is not special and does not suffer from any of the limitations that are listed above for SQL Loader. Other than matching the character set of database and exp/imp sessions, a direct path export simply speeds up your export and does nothing for your import.

-Mark Bole Received on Mon Dec 13 2004 - 16:21:01 CST