Re: High shared pool usage
- From: Laimutis.Nedzinskas@xxxxxx
- To: oracle-l@xxxxxxxxxxxxx
- Date: Mon, 3 Oct 2011 08:44:38 +0300
>What I usually do is keep running a DDL, such as grant select
to dba, on the said table during the period of those inserts. The
memory used by the SQLs will be released.
funny enough :) Do you know pool mechanics behind that behaviour ?
>> insert into table t001; insert into table t002 ...
>That's actually quite common.
didn't know that :))) Sounds like some tool or method is behind it.
Probably good for monitoring of ETL progress... A good way to torture
oracle too.
brgds, Laimis N
---------------------------------------------------------------------------------
Please consider the environment before printing this e-mail
From: Yong Huang <yong321@xxxxxxxxx>
To: Laimutis.Nedzinskas@xxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Date: 2011.10.02 22:08
Subject: Re: High shared pool usage
> I've seen a case when each insert of some ETL generated a new sql.
> There was no way to handle it with cursor_sharing options: the
> guys(developers) decided to use a new alias for each insert:
> insert into table t001; insert into table t002 ...
That's actually quite common. There's no good solution from the DBA
side. What I usually do is keep running a DDL, such as grant select
to dba, on the said table during the period of those inserts. The
memory used by the SQLs will be released. 11g doesn't do that though,
and dbms_shared_pool.purge on individual SQLs has to be used.
Yong Huang
--
//www.freelists.org/webpage/oracle-l
Other related posts:
