Sami / Buddy,

 

Thanks for the suggestion – I had tried a RELOAD but I couldn’t reload to the same location, however I have now reloaded it to elsewhere, copied it back, and I trust that it keeps going without further errors.

 

Thanks for your help.

 

Regards

 

 

John Docherty

 


From: [email protected] [mailto:[email protected]] On Behalf Of Sami Aaron
Sent: Thursday, 3 November 2005 8:18 a.m.
To: RBG7-L Mailing List
Subject: [RBG7-L] - RE: Problems updating index file (7.5)

 

John -

 

This message usually means that the index file is, indeed, corrupted.  Autochk does NOT check for errors in the index file. 

 

I recommend that you make a backup then reload the database - that will re-build all the index files.  If you continue to get these errors, post another message here - you may need to do a complete UNLOAD of the database.

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Sami Aaron

Software Management Specialists

913-915-1971

[EMAIL PROTECTED]

 

 


From: [email protected] [mailto:[email protected]] On Behalf Of John Docherty
Sent: Wednesday, November 02, 2005 1:07 PM
To: RBG7-L Mailing List
Subject: [RBG7-L] - Problems updating index file (7.5)

I have a database which keeps on generating the following error when I try to insert a row into a table

 

<WARNING> Problems updating index file.  Index file may have been corrupted. (2860)

-ERROR- I/O problems - Check for a full disk. (2009)

 

There is certainly no lack of space on the disk. Does anyone have any suggestions as to what may be causing this, and how to fix this. (RScope doesn’t find any errors, neither does autochk)

 

Any suggestions would be much appreciated. Thank you.

 

Regards,

 

John Docherty

 

Reply via email to