Re: Export >2GB files w/7.3.4.3.0 & Solaris 2.6

The other way to get around it is to compress the file (thru a pipe in the background) while doing the export i.e. :

mknod pipe.file p
cat pipe.file | compress > db.dmp.Z &
exp / file=pipe.file

then import it using:

mknod pipe.file p
zcat db.dmp.Z > pipe.file &
imp / file=pipe.file

Mike Merrett

Steve Phelan wrote in message
<36D6C94F.D6F5F61D_at_toneline.n-o-s-p-a-m.demon.co.uk>...
>And you might want to also consider exporting direct to tape, but be warned
>that this can be slow...
>
>Steve Phelan
>
>(Oracle 7 & 8 OCP)
>
>Linda H Montgomery wrote:
>
>> You dont say what Oracle versions you are dealing with, but there is an
>> article on Oracle's Metalink called
>> '2Gb or Not 2Gb - File limits in Oracle' <Note:62427.1> dated 05-Nov-1998
>> that discusses exports over 2G. It states that
>>
>> "....most versions of export use the default file open API when creating
>> an export file. This means that on many platforms it is impossible to
>> export a file of 2Gb file limits with export...."
>>
>> So you may want to check out your version of export and see if this
>> applies. We are on HP-UX not Solaris, but we are successfully exporting
>> via named pipes to a zipped file to get around the 2G file limits at this
>> time.
>>
>> Bob Wickline wrote:
>>
>> > OK. I convinced my customer to let me upgrade to Solaris 2.6 (took me
>> > 4 months!) so we can perform full database exports which have grown
>> > past the 2GB file size limit on Solaris 2.5.1. However, I STILL
>> > cannot export a file past 2GB.
>> >
>> > WHY?!?!
>> >
>> > I can issue the command "mkfile 3000M testfile" as oracle so I know
>> > that I have all the ulimit stuff fixed. However, when I try to either
>> > create a datafile larger than 2GB or export to a file >2GB it crashes.
>> >
>> > What's up?
>>
>> --
>> Linda Montgomery
>> Database Analyst
>> James Madison University
>> montgolh_at_jmu.edu
>
Received on Fri Feb 26 1999 - 15:42:17 CST