Restarting Long-Running Transactions | Oracle Database 10g. High Availablity with RAC Flashback & Data Guard

< Day Day Up >

In the event of some kind of instance outage, there will inevitably be transactions that will stop, and then have to be restarted manually. This can lead to significant shortcomings in time-sensitive reporting and processing.

At Horatio's Woodscrews, the developers that were sitting idle due to the Linux servers having no data decided to try and get a little work done by connecting to the production database to review some of the database structure. However, one of the developers had installed a beta version of the ODBC drivers. When this ODBC driver connected to the production database, it caused a heap corruption that resulted in an ORA-600. The ORA-600 caused the database to crash.

Just like that, all the long-running reports that had been generated by the Accounts Receivable teams began to receive the error ORA-3113 'End-of-File on Communication.' The DBA's pager started to beep, and beep, and beep. He was able to restart the database, but all of the long-running transactions had to be restarted.

< Day Day Up >