sathya | 11 Jan 2005 18:34
Favicon

INGRES R3 . If you plan to use Ingres please read this

Folks,
Before putting Ingres R3 into production please make sure you can get 
support for it.
We went live on a major implementation using zope 2.7.3 ZEO  and Ingres 
R3 (int109) on RedHat AS 3.0  for a large customer (TPA with 200,000 lives)
It has been a nightmare. The memory leaks in the ingres Python DBI are 
just the beginning. We fixed a few and submitted patches
On the DB server
we see the following in the log file
Memory corruption errors
Segvs

iowait hits 100 % and  system comes to a grinding stop.

It could be our code (which worked well on postgres) but I am  inclined 
to think its not  the main cause

We of course contacted CA for support  and spent 4 days to learn that 
they are just getting the system in  to take support calls and sell 
support on R3.
The last time we had an issue  with postgres a guy from command prompt  
inc logged  in within 30 minutes and fixed our problem.

Since Ingres Plone and APE have some things in common I thought I should 
post this on this forum. Your experience may be different  and
the above is just FYI . I hope things get better in the days ahead.

Regards
Sathya

(Continue reading)

Chris Withers | 12 Jan 2005 23:18
Picon

Re: INGRES R3 . If you plan to use Ingres please read this

sathya wrote:
> Since Ingres Plone and APE have some things in common I thought I should 
> post this on this forum. Your experience may be different  and
> the above is just FYI . I hope things get better in the days ahead.

Out of interest, where are APE and Ingres's python support downloadable 
from?

cheers,

Chris

--

-- 
Simplistix - Content Management, Zope & Python Consulting
            - http://www.simplistix.co.uk
_______________________________________________
Zope-Dev maillist  -  Zope-Dev <at> zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

sam | 13 Jan 2005 09:07
Favicon

Re: [Zope-dev] INGRES R3 . If you plan to use Ingres please read this

http://opensource.ca.com/projects/

Chris Withers wrote:

> sathya wrote:
>
>> Since Ingres Plone and APE have some things in common I thought I 
>> should post this on this forum. Your experience may be different  and
>> the above is just FYI . I hope things get better in the days ahead.
>
>
> Out of interest, where are APE and Ingres's python support 
> downloadable from?
>
> cheers,
>
> Chris
>

--

-- 
=========================
ZeOmega
Open Minds' Open Solutions

Plano Tx
972-731-6750 (o)
214-733-3467 (M)
http://www.zeomega.com
==========================

(Continue reading)

sathya | 13 Jan 2005 09:08
Favicon

Re: INGRES R3 . If you plan to use Ingres please read this

http://opensource.ca.com/projects/

Chris Withers wrote:

> sathya wrote:
>
>> Since Ingres Plone and APE have some things in common I thought I 
>> should post this on this forum. Your experience may be different  and
>> the above is just FYI . I hope things get better in the days ahead.
>
>
> Out of interest, where are APE and Ingres's python support 
> downloadable from?
>
> cheers,
>
> Chris
>

_______________________________________________
Zope-Dev maillist  -  Zope-Dev <at> zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

Bruce Lunsford | 14 Jan 2005 18:28
Favicon

Re: INGRES R3 . If you plan to use Ingres please read this

sathya <zope2 <at> zeomega.com> writes:

> 
> Folks,
> Before putting Ingres R3 into production please make sure you can get 
> support for it.
> We went live on a major implementation using zope 2.7.3 ZEO  and Ingres 
> R3 (int109) on RedHat AS 3.0  for a large customer (TPA with 200,000 lives)
> It has been a nightmare. The memory leaks in the ingres Python DBI are 
> just the beginning. We fixed a few and submitted patches
> On the DB server
> we see the following in the log file
> Memory corruption errors
> Segvs
> 
> iowait hits 100 % and  system comes to a grinding stop.
> 
> It could be our code (which worked well on postgres) but I am  inclined 
> to think its not  the main cause
> 
> We of course contacted CA for support  and spent 4 days to learn that 
> they are just getting the system in  to take support calls and sell 
> support on R3.
> The last time we had an issue  with postgres a guy from command prompt  
> inc logged  in within 30 minutes and fixed our problem.
> 
> Since Ingres Plone and APE have some things in common I thought I should 
> post this on this forum. Your experience may be different  and
> the above is just FYI . I hope things get better in the days ahead.
> 
(Continue reading)


Gmane