Oracle Internals - qq
766689Aug 19 2010 — edited Aug 30 2010Have a .Net application using transaction scope management - essentially a Distributed Transaction - but NOT via a dblink.
I need to be able to isolate those sessions (addr/sql_id/sid) for some troubleshooting.
I 'believe' they all require a 'DX' lock during some phase of the cursor life (not sure which).
Any ways to have the session hold the DX lock longer for testing ...... eg manual lock/sleep/update ???
else - any other thoughts ??
I reference this link which appeared useful ...... but mixed results
http://www.jlcomp.demon.co.uk/faq/find_dist.html
john