Mainly pmon (the process monitor), but any
session that needs to use a block that has been
modified by the killed session may tidy up that
block before pmon gets to it.
--
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
The educated person is not the person
who can answer the questions, but the
person who can question the answers -- T. Schick Jr
One-day tutorials:
http://www.jlcomp.demon.co.uk/tutorial.html
Three-day seminar:
see http://www.jlcomp.demon.co.uk/seminar.html
____UK___November
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
"Michel Cadot" <micadot{at}altern{dot}org> wrote in message
news:3fd0a2f7$0$28713$626a54ce_at_news.free.fr...
> Hi,
>
> When a session executes a rollback statement, you can follow the rollback
> by watching the used_blk column in v$transaction.
> But when the session is killed, taddr in v$session is "set" to null and
the row in the
> v$transaction is deleted.
> So, how can you follow the rollback executing for this session?
> In addition, who executes this rollback? The server process (dedicated or
> shared) or a background process?
>
Received on Fri Dec 12 2003 - 06:00:37 CST
