C-ISAM Corrupted Indexes -- Why?
Posted in 1991
Path: emory!swrinde!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!ucdavis!csus.edu!csusac!utgard!kimb From: kimb@utgard.uucp (Kim Berry) Newsgroups: comp.databases Keywords: C-ISAM Message-ID: <1991Aug27.202416.16037@utgard.uucp> Date: 27 Aug 91 20:24:16 GMT Organization: QMA, Inc., Rancho Cordova, California Does anyone know of a possible cause or way of preventing corrupted ISAM indexes? Corruption is a constant problem for us in the field. We are using Informix C-ISAM v3.10.00 w/ MS-DOS 3.3, both as a single user and on Novell Netware 2.10a on various makes of XT, AT, and 386 clones. C-ISAM is a Microsoft-C library. We are not able to research the problem in depth since we do not have the C-ISAM source code (because Informix charges $40,000.00 for it). Is corruption a common problem with all ISAM implementations? Would we be better off switching to Btrieve (which claims to use "pre- imaging" to self-correct any corruption)? And regarding Btrieve, does anyone know how its performance compares with C-ISAM? Any advice or common experiences appreciated. """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" (Mr.) Kim Berry utgard!kimb@csusac.ecs.csus.edu QMA Inc """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""