Is it recommened to flush shared pool after taking statistics??

Question

Hi, all.
The database is 2 node RAC 10.2.0.2.0 on 32-bit windows 2003 EE SP1.
I stoped the default statistics-gathering-job of GATHER_STATS_JOB
because it takes statistics of all objects in database and it runs everyday.
In addition, it seems to cause "library cache related" wait events in a RAC
environment.
I have a plan to take statistics of ONLY an application schema, not all objects
of a database, by using GATHER_SCHEMA_STATS procedure.
Is it recommended to flush shared pool after taking statistics of an application
schema??
Thanks and Regards.

Answer 1

Is it recommended to flush shared pool after taking
statistics of an application
schema??neednt cause whenever you gather stats either its system or not oracle age out the plan and regenerate the new plan on the basis of new gathered stats,see how oracle is smart.
SQL> create table t as select rownum a,object_name
  2    from all_objects
  3  /
Table created. 
SQL> alter system flush shared_pool
  2  /
System altered.
SQL> alter session set sql_trace=true
  2  /
Session altered.
SQL> declare
  2   va  t.a%type;
  3  begin
  4   for i in 1..100
  5   loop
  6    execute immediate 'analyze table t compute system statistics';
  7    select a into va
  8      from t
  9     where a=i;
10   end loop;
11  end;
12  /
PL/SQL procedure successfully completed.
SELECT a from t
   where a=:b1
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute    100      0.12       0.11          0          0          0           0
Fetch      100      0.26       0.32          0      11800          0         100
total      201      0.39       0.44          0      11800          0         100
Misses in library cache during parse: 1
Misses in library cache during execute: 99
Optimizer goal: CHOOSE
Parsing user id: 59     (recursive depth: 1)
Rows     Row Source Operation
      1  TABLE ACCESS FULL T
Misses in library cache during execute: 99 shows you aging out the plan after every gathering stats.
Khurram