Re: Error using dbexport

Rick Stephenson wrote: > > -264 - Could not write to a temporary file. > The database server created a temporary file in the directory > specified by the DBTEMP environment variable, (or /tmp by > default on UNIX systems) but now it has encountered an > error trying to write data into it. Check the accompanying > ISAM error code, and look for operating system error> messages that may give more information. Possibly there > has been a hardware failure; possibly the disk is full. Since > Version 5.01, the DBTEMP environment variable is used by > the INFORMIX-SE database server but not by the > INFORMIX-OnLine Dynamic Server. > > -110 - ISAM error: end or beginning of the file. > Reading rows sequentially, forward or backward, the ISAM > processor has reached one end of the file (table). C-ISAM > programs: This is the normal signal of end of file. Use a > different retrieval mode of isread to reposition the file. SQL > products: See the SQL error message or return code. > > I have looked at my dbspaces and /tmp to see if anything has filled up, none > of that is happening. Is there anything else I can look at to resolve this > problem. DBSPACETEMP is not set to anything either. If DBSPACETEMP is not set temporary tables will be built in the rootdbs. Perhaps that dbspace filled. Also if you have PSORT_DBTEMP set those filesystems are used for sort-work files and one of them may have filled note that Informix uses the PSORT_DBTEMP and/or DBSPACETEMP locations more or less evenly during sorting so the total space that is available for sort-work files is the size of the smallest dbspace or filesystem times the number of dbspaces or filesystems. This is tough to debug because Informix cleans up after itself BEFORE proclaiming the error so you cannot go looking for what filled after the fact you have to have been monitoring things with onstat -d or df -k during processing. Art S. Kagel