The likelyhood that the size of the shared pool is his problem is slim to
none. The shared pool will effect a lot of things related to overall
performance of the system, but it's impact on a single query is slim. You
don't change the shared pool unless there is an indication after using
utlbstat and utlestat. You then look at your library cache to verify that
you are having a low hit ratio in your library or dictionary cache. The
first thing that I would really suggest is analyze all tables being
referenced in the query, and then I would look at tuning with hints.
--
Robert Fazio, Oracle DBA
rfazio_at_home.com
remove nospam from reply address
http://24.8.218.197/
"Kiran Samvedi" <kiran1_at_starhub.net.sg> wrote in message
news:39377bd8.0_at_news.cyberway.com.sg...
> Hi,
> Try Increasing the shared_pool_size.
> ..Kiran
>
> "Deborah Carter" <dcarter_at_cnfei.com> wrote in message
> news:j4xZ4.753$RT3.1291009_at_firenze.visi.net...
> > I am working on this project writing a procedure to select information
out
> > of some rather large tables and insert them into another table. The
> > procedure runs for about 6-8 minutes. How can I improve this
performance?
> > I believe my select statements are optimized. I just don't know what
else
> > to check or do to speed up the performance. The query takes so long. I
was
> > thinking about reorganizing the largest tables as index-organized
tables.
> > How will this effect performance? What are the drawbacks to
index-organized
> > tables? Any suggestions are appreciated.
> >
> > Deborah Carter
> >
> >
>
>
Received on Fri Jun 02 2000 - 00:00:00 CDT
