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

Home -> Community -> Usenet -> c.d.o.misc -> Re: Export and files > 2Gigs

Re: Export and files > 2Gigs

From: MCR <mrush_at_hertz.com.nospam>
Date: 1997/07/07
Message-ID: <01bc8b06$34aaba80$163f04d8@mrush.hertz.com>#1/1

Carlos A. Gonzalez <carlos_a_gonzalez_at_us.dell.com> wrote in article <01bc8a13$dd111ff0$7916a68f_at_rasputin>...
> Gentlemen:
>
> Here is what's happening.
>
> I am in the process of movin a large database (20 Gigs) from one host to
> another.
>
> The export file I'll be creating is over two Gigs space.
>
> The Oracle Gurus at my site tell me about a unix file size limitation
 that
> can not be greater than 2 Gigs.
>
> I'm skeptical, specially since I been told a lot of misinformation from
 the
> same people before.
>
> I am running oracle ver 7.2.3 under unix Solaris ver 5.2 in Sun Sparc
> hardware
>
> Any help/comments/leads will be greatly appreciated
>
> Thanks
>
> Carlos
>
>

What you can do is to export to a pipe. This pipe is remote copied "rcp" to a pipe
on your new host. The pipe on the new host is then used as the input file for the import.

In this way you can export from one machine to another without having any large files.
As you can guess this creates just a little network traffic.

When I did this I exported to a pipe, which was compressed to another which was the one
copied to the remote host. This creates less network traffic. One the remote host you add the step of uncompressing the copied pipe to your import pipe.

If you want more details Email me.

Mark Rush
Oracle DBA
Hertz

mrush "at" hertz "dot" com Received on Mon Jul 07 1997 - 00:00:00 CDT

Original text of this message

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