Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Drawbacks for direct path

Re: Drawbacks for direct path

From: Sybrand Bakker <gooiditweg_at_sybrandb.verwijderdit.demon.nl>
Date: Mon, 13 Dec 2004 21:42:07 +0100
Message-ID: <6hvrr0tk6jbrffvdk903sinlg80cip8sgo@4ax.com>


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
Received on Mon Dec 13 2004 - 14:42:07 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US