Re: Possible problem with dbexport/dbimport serials- SE v4.1 ?

---- original message from Teun Boschloo ---- ++ ++ We are using a laboratory information system based on an Informix ++ database, Informix SE v4.1. For quite some time we have had complaints ++ about strange things happening: losing a record or two (sometimes, not ++ often). These things we could not reproduce. ++ Now the software house came up with a possible explanation. ++ ++ In the database, the serial datatype is used. ++ Once a month we do a dbexport/dbimport/update statistics, because of ++ backup and performance reasons. Now we were told that with this action, ++ Informix loses count of its serials and has to look up the last used ++ number in the database. But, if the record with the last used serial has ++ already been deleted, Informix uses this number again, causing ++ corruption. ++ ++ If this is true, you cannot use dbexport/import on a database with ++ serials in it. Now I wonder if this is a "known" bug (if yes, since ++ when), and if this explanation holds for our corruption problems. ++ This is a know 'limitation' of dbexport/dbimport. You can modify the <database>.sql file to set the serial number after the export but you have to find out what it is before the import. I would suggest a change to the application that uses a different (i.e. less volitile) method of assigning the keys. ++ Thanks in advance for every helpful reaction! ++ ++ Teun Boschloo ++ Waterleiding Mij. Gelderland - Velp (Gld) ++ The Netherlands ++ EMail: tubateun@xs4all.nl ++ ++ -- Jerry M. Denman -- Director of Special Projects Sherwood Systems (a division of Sherwood Mfg Co. Inc.) jerry@sherwood.com ------------------------------------------------------------------------------ The manner in which one endures what must be endured is more important than the thing that must be endured. - DEAN ACHESON