Use an "exp" and "imp" job joined together with a
UNIX "fifo" or "pipe"? That way, both the "exp" and "imp"
processes can run as long as necessary without using any disk space for
a dump file at all? Of course, I guess you'll have to import it into
the same table name but different schema, which I guess is what you
were planning anyway? For example... $ mknod /tmp/pipe.pipe p (or "mkpipe /tmp/pipe.pipe" on certain *NIXs)Then, just let 'er rip... Niall Litchfield wrote: -- //www.freelists.org/webpage/oracle-l |