Re: high cpu on query

Hi,

as already mentioned ...

8) new hard parse with a different peeked value (histogram or partiton/subpartion statistics)

I guess this is not the final point.

regards,

Jaromir D.B. Nemec

• Original Message ----- From: Jeremy Paul Schneider To: Cary Millsap Cc: joseph.armstrong-champ_at_tufts.edu ; ORACLE-L Sent: Friday, June 29, 2007 10:55 PM Subject: Re: high cpu on query

  Don't forget SQL profiles... maybe those were lumped in with stored outlines though. This could be a useful list - is there anything else or is this it?    

1. change in text of sql (including hints)
2. change in init or session params
3. change in object stats (tables stats or index stats, also histograms)
4. change in system stats
5. Change in schema (create/drop indexes, partition/cluster/parallelism declarations, etc.)
6. Stored outline or SQL profile manipulation
7. Oracle CBO code change (e.g., upgrade or patch)

--
http://www.freelists.org/webpage/oracle-l