bad systable on SE 5.0
Hi,
I just ran into the following problem:
(Sun OS 5.4, SE 5.0UC1)
I dropped a table "buchen" and recreated it. Accessing all other
tables was ok but after getting problems with this table I figured out
the following:
* the original systables entry with tabid=246 was unchanged
* the database files had a (new) extension of 312
* the syscolumns entries had changed to a tabid of 312
I could delete the syscolumns entries and the database file. bcheck on
systables said everything is ok but accessing the systables entry
failed (see log below). I can't delete the systables entry and
recreating the table is impossible, too.
Is there *any* chance to repair the systable or must I spend my next
weekend on rebuilding the complete database?
THX Axel
informix>dbaccess spross -
> select * from systables where tabname="buchen";
tabname buchen
owner sptest
dirpath buchen_246
tabid 246
rowsize 104
ncols 18
nindexes 0
nrows 239837
created 17.01.98
version 16121991
tabtype T
audpath
1 row(s) retrieved.
>
> select * from systables where tabid=246;
No rows found.
>
> delete from systables where tabname="buchen";
240: Could not delete a row.
111: ISAM error: no record found.
Error in line 1
Near character position 43>
--
This is the automatic signature replier. The current signature
is on vacancy. Please leave your login ID and password. THX