Re: ORACLE RAC CRASHES ORBITZ

From: Blair Adamache <badamache_at_2muchspam.yahoo.com>
Date: Mon, 28 Jul 2003 13:39:40 -0400
Message-ID: <bg3n1g$jap$1@hanover.torolab.ibm.com>

It's possible that DB2, Informix, Sybase and 'C' compilers have all caused crashes. Never heard of a C compiler crash that interrupted production and got the same level of coverage as Orbitz did in eWeek and Computerworld. I guess when you buy the back page of the Economist and Businessweek and use the word "Unbreakable", you attract a little more attention - the same way a blivet attracts flies.

Daniel Morgan wrote:

> Mark A wrote:
>
>

>>>>Tom Longfellow wrote:
>>>>
>>>>
>>>>>GOD!! sometimes I just HATE the internet.  It is  too easy to be
>>>>>misinterpreted.   My suggestions were tongue in cheek.   I TOTALLY get
>>>>>marketing.  I was just commenting on how marketing departments can
>>>>>embarrass their companies.
>>>>>
>>>>><snipped>
>>>>
>>>>This is why emoticons were invented.   ;-)
>>>>
>>>>Sorry if I didn't see your tongue planted firmly in your cheek.
>>>>
>>>>Unfortunately PT Barnum was correct. And we will be dealing with the
>>
>>effluent
>>
>>>>of marketing departments right up until customers use their own brains
>>
>>and stop
>>
>>>>buying the drivel they produce. And that will not be in our lifetimes.
>>>
>>>Just a rumor mind you, but the Orbitz glitch has been traced to some
>>>hardware issues...will post more if I hear more.
>>>
>>>Mike
>>
>>Yes, it will turn out to be a hardware problem even if Larry Ellison has to
>>buy the hardware company and then have the hardware company accept the
>>blame.

>
>
> What a blivet.
>
> In an environment as complex as Orbitz's a crash could be caused by many things.
> Hardware, operating systems, networks, routers, hubs, databases, tools, etc.
> etc. etc. right down to a poorly run code review on some internally generated
> program or a DBA or SysAdmin that made an innocent mistake.
>
> But you are so knee-jerk negative toward Larry, who I doubt has ever taken a
> single dollar from your pocket, you jump to a conclusion the size of Mt.
> Everest. Give it a break.
>
> As Freud once said ... "Sometimes a cigar is just a cigar."
>
> Do the universe a favor. Wait for the facts to come out: They will. Then comment
> on the facts. If they demonstrate Oracle was responsible so what. Has DB2 never
> been responsible for a crash? Informix? Sybase? A 'C' compiler?
> --
> Daniel Morgan
> http://www.outreach.washington.edu/extinfo/certprog/oad/oad_crs.asp
> damorgan_at_x.washington.edu
> (replace 'x' with a 'u' to reply)
>
>
Received on Mon Jul 28 2003 - 12:39:40 CDT