Re: Database corruption. How? Leading to bcheck. - clarification.

Well, in that case, database corruption can occur in all the ways that data corruption can occur in any C program. Stray pointers, uninitialized variables, incorrect parameters to C-ISAM calls, etc... You also need to ensure that your program always closes all the files cleanly, and terminates all transactions if you are using a transaction log. One of the nastier ways of running into problems is to accidentally interpose your own function X for a function in the C-ISAM library also called X. Normally, this leads to immediate core dumps (which might or might not corrupt your C-ISAM files), but sometimes you get the bizarrest results. I'd rate this an unlikely, but not impossible, cause of problems. If your own code has a half-way decent naming convention, it is very improbable. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> >From: nausy@aol.com (Nausy) >Date: 18 Jul 1996 09:14:19 -0400 >X-Informix-List-Id: <news.26293> > >Hi all, >To further clarify this original posting it should be noted that the >application that is having problems with corrupt indexes is written is C >with embedded C-ISAM calls. > >Cheers, Ian.