Hi Thorsten,
I just uploaded the catalog extract. We actually have 33 constraints with the name YEAR_ID, so we need the table name to find out which one caused the problem (it might actually be the ones from tables PERSON and PERSON_LOG, because we sometimes get AK errors with these 2 tables). FYI, we actually almost get all AK errors with the table ACCOUNTTRANSACTION.
Actually we recently copied the entire table ACCOUNTTRANSACTION into a new table, dropped the old table, and renamed the new one to ACCOUNTTRANSACTION. We then reinserted all foreign keys and constraints ... but it did not help. :-(
By the way, did you check the file KnlMsgArchive in the diagpack files I uploaded? There you can see a stacktrace of the error when the DB crash occurs, it's a SIGSEGV: maybe you find out something useful there?
Thanks again for your support,
Christophe