RE: DBExport Failure -- Incorrectly states "Disk space may be ful l."

I have found our issue with or dbexport, it was a sequence of control characters within a character field in a single row of the first table being exported, I believe by cleaning up this field I will be able to continue my dbexport. Thanks for the help! John -----Original Message----- From: Russ_Evans@doh.state.fl.us [mailto:Russ_Evans@doh.state.fl.us] Sent: Monday, March 22, 1999 10:13 AM To: jep-corp@BOB.KAMAN.COM; informix-list@iiug.org Subject: RE: DBExport Failure -- Incorrectly states "Disk space may be ful l." Assuming it is not a bug with DBExport (I don't know that, I am assuming you have looked into that possibility, and your statement that 'as of Saturday it has started to abort' seems to indicate), you should try to find out what has changed on your system around that time. You may also check your /tmp space, since if you have BLOB data in your databases DBExport will use temp space (or whatever you specify in the DBTEMP variable) to place BLOB data. -----Original Message----- From: Porcello, John [mailto:jep-corp@kaman.com] Sent: Monday, March 22, 1999 8:37 AM To: Informix (E-mail) Subject: DBExport Failure -- Incorrectly states "Disk space may be full." We do a dbexport every night and as of Saturday it has started to abort with the following output: "Disk space may be full. Cannot write to file. Dbexport aborted." There is plenty of disk space and the database seems to be stable, we are running IDS7.3FC6 on Digital Unix V4.0. I have found some information in the archives, but it was on OL 5.08UD2 and it had to do with versions of dbexport, there does not seem to be a resolution for 7.3, can anyone help us? TIA, John E. Porcello, Jr. Corporate DBA Kaman Corporation jep-corp@kaman.com My views and opinions may not reflect those of Kaman Corporation.