This page covers stop, abort or termination of a Rollback in Oracle.

“You can abort rollback but I think it can mess up the database”, was my last answer I gave when I was asked this question. I also searched Google for “abort a rollback in oracle” and I found some interesting details that I had never found because the client was attempting a restart, and obviously that restart was still trying to do the rollback (or perhaps rollback the rollback itself):

For Google abort a rollback in oracle

Or google stop a rollback in oracle

Just don’t forget to reset the trace context at the end again otherwise you might have a very bad day some time soon

Also, I seen this particular issue before with huge performance slow downs as a result of rollbacks and/or attempts to abort of those rollbacks when working with fast refresh materialized, and perhaps forgotten bu incredibly large materialized view logs. If you think about it: the materialized view is constantly being appended to, and you perform a fast refresh that may be large or has not been done for a while, and maybe you’re trying to do replication over a global network … what happens is perhaps the append process might catch up with the fast refresh process in terms of transactional snapshot containment and then you might get a lot of conflict between the two competing processes. And you probably won’t hit a snapshot too old error either because there isn’t enough rollback to actually run out of rollback space, and so on and so forth.