Re: bad systable on SE 5.0

axsander@okay.net (Axel Sander) offerred: +Thanks for you advice but I had no luck. I can *select* the bad +systable and view its contents but that's all. No *update*, no +*delete*, nothing (but an error). You mean you can't perform an update on systables? As user informix? You can't do it as any other user, but userid informix can alter the contents of system catalogs. If you are getting an error as user informix, try running CHECK TABLE systables; in SQL (this is the same as doing a bcheck/secheck). It's possible, if the table got hosed some way, that the index on it is corrupt. The error codes you get when you try and update would be useful to know. +BTW, I think, an update of the tabid +in systables is not possible, cause this is a "serial" field ? I You can update a serial field via sql. The only thing a serial field by itself does for you is to provide an automatically sequenced domain when you insert a record into the table with a value of 0 for that field. All other operations are the same as on any integer field. Now, if you built a unique index on it, or applied any other sort of constraint, there may be some limitations as to what can be done with a serial field. But a serial in of itself has no inherent limitations along those lines. +updated the syscolumns and all other tables to the *old* values and +renamed the .dat file. I can access this table now, but the systable +is *still* defect, so I think I have to rebuild the complete database +:-( If you prefer to rebuild, that will certainly work. I always prefer the challenging way ;-). Dave ** Dave Kosenko <davek@summitdata.com> ** Director of Training Services (732) 469-4070 ** Summit Data Group (an Informix Authorized Education Center) ** Find my advice useful? Let me teach you everything I know about ** Informix. Sign up for OFFICIAL Informix training at SDG. ** For details, see http://www.summitdata.com/training