We have been having some heavy discussions about
system failures, root cause analysis and developing
some proactive metrics. Generally, our problems
revolve around frequently late nights for the On Call
DBA because something out of our control goes wrong.
The damagement folks want to fix the
Peter - I can see your desires going in two directions:
1. Operational procedures - Things like how do I know I'm running out of
disk space before I've run out.
2. Change management. Most failures come from changes to the software. Like
somebody adds some programs and that affects other
-- Peter Barnett [EMAIL PROTECTED]
We have been having some heavy discussions about
system failures, root cause analysis and developing
some proactive metrics. Generally, our problems
revolve around frequently late nights for the On Call
DBA because something out of our control goes
Hello Peter
A good source if the calls themselves.
After each call analyze the root cause and start checking for it.
This way you will be able in a short time to eliminate a lot of problems.
Yechiel Adar
Mehish
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL
=
Steven Lembark [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
01-05-2002 02:44 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Fax to:
Subject:Re: Root Cause Analysis White Papers
-- Peter Barnett
