SegmentMap is corrupted

[Steve Albin]

On Wednesday, February 14, 2007 sunshine at public.kherson.ua (Ruslan Zasukhin) wrote:

>I do not think it is related to Convert_1_2().
>You can convert_1_2 then flush or db.close()
>Done.
>
>It is out of game.

After I wrote this, I realize that after I do the Convert_1_2, I also change the structure of the DB and update data of all records in some tables.  I have just updated my app to add a flush on every 100 updates and I've sent it to my user.  

The reason I feel that it was related to Convert_1_2 is because I'm only having trouble with databases that have been converted.  I wasn't thinking everything through and when you mentioned before that segmentmap corruption occurs with many updates, I had forgotten about the updates I do after conversion.  This user that is having the problem has a bigger database by far than other users, so if massive updates cause the problem, then he would be the likely candidate to have it.

>
>Clone cannot produce db with already bad segment map..
>If it do -- this is bug. So far nobody else meet this.
>
>So assume cloned db is fine.
>Then some NEXT operation cause corruption.

I cloned my user's converted database and sent it back to him and he continued to have the crash without doing ANY updates on the DB.  But, I'm not confident that the clone was good.  As I said, it took 4 hours to run and I was doing nothing else on my computer.  If my fix to the conversion process does not solve the problem, then I will revisit the cloning.


>We have PCs so we can try your app + db + steps later.


I will very interested to know what you find.

Thanks,
Steve

-- 
Steve Albin - Montclair, NJ
http://www.jazzdiscography.com/
http://www.steve-albin.com/