Hi Bernhard,
thank you for uploading the catalog file. Unfortunately it did not give us any new insights about why the catalog should have become corrupted since the affected table 'RKA_ANTRAGBEARBEITUNG' did not have any unusual constraints set.
We might have found the bug with a database restart followed by a 'default' kernel trace plus 'select' option enabled while the catalog was still corrupt, but now it is too late for that since you had that table already dropped and rebuild.
We have added this incident to our bug tracking tool per PTS1254412, although at this point we most likely do not have enough information to fix it:
"Error -9205 "System error: AK Catalog information not found: 000000000003F5F5000A000F" at
SELECT CONSTRAINTNAME, DEFINITION, CONSTRAINTTYPE FROM DOMAIN.CONSTRAINTS WHERE SCHEMANAME = <schemaname> AND TABLENAME = <tablename>
Check catalog does not show any problem.
Problem is probably a lost catalog record for some constraint information (see cak_eviewdesc in a44constraint_into_moveobj)."
Regards,
Thorsten