Re: Performance Monitoring strategies?

Starting to ....

AFAIK the RBs need to be big enough to hold the biggest transactions that can be going on ever

but this is not always a database problem and sometimes more to do with the app that is never committing.
(Although doing a big job in a single commit has a LOT of nice points )

Why not use OEM - email alerts and fixup jobs for anything you want

it does exactly what you described.. however arbitrarily increasing RBs size is a fix -the -symptom -not- the- problem thing.

just my 0.05c
"Ryan Gaffuri" <rgaffuri_at_cox.net> wrote in message news:1efdad5b.0206120750.716cbe60_at_posting.google.com...
> We often have problems with rollback segments blowing up. Our DBA then
> needs to go in and essentially increase their size. I know enough
> about being a DBA(which is not much) to know that this probably isnt
> the best way to go about things.
>
> We are not using any GUI tools(such as the OEM)... In your experience
> how have you monitored these kinds of things? My assumption is to have
> jobs run every 2 hours? or so that hit the data dictionary and then I
> would assume insert the results into some tables. Then have some
> queries hit those tables analyzing them for possible issues that may
> arise soon. Then have an alert sent out if they pass some limit.
>
> Am I going in the right direction?
>
> Ryan
Received on Wed Jun 12 2002 - 11:54:07 CDT