Wednesday, April 3, 2013

SMON: Restarting fast_start parallel rollback in alert log


Error:
Today morning I check the Our Production Database Alert Log   and I found some message are shown 

Thu Apr 04 10:54:33 2013
SMON: Restarting fast_start parallel rollback
SMON: Parallel transaction recovery tried





Applies to:
Oracle Server - Enterprise Edition - Version 10.2.0.2 to 11.2.0.2 [Release 10.2 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 24-Apr-2012***
Symptoms
After canceling a delete operation, then, physically killing the OS process and performing a truncate on the same table, the following is reported in the alert.log and trace file:
ALERT LOG
"SMON: Restarting fast_start parallel rollback"

TRACE
Parallel transaction recovery caught exception 12801
Parallel transaction recovery caught exception 30317
NOTE: Trace files are SMON traces found in bdump directory.
Cause
Parallel UNDO operation cannot find record previously deleted.

The error indicates that Oracle is trying to apply some parallel undo and checks to see if the object or record exists, if not, this error is raised.
This generally occurs when a truncate or a delete has taken place and the transaction is canceled.
If another delete or truncate then is issued, if the record is no longer in the UNDO, then you will receive this error.
Solution
No action is required. No corruption applies unless the error is followed by other internal errors on the object.

Thanks.
Happy Reading...
 

No comments: