Thanks Hemant. That explains it. On Thu, Mar 5, 2015 at 10:51 PM, Hemant K Chitale <hemantkchitale@xxxxxxxxx> wrote: > V$fast_start_transactions is populated only in respect of rollback > initiated by instance recovery from a startup after shutdown abort or > instance or server failure. > > Sent from my smart phone. > Hemant K Chitale > On 05-Mar-2015 12:25 PM, "Gokul Kumar Gopal" <gokulkumar.gopal@xxxxxxxxx> > wrote: > >> Thanks Dominic/Mark/Hemant, >> >> I was able to able to map v$transaction.ses_addr = v$session.addr. This >> did it. >> >> You are right the transaction was doing a long running rollback. However, >> the used_blk started decreasing only >> after 30-45 mins after killing the session. >> >> Are there other indications to understand this behavior better ? >> >> This hang behavior tempted us to look for a db bounce option ;-). >> >> We had a similar issue a year back. But then, we had an entry in >> v$fast_start_transactions table. >> >> This time, there was no entry in this entry. >> >> Any idea, why the entry could be missing this time ? >> >> Thanks >> Gokul >> >> On Thu, Mar 5, 2015 at 5:21 AM, Hemant K Chitale < >> hemantkchitale@xxxxxxxxx> wrote: >> >>> If you killed the process, the session no longer exists. PMON has >>> initiated the cleanup. >>> >>> Sent from my smart phone. >>> Hemant K Chitale >>> On 04-Mar-2015 10:17 PM, "Gokul Kumar Gopal" <gokulkumar.gopal@xxxxxxxxx> >>> wrote: >>> >>>> Hello, >>>> >>>> 11.2.0.3 RAC. >>>> >>>> We had run a big feed job by mistake. Later the job was killed. >>>> >>>> All selects on a table that was part of the feed transaction is taking >>>> time. >>>> >>>> From v$transaction table I can see an entry with used_ublk = 700000. >>>> >>>> However, I am not able to map the v$transaction.addr = v$session.taddr. >>>> >>>> No rows returned. >>>> >>>> Where else can I find the session information of the v$transaction >>>> entry ? >>>> >>>> Rgds, >>>> Gokul >>>> >>> >>