Re: 1 minutes: best downtime story
- From: Laimutis.Nedzinskas@xxxxxx
- To: oracle-l <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 15 Mar 2013 08:42:46 +0200
A small but major database (a central hub) could not be accessed. That's a
story of chain reaction.
SUN Solaris and ldap integration glitch caused all user related operations
like sudo to cease for some minutes. Veritas cluster resource check script
(custom made) could not sudo and returned error. Veritas cluster brought
down Virtual IP assigned to the active database node. The database serving
as a central node effectively stopped all operations of the institution,
though the database itself was perfectly alive.
---------------------------------------------------------------------------------
Please consider the environment before printing this e-mail
From: Jeremy Schneider <jeremy.schneider@xxxxxxxxxxxxxx>
To: oracle-l <oracle-l@xxxxxxxxxxxxx>
Date: 2013.03.14 23:09
Subject: 1 minutes: best downtime story
Hey all -
I'm writing a paper about top causes of downtime. As one component
of research, I'd like to get some input from you!
One minute, two sentences. First sentence: describe what went down.
Second sentence: describe why. (I have to categorize all of these.)
Everyone should have at least one downtime story so I'm hoping for a
lot of feedback!
Answer about any technology - database, operating system, etc.
Thanks!
-Jeremy
--
Jeremy Schneider
Pythian Consulting Group
Chicago
+1 312-725-9249
http://www.pythian.com
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
