Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!gatech!udel!rochester!kodak!ektools!isctsse!brunjes
From: brunjes@isctsse.UUCP (Roy Brunjes)
Newsgroups: comp.databases
Subject: Re: Major data corruption in INGRES
Keywords: INGRES corruption
Message-ID: <178@isctsse.UUCP>
Date: 5 Apr 89 16:53:59 GMT
References: <22812@lll-winken.LLNL.GOV>
Sender: daemon@ektools (The Devil Himself)
Reply-To: brunjes@isctsse.UUCP (Roy Brunjes)
Organization: Eastman Kodak Telecommunication Services, Rochester, N.Y. 14650
Lines: 43

In article <22812@lll-winken.LLNL.GOV> manatt@lll-winken.LLNL.GOV (Doug Manatt) writes:
>
>     For the last 1.5 years we have been having problems with the
>reliability of the INGRES (rti, commercial) rdbms system.  The
>symptoms we have been experiencing are major corruption of the
>"backend" "system" tables and also corruption of index pages in
>btree table structures.  
>
>     I have tried to work this out with the rti tech support
>team, but so far, the response that I receive is that they are
>unable to duplicate my problems at their site.  
>
>     What I need to know from the net is whether others have
>similar experiences with their rdbms packages, and in particular
>what sort of support has been provided in similar situations.  We
>are reevaluating our use of ingres and if we can find a more
>reliable package we might think of switching.
>
>                         Doug Manatt
>                         manatt@lll-winken.llnl.gov
>                         (415) 422-7257

Sorry for posting this ... the email bounced (again)  8^(

Doug -- I have used Ingres since 1985 and have found it to be very reliable
for the project I have been working on (and in fact have heard of no
such problems in Kodak).  We have hit bumps in the road with Ingres
(no vendor's products excludes you from that pleasure!), but the RTI
folks have been very helpful.  We hit a problem that RTI couldn't
reproduce either, and in that case, they dialed in and found the
problem in a little over one day.  It turned out to be their problem
and they fixed it right away -- they had to cut a tape and Federal Express
it, but we were running in the meantime (limping more like it) and
within 2 days, things were fine.  Sorry that I can't say I have heard
of a similar problem here and we did xyz to fix it.  Your nearest RTI
sales person might be the one to turn up the heat in RTI to find the
problem.  Ours did that for us on one item (Sun OS 4.0 support) for
a Sun 4.  Does he/she understand the severity of the situation?

Roy Brunjes   If you dare try email:  ...rochester!kodak!kadsma!brunjes

Standard disclaimer applies:  My opinions, my thoughts, company in dark
about my thoughts and opinions, etc.