Hi Rick,
This might be related to your problem: dbimport (and I think dbexport
and db-access as well) creates temporary files in either /tmp or DBTEMP
if it has to process blob data. DBSPACETEMP will be ignored in this
case. This thing is documented in the 7.2 Informix Migration Guide as an
NT only feature, but actually works on HP-UX 10.20 with IDS 7.24.UC4 (I
tested it and Informix UK confirmed it). Informix logged this issue as a
documentation defect - 88942.
Best regards,
Cristian.
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.
>
> Any help would be appreciated. Thanks,
> Rick Stephenson
> rick@byu.edu