Enable the alert :
SQL> alter system set events '00942 trace name errorstack level 1';
Disable the alert:
SQL> alter system set events '00942 trace name context off';
Oracle DBA and beyond; these are practical tips for day to day DBA operation and maintenance; a place where you would come to look for a quick fix for a burning situation. I hope that by sharing all these, we all will become better in what we do. And on the way, I hope to save you some sweat :-)
Enable the alert :
SQL> alter system set events '00942 trace name errorstack level 1';
Disable the alert:
SQL> alter system set events '00942 trace name context off';
This is a very common problem, we kill an update/merge and is taking forever to rollback.
There are 2 solutions for this:
1) Kill the spid oracle shadow process and set the parameter below:
SQL> alter system set fast_start_parallel_rollback=HIGH;
2) Bounce the DB and set the same parameter as above.
SQL> alter system set fast_start_parallel_rollback=HIGH;
The only issue now, to monitor the rollback, we'll need a different query:
SQL> SELECT usn, state, undoblockstotal "Total",undoblocksdone "Done",undoblockstotal-undoblocksdone "ToDo", DECODE(cputime,0,'unknown',SYSDATE+(((undoblockstotal-undoblocksdone) / (undoblocksdone / cputime)) / 86400)) "Finish at" FROM v$fast_start_transactions;