Thanks Michael,

I'm on a very restricted time frame and opted for 9.2.0 and was able to
tweak it to the performance required.

Now I have another question.

I used to use the following to determine *who is logged in* but it no
longer works - I only get some of the records - any ideas???

#!/bin/sh
sql -s imadb <<EOF
select client_info, db_name
from ima_server_sessions
where client_info != ''
and db_name != 'imadb'
order by 1, 2
; \g
EOF


Regards,
Andy.


On 29/09/2010 3:57 PM, Michael Dyer wrote:

Hi Andy,



That SQL will work but will only return sessions in the DBMS you're
connected to. If you have more than 1 DBMS then you need to add



Execute procedure ima_set_vnode_domain;



Before the select. This will expand the "horizon" of what you can "see"
to all servers in the current instance of Ingres.



Regards

Paul



From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Andy
Sent: 30 September 2010 13:40
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Which version



Thanks Michael,

I'm on a very restricted time frame and opted for 9.2.0 and was able to
tweak it to the performance required.

Now I have another question.

I used to use the following to determine who is logged in but it no
longer works - I only get some of the records - any ideas???

#!/bin/sh
sql -s imadb <<EOF
select client_info, db_name
from ima_server_sessions
where client_info != ''
and db_name != 'imadb'
order by 1, 2
; \g
EOF


Regards,
Andy.


On 29/09/2010 3:57 PM, Michael Dyer wrote:

Assuming that you have a support contract (using II 9.2.1 with patch
13876 implies that you have), raise an issue with support.

Be ready to let them have output from running the inglogs script a
couple of time while the system is in the state where it has 'ground to
a halt'.



Inglogs can hang, as it uses iimonitor, which may hang if Ingres is
locked up.

If it does, then just abort it and provide the data that has been
produced. (A couple of times)



I routinely run both 32bit and 64bit II 9.2.1, as well as many other
versions, in SuSE 11.2.

It runs sweet and as fast as my hardware can be expected.



Michael

________________________________

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Andy
Sent: 29 September 2010 03:01
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Which version



Thanks Karl and Paul.

So, now I have installed Ingres 9.2.1(32bit) + p13876 on SuSE linux 11

Everything looks ok, OpenRoad 4.1 connects ok, runs the menus, a lot of
screens work fine, but...

When I try to run a program (to create a report) that does a bit of work
- some select loops, array processing, queries joining up to 6 tables -
nothing over the top, but it runs ok for about 30 seconds and then
grinds to almost a halt...

Looking in IPM, Lock List Display, showed nice progress for a little
while and then, for my single user, the Count dropped and the Status
showed SHARED. I have tried setting "set lockmode session where readlock
= nolock" in the ING_SET variable, tried an optimizedb, and sysmod.

I have not traced it down yet but I was wondering if there were any
out-of-the-box changes that other people do on 9.2.1?

Or should I have tried Ingres 9.2.0?

Regards,
Andy.


On 4/09/2010 12:51 AM, Paul Mason wrote:

10.0 is not GA yet so yes 9.2 is still the recommended version.
Depending on how close the upgrade is you might want to start testing
with the 10.0 beta.



HTH

Paul



From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Andy
Sent: 02 September 2010 00:36
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: [Info-Ingres] Which version



Hi All,

It was suggested awhile ago that I upgrade some of my clients versions
of Ingres to 9.2 (linux)...

That was awhile ago.

Should I still go to 9.2 or 10.? ?

Regards,
Andy.

Thanks Paul - worked well.

One more tick on the To-Do/To-Fix List.

Regards,
Andy


On 30/09/2010 10:55 PM, Paul Mason wrote: