You don't specify the version, since 11g you can access alertlog information through the database. If you have access to the V$% views, v$diag_problem lists all problems defined by the ADR. The v$diag_info view has the number of active problems. Perhaps the shared pool fragmentation error that you allude to can be traced that way? Cheers, Tony On 23/04/13 06:14, Dba DBA wrote: > Some constraints since another company has the operations contract. No > access to alert log. No access to SYS. So no x$tables. I also can't turn > get an audit option turned on to audit for errors (not sure if shared pool > errors would get caught anyway). > I found a good article here on it, but it hits alot of x$tables. I know how > to tell if we have queries that don't use bind variables. Found some, but I > am not sure how to tell if the shared pool fragmentation error got thrown > with my limited access. I have access to the data dictionary views. > > http://coskan.wordpress.com/2007/09/14/what-i-learned-about-shared-pool-management/ > > > -- > //www.freelists.org/webpage/oracle-l > > > -- //www.freelists.org/webpage/oracle-l