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: Impact on exp/imp in production system.-Direct=y

Re: Impact on exp/imp in production system.-Direct=y

From: duraisingh <duraisingh_at_yahoo.com>
Date: Mon, 18 Oct 1999 15:51:24 -0400
Message-ID: <380B7A3C.F1A57E9E@yahoo.com>


Thanks Bakker.
Your reply has really enlightened me a lot. John

Sybrand Bakker wrote:

> On Mon, 18 Oct 1999 13:40:31 -0400, duraisingh <duraisingh_at_yahoo.com>
> wrote:
>
> >Hellow Gurus.
> >Can any one can tell me , what is the difference between direct &
> >conventional path on the exports.I know it ll fasten exp/imp timings.
> >
> >Since I want to reorg the fragmented tables thru direct =y option .
> >Some of my friends told me that it's not the secured & proven method on
> >any production system.
> >Is it true & why???
> >I think some of you guys might have gone thru this question.
> >
> >John Durai
> >Prod.Supp Dba -Tampa
> >
> Normal export issues normal selects. Direct export bypasses the select
> layer and reads directly from tables. I would think this precludes the
> use of consistent=Y, which makes sure your export is consistent, ie
> the export process will not see any transactions. You will usually not
> manage to do so, because your rollback segments are too small. Also
> direct export is always done in the native characterset of the
> database, no conversion will be allowed.
> To minimize the consistency issue, you could as well kick everyone
> out, and issue an alter system set restricted_session=true, which
> makes sure only DBAs can connect.
>
> Hth,
>
> Sybrand Bakker, Oracle DBA
Received on Mon Oct 18 1999 - 14:51:24 CDT

Original text of this message

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