Re: Help with INFORMIX error message
Posted in 1993
}> I'm experiencing a problem with a INFORMIX 4GL program }> that I'm hoping someone has seen before and can offer a }> solution. }> }> The error message I'm getting is: }> }> SQL statement error number -242 }> ISAM error number -2 }> Could not open database table (profile). }> }> Does any know the mapping for the error numbers to the actual error? }> }> If it's important, I'm running a very old verison of INFORMIX }> version 1.10.04E, created around the 1988 time frame. } It matters. It's time to upgrade. And was there really a 1.10.04E? I'd } believe 1.10.03E without quibbling, but only that, 1.00.00x and 1.10.06x. Yep, there really was an 1.10.04E. } Anyway, with the next release, the finderr utility provided the answer to } such questions. It sayeth: Thanks for the info on 'finderr'. It will come in handy when I'm ready to upgrade. } -242 Could not open database table table-name. } } The database server is unable to begin reading a table. Check the } accompanying ISAM error code for more information. There may be a problem } with file permissions, or a hardware error, or the system catalog may have } been corrupted. Unless the ISAM error code or an operating system message } points to another cause, run the bcheck utility to verify file integrity. BCHECK comes out clean on all files with all qualifiers. } -2 No such file or directory. } } An operating system error code with the meaning shown was unexpectedly } returned to the database server. Look for operating system error messages } that may give more information. Unfortunately, the error message doesn't tell you WHAT "file or directory". I posted all the available information -- there isn't any other "operating system error messages". } Please respond to this newsgroup as well as to me directly. } Thanks for any solutions, leads, or pointers. } What have you changed recently that means that the program was working and } now doesn't? Go and undo it. } } I'd hazard a guess that you moved the database, or deleted a file which you } thought was not in use but actually was. If you'd got -1, then you'd have } been fiddling with permissions. Possibly, you've altered DBPATH. The database was moved in the sense that there was a "head crash" and the database was restored from a BACKUP tape. That's the best that can be "undone". -Regis