Re: UNIX 2 gig size limit.

Yes, when importing a large file Oracle will need to need to read from a pipe. What is going on is that Oracle's import and export programs can't read or a write beyond the 2 Gigabyte point in a file. Using a named pipe gets around Oracle's limitation since the pipe is only a few hundred blocks long but actually passes gigabytes of information. When the data is written out, Oracle can write to the pipe and thus output more than 2 gigabytes. Generally people compress the output of the named pipe onto a tape device.

When you take the data from the backup file, you must uncompress the file if it has been compressed and then read it into the system through a named pipe. If you try to read a regular uncompressed file Oracle will freeze after 2 gig. So make sure the oracle import and export files are seeing named pipes and not regular files so they can handle larger amounts of information.

Regards
-R

world wrote:

> Excuse me for my ignorance,
> but when you say you will need to do the same thing when you import the data
> again, what exactly do you mean?
> When importing, you need to pipe to a file while uncompressing before
> importing?
>
> Thanks.
>
> Robert Briley wrote:
>
> > You can get around the oracle export limit or 2 gig by creating a named
> > pipe and exporting to it while dumping the data in the pipe to a tape or
> > other device. This should allow you to export up to 4 gig on a 2.6
> > Solaris machine. Note that in order to import the data again you will
> > need to do the same thing and that you are well advised to confirm your
> > exports by importing them before you declare success.
> >
> > Regards
> > -R
> >
> > Tom Karelin wrote:
> >
> > > Gurus, I need to run export which creates dump file larger then 2 Gig
> > > allowed by Unix
> > > Anyone has code to solve this problem.
> > > Appreaciate your support.
> > > I am on Solaris 2.6 Oracle 7.3.4.5
> > > Michael
Received on Mon Jan 03 2000 - 17:27:19 CST