Re: Monthly maintenance

"Lber" <lber_at_smartitc.co.uk> wrote in message news:8_i4h.49573$8Y7.10637_at_fe06.highwinds-media.phx...
> Hi thanks for the reply,
> by optimal i mean that the database is running as quick as it can, that
is
> kept in peak condition, so that uses do not complain that it slow to
> function etc.
>
> patching is not really an issue, as i have a test enviroment which is used
> to try out patches before deploying them, and this can take time. I'm not
> really worried about that.
>
> I'm just looking for a guide on good houskeeping for oracle i guess
>
> "Tom Churchward" <tcprof_at_tolan.fr> wrote in message
> news:u5d3l21fiu8bu8l26qtttdgq354vm281nr_at_4ax.com...
> > On Wed, 8 Nov 2006 10:25:03 -0000, "Lber" <lber_at_smartitc.co.uk> wrote:
> >
> >>Hi,
> >>I'm in the process of setting up an Oracle server.
> >>what sort of maintenance does Oracle need to keep it running at it's
> >>optimum
> >>levels?
> >>
> >>FYI it's an 8i server
> >>
> >>TIA
> >>
> >
> > I wonder if you could approach this from a different angle? What does
> > the Business you work for regard as optimal? They will have
> > priorities which perhaps aren't quite the same as yours. Taking a
> > crude example: if their priority is application/database available at
> > 9am each morning then you'd better make sure it is running at 9am each
> > morning - your business users might argue that the system is optimal
> > if it's available at 9am each morning....
> >
> > I guess the question wasn't really about this type of thing but it
> > might be worth asking them to define 'optimal' rather than using a
> > list of items such as, each logical I/O should take less that 10micro
> > seconds, each disk read less than, must keep up-to-date with patches
> > etc.
> >
> > Just a thought.
> >
> > Tom Churchwad
> >
> > http://tcprof.tolan.fr - The home of tcprof, an Oracle 10046 Trace
> > File Profiler.
>
>

Remember to set the _fast=true parameter. But seriously you need to define what is fast enough for what processes. You can always make it go faster by identifying what Oracle is waiting on and removing those bottlenecks, but it would be a never ending process. (yet fewer and fewer gains while costing more and more time and dinero to get those gains) Making Oracle go fast is dependent upon quite a few other things. Is the application written well? (eg in oltp app. use bind variables, use array interface) Is the hardware tuned and disk IO set up efficiently? Etc. Jim Received on Wed Nov 08 2006 - 06:59:40 CST