Hi, guys. We were getting killed on SAP, when checking locks, after we upgraded to 9.2 One of the other DBAs came up with this and it was a dramatic improvement. Not sure if he got it from metalink or? We just upgraded a 8.1.6 database to 9.2 and had the same problem. This fixed it. He also had this comment "Has anyone tried selecting a particular extent out of dba_extents, on the SAP systems I'm seeing horrendous performance" Are there any other views that we should be replacing? Thanks Larry drop view v_$lock; drop public synonym v$lock; create or replace view v_$lock as select /*+ rule */ l.laddr as addr ,l.kaddr as kaddr ,s.ksusenum as sid ,r.ksqrsidt as type ,r.ksqrsid1 as id1 ,r.ksqrsid2 as id2 ,l.lmode as lmode ,l.request as request ,l.ctime as ctime ,l.block as block from v$_lock l ,x$ksuse s ,x$ksqrs r where l.saddr=s.addr and l.raddr=r.addr ; create public synonym v$lock for v_$lock; ********************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. ---------------------------------------------------------------- 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 -----------------------------------------------------------------