If you have objections against the application you bought - request
supplier to fix it (you paid for it, and probably paid a lot) or do it
yourself - stored outlines may be of help to fix misbehaving queries
and cursor_sharing may help fixing lack of bind variables (but may
break something else along the way...), and there a lot of other things
you, as DBA, can fix before resorting to physical storage. And if the
application is written so poorly it can't be optimized without major
rewrite - playing with physical storage won't help you anyway.
My $.02
--
Vladimir Zakharychev (bob@dpsp-yes.com) http://www.dpsp-yes.com
Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications.
All opinions are mine and do not necessarily go in line with those of my employer.
"Sybrand Bakker" <gooiditweg_at_sybrandb.demon.nl> wrote in message
news:13dhoukmgbno77ggm2k4maf96j55hb0oro_at_4ax.com...
> On Wed, 18 Sep 2002 14:30:23 +0400, "Vladimir M. Zakharychev"
> <bob_at_dpsp-yes.com> wrote:
>
> >Still, if you don't have obvious I/O bottlenecks in your system - leave it be
> >and concentrate on tuning your applications.
>
>
> So what if the application has been bought?
>
> Regards
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
Received on Thu Sep 19 2002 - 03:28:56 CDT
