G
George Potemkin
Guest
Development team did a big job while investigating a root case of the errors. First of all, two incidents that I mentioned above were caused by two absolutely different errors: SYSTEM ERROR: Error in undo of record delete (815) SYSTEM ERROR: Error in undo of record delete (819) There is the error # 820 but our customers did not yet ;-) get it: SYSTEM ERROR: Error in undo of record delete (820) The error 815 is fatal for database. To get an access to a database we need either to use the -F option or to roll forward AI files to a time before a corrupted note was created (it’s not the time when message # 815 was issued). The error 819 is recoverable. Transaction undo performed by a client’s session failed but database crash recovery will be successful. In our case crash recovery took a long time (more than 5 hours) because the remote user did not really logout from database which resulted in a very large bi file (user’s transaction stayed open for a week). The error will be fixed in 12.1. IMHO, a workaround for such errors: on standby database do not apply AI files that contain the notes for transactions that are not yet committed on source database.
Continue reading...
Continue reading...