Re: How to cleanup "obj stat memory" component in Shared Pool
- From: Maclean Liu <maclean_007@xxxxxxx>
- To: yong321 <yong321@xxxxxxxxx>
- Date: Mon, 24 May 2010 23:23:19 +0800
Hello Yong,
I believe that setting hidden parameter will fix this error. I just wonder
if any other better method.
Oracle support always provide a workaround solution ,it's acceptable.
Bus as a researcher rather than DBA , i am glad to receive various
solutions.
2010/5/24 Yong Huang <yong321@xxxxxxxxx>
> large memory usage in shared pool, especially the "obj stat
> > memo". Recently they encountered the error 4031 ,
> ...
> > I have read the metalink note "Bug 5573238 Shared pool memory
> > use / ORA-4031 due to "obj stat memo" in one subpool", oracle
> > support advise to workaround this problem by setting
> > STATISTICS_LEVEL=BASIC or _object_statistics"=false.
> > But i am not satisfied with this solution.
> ...
> > So i wonder if there is are events or other method to cleanup
> > obj stat memory in shared pool ?
>
> Bug 5573238 is actually a very sensible report. Unless you use
> v$segstat or v$segment_statistics often, the suggestion of
> setting "_object_statistics" to false is a good one (setting
> statistics_level to basic has a lot of consequences). Why are you
> not satisfied with the suggestion? You didn't say your version.
> The bug description note 5573238.8 says it's fixed in 10.2.0.4.
>
> The bug says the allocated memory is permanent. I doubt there's
> a way to clean it up. Just set the underscore parameter and
> bounce the instance. If you use alter system to set it now, the
> "obj stat memo" will stop growing but won't shrink.
>
> Yong Huang
>
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
> 网易为中小企业免费提供企业邮箱（自主域名）
>
>
>
--
Maclean Liu
Oracle Database Administrator
Oracle Certified Master
http://www.youyus.com
--
Maclean Liu
Oracle Database Administrator
Oracle Certified Master
http://www.youyus.com
Other related posts:
