Re: Protection against corruption

From Bharat Shah: * * * How to Guard against Index Corruption. * * Our product which typically inserts a large number of records in a burst, * corrupts indexes on a table. Most of the time the index is on a 'datetime' * field. * * This is eventually caught with return codes: * 271 - See ISAM error * 105 - Corrupted index * * Manuals and finderr tells about how to correct such a problem (isrecover, drop * recreate etc.). * * My question is how does corruption happen in the first place? and how should * one protect against it? * * All experiences, comments, divine rulings will be appreciated. One way to avoid corrupted indexes from large inserts is to drop the indexes prior to doing the insert 'burst'. This should also speed up the inserts and free up any used disk space available from deleted records ( index file only ). Then, recreate the indexes after the inserts are done. Robert Minter |Data Systems Support| \\\\\\_/// Programmer, Software Development | Orange, CA | ( _ _ ) internet: rob@dssmktg.com | Tel: 714.771.0454 | (| ^ |) bangpath: uunet.uu.net!dssmktg!rob| Fax: 714.771.3028 | \\`-'/ I used to not know, now I know I don't know. \\_/