On Intel Linux, Ingres 2.6/0305 a copydb fails when the size of the
binary file reaches the size of 2 GB.

In some (old) threads I read that the Linux version of Ingres does not
support files larger than 2 GB. Is that correct?

If it is: How can I unload the table (18 GB) that gives the problem?

If it is not: Is it a Linux problem?

Thanks,

Erwin

On 8 Jun 2005 02:02:48 -0700, eteunisse <eteunisse@gmail.com> wrote:
> On Intel Linux, Ingres 2.6/0305 a copydb fails when the size of the
> binary file reaches the size of 2 GB.
>
> In some (old) threads I read that the Linux version of Ingres does not
> support files larger than 2 GB. Is that correct?
>

It's true. Ingres 2.6 supports kernel versions that may not
necessarily have large file support.

> If it is: How can I unload the table (18 GB) that gives the problem?
>

Named pipes.

1) create a named pipe (aka fifo)

mkfifo myfifo

2) create a background process to read from it

gzip < myfifo > file.dat.gz &

3) edit your copy.out to write to the fifo rather than a file

copy(...
...
into 'myfifo'

4) run the copy.out

sql mydb < copy.out

To reload do the reverse

Step 1 is the same

2*) gunzip -c < file.data.gz > myfifo &

3*) copy(...
...
from 'myfifo'

4*) sql mydb < copy.in

Technically you don't need to compress - you could use cat instead of
gzip - provided your kernel and filesystem support > 2Gb files.

> If it is not: Is it a Linux problem?

It's an Ingres 2.6 limitation, but it could also be a Linux limitation too.

>
> Thanks,
>
> Erwin
>
> _______________________________________________
> Info-ingres mailing list
> Info-ingres@cariboulake.com
> http://mailman.cariboulake.com/mailm...py/info-ingres
>


--
Paul Mason

Thanks Paul!

Very efficient solution!