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 immediate problem and consider the job done. The DBAs are asking for an approach that will allow us to identify potential problems before something breaks at 3:00 a.m.
Does anyone know of a source of white papers or other data that has been generated for systems, storage or databases? We can always roll out own, but why recreate someone else's work. ===== Pete Barnett Lead Database Administrator The Regence Group [EMAIL PROTECTED] __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Peter Barnett INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
