As a follow-up to this thread, I identified the source of the problem One of my programs creates a temporary table (TEMP_COLS) with a list of a given table's column names and data types. It then cycles through each column name to set null or missing values to values of my determination.
The problem exhibits itself when using the temporary table. Since I've changed "TEMP_COLS" to a "permanent" table I've had no problems. This particular program is called frequently throughout my database system. The vast majority of the time there is no issue but for some reason when dealing with some specific tables I would get the "I/O problems" error when the temporary table was used. There are, of course, numerous ways of accomplishing an intended goal. I am going to devise a better method of doing what the program does. I remember a wise person saying, "If you can dream it you can do it. . ." Excuse me while I do some dreaming. Thanks to all who provided guidance and suggestions. Mike Ramsour AK Steel Coshocton Works Quality Department Phone: 740-829-4340 Cell: 740-502-1659 From: "A. Razzak Memon" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: 04/01/2014 12:41 AM Subject: [RBASE-L] - Re: Error message: I/O problems. Check for fullDisk Sent by: [email protected] At 06:11 AM 3/29/2014, Mike Ramsour wrote: >One of my programs has been generating the error mesasge: >-ERROR- I/O problems - Check for a full disk. (2009) > >Is there anything in particular I can look for in the program that might >cause this error to be generated? There are quite a few calculations in >the code including several instances of the ROUND function. > >It happens both in Turbo V-8 and eXtreme 9.5 64-bit. > >I have RSTYLEd the code and TRACEd it several times. This is one of those >situations where the program runs fine when it's run as a standalone program >but when it's run as part of a sequence of dozens of programs it errs out >each time. > >Any suggestions would be appreciated. Confidentiality Notice This message is intended exclusively for the individual or entity to which it is addressed and may contain privileged, proprietary, or otherwise private information. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message.
