RE: Source of expensive SQL

Nice idea, but no.

Index monitoring is not turned on.

Ray  

From: Bobak, Mark [mailto:Mark.Bobak_at_il.proquest.com] Sent: Friday, January 06, 2006 9:57 AM
To: ray_at_seertechsolutions.com; oracle-l_at_freelists.org Subject: RE: Source of expensive SQL  

Just a guess.....do you have index monitoring turned on...?  

-- 
Mark J. Bobak 
Senior Oracle Architect 
ProQuest Information & Learning 

"There are 10 types of people in the world:  Those who understand binary,
and those who don't." 

 

 



  _____  


From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of Ray Feighery
Sent: Thursday, January 05, 2006 5:52 PM
To: oracle-l_at_freelists.org
Subject: Source of expensive SQL

Hello

 

Solaris 8

Oracle 9.2.0.4

 

The following piece of SQL is popping up in STATSPACK reports as expensive.
It runs about once an hour. I can see that it is executed as the SYS user,
but I don't know what is causing it to run.

Any ideas what the source of this is?

 

select      i.obj#, i.flags, u.name, o.name

from        sys.obj$ o, sys.user$ u, sys.ind$ i

where       (bitand(i.flags, 256) = 256 or bitand(i.flags, 512) = 512) 

and         (not((i.type# = 9) and bitand(i.flags,8) = 8)) 

and         o.obj#=i.obj# 

and         o.owner# = u.user#

Ray