[unixODBC-support] Is Unix ODBC Driver Manager using /tmp

Thomas A. Lowery tlowery at rparts.us
Mon Nov 1 23:14:02 GMT 2004

On Mon, Nov 01, 2004 at 09:19:25PM +0000, Nick Gorham wrote:
> Thomas A. Lowery wrote:
> >
> >So whatever is opening the tmp file is doing so outside of the DM and 
> >driver?
> >
> To me that looks like its being done in the DM or driver, its logging 
> the entry to SQLFetchScroll and the opening the temp file, then logging 
> the exit of the fetch scroll.
> Just had a though, it could be the cursor lib, that uses a temp file to 
> store the cursor result set in, I bet its that.
> Assuming it is, what the problem with the file, is it failing to clean 
> up after itself ?

I wouldn't say failing to clean up, but accumulating over the course of a run
to the point where /tmp full.
So for an extract of 5.6M records, I get around 900,000 completed before
the process abort with a seek error from the driver manager.
Using df to watch /tmp, I see it go to 100% used.


More information about the unixODBC-support mailing list