I've been having a play with runbuild.sh and trying to get it to work on
Ubuntu (which I'll be raising a ticket for shortly)
I think runbuild.sh is great - you can basically now download the source and
run one script to build ingres without any setting of environments variables

By popular request, I have created a #ingres channel on
irc.freenode.net. I invite you to join me in the channel.
You can do so with any number of IRC clients (including free ones) as
well as a number of web sites offering free access.

Happy easter all.
I think I am missing something.
I'm trying to configure ingres for failover on a solaris cluster.
I've got the basic Ingres2006R2 installation going on the shared disk array.

I use, Ingres 2006 R2 (for Linux) v 9.1.0 on RHEL 5.0.
I created a database called test. When I try to create a table without
a primary key, it creates without any hassles. But, when I create a
table with a primary key, it throws the following error:

Did anyone realise that you cant raise an error from within an OME
external lenspec routine? I didn't and now I'll be spending this evening
fixing the fixes I installed on my last set of functions.
If an error is raised the program will crash out of the server and

Can someone point me in the right direction...
I've using the .net 2.0 data provider from visual studio 2005
I can connect successfully using the ingres userid. The host server has
DAS running.

I am using the Ingres .Net data provider to connect to an Ingres
database from a C#. Net application, but I am finding that even for a
simple select I am getting table level locks created on every database
table I use in my query.

All
I'm going to unloaddb on Ingres 2.0 and then reload into Ingres 2006
I have an open road 3.5 app, could I point that at Ingres 2006 without
any issues?

I thought the group might enjoy the following article re-posted on
"Daily WTF, titled "Jurassic Programmers"
<http://thedailywtf.com/Articles/Jurassic-Programmers-.aspx>.
I found the parallels between criticisms of highly-functional ABF/INGRES

Hi Larry,
Our L2 team just told me  that Icebreaker's update to SP1 is in progress.
It might take one week more on QA process.
I'll let you know where it gets available.

In my role as chair of the UK Ingres Users Association I have been contacted
by a recruiter looking for 7 Ingres people.  Here's the text of their
requirement:
"The roles are working for EDS Defence for their Defence Logisitics

The way CP flushing is done has changed repeatedly over the years.  Way back
in the bad old days, a consistency point flush used to stall the server.
Also, the WB threads used to help out with CP flushes.  Later the behaviour
was changed so that CP flushes no longer stall the ...

Thanks Grant
Your suggestion helped and worked.
In order to enable connecting to the remote node we had to undefine the
local logical. If we left it we would still connect only to the local node.

We use an older version of Ingres ( II 2.0/0011 ) on VMS.
We have set up netutil in a way that I of our servers can access another
1, serving as local & remote.
Our database , lets say is called MYDB, so now we can access the

It seems trace point OP188 is broken in Ingres 9.2.0.  It no longer reports
the query plan numbers.
Since it is an undocumented feature (albeit a virtually indispensible one) I
don't think I can really log it as a support issue.   If there are any