Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ub!canisius!pavlov
From: pavlov@canisius.UUCP (Greg Pavlov)
Newsgroups: comp.databases
Subject: Re: INGRES/NET, DEC RISC
Message-ID: <3120@canisius.UUCP>
Date: 10 Jan 91 07:32:48 GMT
References: <49311@seismo.CSS.GOV>
Distribution: usa
Organization: Canisius College, Buffalo N.Y. 14208
Lines: 25

In article <49311@seismo.CSS.GOV>, jean@beno.CSS.GOV (Jean Anderson) writes:
> In <3113@canisius.UUCP>, pavlov@canisius.UUCP (Greg Pavlov) writes
>> After months of struggle with the destructive 6.2 INGRES,we achieved Nirvana:
>> a 6.3 release tape.  It does appear to be better-behaved but that may only be
>> because of a new problem: our client machines can no longer talk to our
>> server. ....
> 
> Are you in a heterogeneous environment? and did you upgrade to Ultrix 4 at 
> the same time?...... 

  We have a heterogeneous envrionment, but we are running INGRES only on DEC
  RISC systems.  We were running INGRES 4.0 prior to installing INGRES 6.3.

  .... INGRES informed us that we are seeing the effects of a bug, to be fixed
  and distributed in the next release in February (????).  Since this wouldn't
  do at all for our user population (they've been waiting on a reasonably stable
  database for many moons now...), our system administrator attempted a "desper-
  ation fix" which, for some reason, did the trick: he modified the ULTRIX con-
  fig file to indicate that DECnet is to be installed.

  Not sure why this worked: we run TCP/IP and do not have either licenses or
  the ability to actually enable DECnet in either ULTRIX or INGRES....

  greg pavlov, fstrf, amherst, ny
  pavlov@stewart.fstrf.org