Re: Error -229 cannot open or create a temporary file
In article <5tcr84$3l8@cssun.mathcs.emory.edu>, "Maria L. Wilson" <m.l.wilson@larc.nasa.gov> writes > >--------------F12EB7EAE3F35812F39D06F8 >Content-Type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >Greetings, > > We have Informix 5.0 running on a Unix/Sun machine. Yesterday we >began getting calls that users were getting SQL statement error number >-229. >> > Could not open or create a temporary file. >> > SYSTEM error number -162. >> > ISAM err: BlobSpace does not exist. >when they ran a 4GL or ISQL application. Looked in the message log and >could not see anything out of the normal. ALso checked the temporary >space --- plenty of room. > >The only thing that gave an information was tbcheck which looked like >the system catalog tables were corrupt. We did a restore and >everything was back to normal. > >Can anyone shed some light on what possibly could have caused all >this? Anything to do to prevent? > >TIA, >Maria > >-- >----------------------------------------------------- >Maria L. Wilson Computer Sciences Corporation >NASA Langley Research Center >3217 N. Armstead Ave. Hampton, Va 23666 >email: m.l.wilson@larc.nasa.gov >phone: 757-766-8265 >fax: 757-766-2571 >----------------------------------------------------- > > > >--------------F12EB7EAE3F35812F39D06F8 >Content-Type: text/html; charset=us-ascii >Content-Transfer-Encoding: 7bit > ><HTML> >Greetings, > ><P> We have Informix 5.0 running on a Unix/Sun >machine. Yesterday we began getting calls that users were getting >SQL statement error number -229. ><BR>> > Could not open or create a temporary file. ><BR>> > SYSTEM error number -162. ><BR>> > ISAM err: BlobSpace does not exist. I have seen this problem under 7 which was because the dbspace where temporary table and sort files were being created was full. i.e. the real error is Could not create temporary file + out of space. It was a bug in Online 7, possibly something similar is occuring in Online 5... ><BR>when they ran a 4GL or ISQL application. Looked in the message >log and could not see anything out of the normal. ALso checked the >temporary space --- plenty of room. > ><P>The only thing that gave an information was tbcheck which looked like >the system catalog tables were corrupt. We did a restore and >everything was back to normal. > ><P>Can anyone shed some light on what possibly could have caused all >this? >Anything to do to prevent? > ><P>TIA, ><BR>Maria ><PRE>-- >----------------------------------------------------- >Maria L. Wilson Computer >Sciences Corporation >NASA Langley Research Center >3217 N. Armstead Ave. Hampton, Va 23666 >email: m.l.wilson@larc.nasa.gov >phone: 757-766-8265 >fax: 757-766-2571 >-----------------------------------------------------</PRE> > </HTML> > >--------------F12EB7EAE3F35812F39D06F8-- > -- David Williams