RE: c-isam re-write failures
Posted in 1998
Topics: Migration, Import/Export & Data Conversion, Platform-Specific Issues
Its been a while since I used C-ISAM but as I recall you cant modify the primary key index of a C-ISAM file. You can use isrewcur if any data other than the primary key has changed. If the primary key changes you must delete and rewrite the row. I believe this is what SE does. > ---------- > From: Sean Kelsey[SMTP:seank@teepee.demon.co.uk] > Reply To: Sean Kelsey > Sent: 02 December 1998 12:38 > To: informix-list@iiug.org > Subject: Re: c-isam re-write failures > > What problems are you getting ?? Are you using Informix SE at all ?? > > Usually, if isam can re-write the record back to its original position it > will do. If you are altering the physical length of the row, then it will > try to append it to the end of the DAT file. The problem with using isam > routines to update the tables instead of using Informix is that any data > that is added to the tables is not reflected in the Informix catalogue > tables i.e. you have to run UPDATE STATISTICS on a regular basis. > > Once you have written the row back to the table, can Tetra/Informix locate > the row using the date as the key ?? Which Tetra table is it ?? ( I am > fairly familiar with Tetraplan, T2000, CIM, Chameleon 2000 & CS3 ). > > Does 'bcheck' not solve the problem ? > > What is the index structure ( can you send me an 'isdata' of the table ? ) > > Sean > > > > J.S.Kinghorn wrote in message <72us71$18n$1@flex.london.pipex.net>... > >Hi > > > >I have the following problem using c-isam ver 4.10 on an AIX platform. > > > >I am reading in a Tetra file using it's second index ,altering a date, > which > >is part of the primary key and writting it back using isrewcurr. > > > >The information is being written succesfully but the primary index is not > >being updated and the record remains in the same physical place in the > .dat > >file. > > > >An Unload and load curres the problem but this is not a practical > solution > >as the routine is run frequently throughout the day > > > >Is this a known problem and is there a fix / work round > > > >Thanks > > > > > > > > > >