Hi again,
More useful information: we had today again a few db crashes and they all seemed to be related to one specific table where we could insert data, but trying to update any row failed with an "AK Cachedirectory full" error. In an attempt to find a solution, we temporarily disabled one "update" db trigger on that table, and this has immediately solved the problem. We reactivated the trigger to see if this was not a coincidence, and the problem immediately reappeared (although this time we got an "[-9206]: System error: AK Duplicate catalog information" error which quickly lead to a "Restart required" error). De-activating the trigger again solved the problem. Note that this trigger usually works without any problem, so it's also unclear why it suddenly lead to that problem.
Actually we also noticed in the past that adding or removing a constraint on that particular table could lead to suddenly having some "AK" errors. Also adding or dropping columns, or adding/removing foreign keys seemed to sometimes make that table "unstable".
Maybe that's a silly question, but is there a way we could check if the internal "structure" of a table is somehow corrupted? For example we also get a strange error that when a constraint is violated, the exception usually reports the wrong constraint, having an offset of 1 with the real constraint (I don't remember if it reports the previous or next constraint instead of the right one).
Any idea or hint about a possible problem?
Thanks,
Christophe