Re: dbexport failed with "Disk space full" message.
Posted in 2000
Topics: Storage & Space Management, Server Administration, Migration, Import/Export & Data Conversion
You could also 'partition' your table among several temp tables using the PK
and export these tables to separate files. Not very pretty, but it should
work.
SC
> Hi Family.
>
> I just tried a dbexport on a database with some enormous tables. The
> dbexport failed with the message: Disk space full.
>
> Clearly, the dbspaces and the file system I am unloading from and to
> are far from full. Only at the second failure did it occur to me to
> look at the .unl files. ls -lt indicated the most recently written .unl
> file to have just hit the 2-GB boundary.
>
> My expletives at this revolting develpoment aside, I went looking for a
> similar victim in this newsgroup and I found a long thread, started by
> one CHENUS Thierry, that lamented over it.
>
> The only way around this stupid restriction in dbexport was to export
> to tape. And, according to the info in the thread, there is still a 2-
> GB restriction on the amount of data dbexport will write to a tape,
> even a 40-GB tape.
>
> I am still using 7.2 (don't worry! We're upgrading soon to 9.2! ;-) but
> it seems that 7.3 is no smarter. I don't know if it improves in 9.2
> either.
>
> Next straw to clutch at: Does anyone out there know of a utility to
> replace dbexport and gets around the 2-GB constraint? Has anyone (i.e.
> Jonathan? Art?) written one?
>
> Thanks much, folks.
> --
> +----- Jacob Salomon - DBA JSalomon@bn.com - --------------------------+
> |------------------- Bulletin Board Announcement ----------------------|
> | Congregants will please note that the bowl at the back of the church |
> | bearing the sign "For the Sick" is for monetary contributions only. |
> +----------------------------------------------------------------------+
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.