Re: Schema to Text File

"Noel" <tbal_at_go2.pl> wrote in message news:3ba21667$1_at_news.vogel.pl...
>
> U¿ytkownik "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> napisa³ w
wiadomo¶ci
> news:tq420vtk5dp8e0_at_news.demon.nl...
>
> > export, rows=n, will dump only the table and index definitions and can
be
> > used anywhere.
>
> I used to move schemas that way, but there is one thing that worry me.
> If you have very large table with tons of rows, it will be moved to new
> schema and will take same amout of tablespace :(
> Is there any way to get rid of it?
>
>
> ---------------
> Noel
>
>
>

First of all: you should always run with compress=n This will make sure you the initial extent has the original size. With compress=y (the default!!!) you will set the initial extent in your export to the total number of bytes in the segment in your source database. I think this will address the issue almost completely. Secondly, you can of course dump the export file to plain ascii with imp show=y full=y log=<any file>
<Any file> will contain create commands in ascii. Just edit them and run this file as a script and you'r there.

Hth,

Sybrand Bakker, Senior Oracle DBA Received on Fri Sep 14 2001 - 19:19:29 CEST