Hello Bernhard,
yes, recreating the table solves the problem, however it does not fix the bug which led the catalog become corrupt...
But you mentioned that the error occured on any table with a primary key. Do you have 'named primary keys' defined? I am asking, because these named primary keys are handled like a constraint in MaxDB, so maybe your problem was not with constraints in general, but the named primary keys?
That info would help us in trying to recreate the bug.
Regards,
Thorsten
↧
Re: [-9205]: System error: AK Catalog information not found / CONSTRAINT
↧