Slot number is: id1 - 65536 * trunc(id1/ 65536) Your analysis is perfectly reasonable. Collision on unique indexes would cause TX mode 4. The logic is identical to that for PKs and UKs. Regards Jonathan Lewis http://www.jlcomp.demon.co.uk The Co-operative Oracle Users' FAQ http://www.jlcomp.demon.co.uk/faq/ind_faq.html Optimising Oracle Seminar http://www.jlcomp.demon.co.uk/seminar.html June 2004 UK Manchester July 2004 Iceland July 2004 USA California Aug 2004 USA North Carolina Sept 2004 UK Manchester Sept 2004 USA NYC Oct 2004 USA Boston ----- Original Message ----- From: "Diego Cutrone" <diegocutrone@xxxxxxxxxxxx> To: <oracle-l@xxxxxxxxxxxxx> Sent: Wednesday, May 05, 2004 1:43 AM Subject: Re: V$session_wait question and rollback segments Yeap, Sorry Jonathan. This is the correct infomation from v$lock (ID1 and ID2): SID TY ID1 ID2 LMODE REQUEST CTIME BLOCK --------- -- --------- --------- --------- --------- --------- --------- 112 TX 196661 514403 0 6 439874 0 I know I can get rollback segment ID from "trunc(ID1/65536)". Do you know how to get the slot number? BTW, I think I have finally found the cause of the problem from my other question: (the TX 4 enqueue wait --) ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------