Can you trace the sessions involved and compare the parse and execute times? Any real role overhead would have to be on the parse side of things. If the parse component is the same for the two queries, there is probably something else going on, i.e. data is cached when the second query runs. Justin Cave Distributed Database Consulting, Inc. http://www.ddbcinc.com/askDDBC -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Larry Hahn Sent: Tuesday, April 27, 2004 11:32 AM To: Oracle-L@xxxxxxxxxxxxx Subject: Overhead using a role Is there much overhead involved in using roles? I have a query that runs about 4 minutes using the schema owner account. The same query runs about 50% longer using a userid that is attached to a role that has read any table rights.=20 I did an Explain Plan on both, but they are exactly the same. We are running under RBO. The database is 8.1.7.3 running on Sun Solaris. Thanks for any light anyone can shed on this. Larry =09 =09 __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover ---------------------------------------------------------------- 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 ----------------------------------------------------------------- ---------------------------------------------------------------- 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 -----------------------------------------------------------------