Error 211 Error Isam 111

Posted in 1999

Roxana Spavioli — Mon, 04 Jan 1999 19:01:26 -0300 — source: Informix-list mailing list archive (1991-1998)

I have this problem. 211: Cannot read system catalog (syscoldepend). 111: ISAM error: no record found. Anybody know the solution? Thanks -- Roxana Spavioli --------------- roxs@tsubcero.com.ar

↪ replying to Roxana Spavioli

Laurent COLLIGNON — Tue, 05 Jan 1999 10:43:15 +0100 — source: Informix-list mailing list archive (1991-1998)

Please give us more informations on the engine (SE, Online OWS or ODS) and the tools (I4gl, D4gl and so on). Roxana Spavioli wrote: > I have this problem. > > 211: Cannot read system catalog (syscoldepend). > 111: ISAM error: no record found.> > Anybody know the solution?

↪ replying to Roxana Spavioli

Art S. Kagel — Tue, 05 Jan 1999 13:57:44 -0500 — source: Informix-list mailing list archive (1991-1998)

Roxana Spavioli wrote: > > I have this problem. > > 211: Cannot read system catalog (syscoldepend). > 111: ISAM error: no record found.> > Anybody know the solution? Yup export the entire database and drop and create and reload it. Someone messed with your system catalog table you may be hosed but this is the only chance you have. Can you restore from archive to a point before this problem showed up? Art S. Kagel

↪ replying to Art S. Kagel

Dragi Raos — Tue, 05 Jan 1999 20:46:21 +0100 — source: Informix-list mailing list archive (1991-1998)

Art S. Kagel wrote: > > Roxana Spavioli wrote: > > > > I have this problem. > > > > 211: Cannot read system catalog (syscoldepend). > > 111: ISAM error: no record found.> > > > Anybody know the solution? > > Yup export the entire database and drop and create and reload it. > Someone messed with your system catalog table you may be hosed but > this is the only chance you have. Can you restore from archive to a > point before this problem showed up? > > Art S. Kagel If this is a result of 'long transaction aborted' while altering tables, and somebody got impatient and brought the engine down during rollback (it happend to me once with 5.03), there is a chance that even export won't work. In that case there are two instances of altered table, new one with normal name, and 'old' with some strange name beginning with blank. Of course, system tables like dependencies, references and such point a bit to one, a bit to other. I recall I was able to do 'open heart surgery' on sys tables and recover everything. Just study content of various system tables very carefully. And, of course, as Art suggests, restore is probably the easiest option. Good luck! Dragi "Bonzi" Raos

Glossary

ISAM error