Roger that, what I was more joking at was to not even get the row at all. The fastest way to do anything is to not do it at all. ;-) (My kids seem to have listen to me a bit too much on this point....) =================== Ric Van Dyke Education Director Hotsos Enterprises LTD. -----Original Message----- From: Jonathan Lewis [mailto:jonathan@xxxxxxxxxxxxxxxxxx] Sent: Wednesday, July 24, 2013 11:04 AM To: Ric Van Dyke; ORACLE-L Subject: Re: Doubt related to ROWID Well, You could avoid the LIO by using the result cache, but there are far fewer latches on the result cache, so not doing the LIO might cause more contention and therefore be more resource-intensive than doing the LIO ;) Regards Jonathan Lewis http://jonathanlewis.wordpress.com/all-postings Author: Oracle Core (Apress 2011) http://www.apress.com/9781430239543 ----- Original Message ----- From: "Ric Van Dyke" <ric.van.dyke@xxxxxxxxxx> To: "Jonathan Lewis" <jonathan@xxxxxxxxxxxxxxxxxx>; <John.Hallas@xxxxxxxxxxxxxxxxxx>; <JSweetser@xxxxxxxx>; <ecandrietta@xxxxxxxxx>; "ORACLE-L" <oracle-l@xxxxxxxxxxxxx> Sent: Wednesday, July 24, 2013 4:01 PM Subject: RE: Doubt related to ROWID The best LIO there is! Other than not doing one at all.... :-) -----Original Message----- From: Jonathan Lewis [mailto:jonathan@xxxxxxxxxxxxxxxxxx] Sent: Wednesday, July 24, 2013 10:57 AM To: Ric Van Dyke; John.Hallas@xxxxxxxxxxxxxxxxxx; JSweetser@xxxxxxxx; ecandrietta@xxxxxxxxx; ORACLE-L Subject: Re: Doubt related to ROWID Slightly better even than "one LIO" - with the correct configuration (and a bit of luck, sometimes) it can be a "consistent get - examination", which is an LIO that requires only a single latch, and accesses the buffer while holding the latch rather than having to go through the whole pin cycle. -- //www.freelists.org/webpage/oracle-l