Re: The responsible

YAGRTDE (Yet Another Good Reason To Document Everything), or at least every time you change something from it's default/previous value. What works well with this version of the optimizer won't necessarily work well with a future version.

Just a thought but, that's something that might work well as part of an OUG conference/SIG presentation aimed at newbie/nearly-newbie (slightly worn?) DBAs. Although it's probably covered, in part, by the "Oracle Myths" presentation that (IIRC) Connor has delivered a few times.

Incidentally, it's worth remembering with those two parameters that they're both settable at the session level. So long as your app/tool supports it, if you've got a query that works best with radically different values for them than the rest of the app you can set them at session level before your query.

Stephen

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