Re: shared_pool_reserved_size and sga

  • From: Tim Gorman <tim@xxxxxxxxx>
  • To: veeeraman@xxxxxxxxx
  • Date: Thu, 19 Aug 2010 15:11:27 -0600


On 8/19/2010 2:33 PM, Ram Raman wrote:
Hi
We have an application running on 10.2 with ASMM which was recently upgraded to a newer version of the application, still running 10.2. After the upgrade we got some errors related to shared pool. We tried flushing shared pool. The error would go away temporarily but would be back after a while. Last week we bumped up the shared_pool_reserved size to 260MB from the default size. It was ok for a while, but then we ran into errors with shared pool again, which prevented us from logging into the database. We had to bounce the instance. It seems ok for now. Is it alright to increase the SPRS further or do I have to worry about latch contention. Querying shared_pool_reserved view after the bounce an hour ago shows us that the request failures is 28. Our sga target is 4.5Gb now.
Thanks.
--
//www.freelists.org/webpage/oracle-l


Other related posts: