optimizer parameters
- From: "ed lewis" <eglewis71@xxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Sun, 24 Apr 2011 08:22:51 -0400
Hi,
I'm curious what other peoples's experience, suggestions
are in regard to the use of the "optimizer_index_caching", and
"optimizer_index_cost_adj" parameters.
As a general practice, I leave them at their defaults, unIess
the vendor specifically requires that they be modifed. I use
system statistics instead. I haven't find the need to do otherwise.
I've tested these parameters on queries, and have received various results.
In some cases, it made use of an index, and in other cases,
it had no impact.
I'm not a fan of changing this in midstream for an app
that has been running for almost 2 years. This particular vendor
is asking to modify this, as a possible solution to a slow-running
query. I'm pushing back, and would rather address this in other
ways, such as tracing the query, and go from there.
Your input is appreciated.
ed
oracle 10.2.0.4
solaris 10
rac, asm 10.2.0.4
Other related posts:
