Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: export tuning
Don't use direct path export if you suspect your tables have chained/migrated rows; it is very likely that your export file would be corrupt and it wouldn't be possible to import it.
This (mis)behaviour of direct path export on particular version of Oracle on particular platform is easiliy reproducible.
Regards,
Goran
"Tanel Poder" <change_to_my_first_name_at_integrid.info> wrote in message
news:3fce0f7e$1_1_at_news.estpak.ee...
> Export to different disk you're reading from.
>
> Use direct=y
> If not using direct mode, set db_file_multiblock_read_count high (for exp
> session using logon trigger).
>
> If exporting over network, set your SDU settings to the max allowable
> (depending on MTU).
>
> Tanel.
>
> "NetComrade" <andreyNSPAM_at_bookexchange.net> wrote in message
> news:3fce0253.3460644453_at_nyc.news.speakeasy.net...
> > besides things already suggested..
> >
> > consider partitioning the table, and exporting monthly/weekly data
> > (however you please to partition).
> >
> > If IO is a bottleneck, you can try gzipping on the fly (through a
> > pipe).
> >
> >
> >
> > On Wed, 3 Dec 2003 09:04:49 -0000, "Tom"
> > <tomNOSPAM_at_teameazyriders.com> wrote:
> >
> > >Hi,
> > >
> > >I have a daily export running and although one of the tables has around
6
> million rows in it the data is mainly just clickstream
> > >style data, so navigation path through site type data etc.
> > >
> > >As a result the export takes around 7 hours which seems way too long
and
> as this table will only grow what tuning parameters are
> > >available to me to try to speed up this export?
> > >
> > >This is on 8.1.7
> > >
> > >thanks
> > >
> > >Tom
Received on Thu Dec 04 2003 - 04:43:41 CST