RE: The responsible

  • From: "Mike Killough" <mwkillough@xxxxxxxxxxx>
  • To: juancarlosreyesp@xxxxxxxxx, oracle-l@xxxxxxxxxxxxx, jonathan@xxxxxxxxxxxxxxxxxx
  • Date: Tue, 07 Feb 2006 11:06:47 -0600

This is why I always set the parameters generic in test and force them to reprove their need, before including them in the upgrade.

Mike



From: Juan Carlos Reyes Pacheco <juancarlosreyesp@xxxxxxxxx>
Reply-To: juancarlosreyesp@xxxxxxxxx
To: oracle-l@xxxxxxxxxxxxx, jonathan@xxxxxxxxxxxxxxxxxx
Subject: The responsible
Date: Tue, 7 Feb 2006 12:46:54 -0400

HI I want to share this info, not asking.

Some years ago I changed the optimizer parameters, and this solved a query,
from minutes to seconds
OPTIMIZER_INDEX_COST_ADJ = 10
OPTIMIZER_INDEX_CACHING = 90
Now the situation reversed, and I had to comment them
To move a process from 4 minutes to 7 seconds.

using optimizer parameters 10,90
trace file 870 M
time 4 minutes (without trace)
recursive 465.43 s
non recursive 233.21 s


commenting optimizer parameters and leaving with their defaults Trace file 6 M time 7 seconds recursive 5.87 s non recursive 1.79 s






-- Oracle Certified Profesional 9i 10g Orace Certified Professional Developer 6i

8 years of experience in Oracle 7,8i,9i,10g and developer 6i


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


Other related posts: