Hi group,

Is there any way to list the sessions currently connected to an Ingres
installation that connected via the Ingres Data Access server (iigcd)?

Cheers,

Martin

You can do this with iimonitor, you need to know the port number (Name
in IPM Server list)

iimonitor xxxxx

iimonitor>show user sessions

or

iimonitor>show user sessions formatted

I'm hoping that a future version of IPM will be able to show sessions.

Jeremy


--
jruffer

On Windows servers I use
netstat | find "21071"
for that.

(21071 is the iigcd standard port)

HTH
Gerhard


--
gerhard.hofmann (AT) planat (DOT) de
------------------------------------------------------------------------
gerhard.hofmann (AT) planat (DOT) de's Profile: http://community.actian.com/forum/member.php?userid=857
View this thread: http://community.actian.com/forum/sh...ad.php?t=14065

Hi Martin,

Here is an example using command line tools in Linux. Similar results with
Windows but the server IDs will be something like this. xx\ingres\abc


1. Check the process id of iigcd

[ingres@pitingrestemp ~]$ ps -ef|grep iigcd
ingres 5551 1 0 Oct04 tty1 00:00:50
/data1/Ingres/IngresII/ingres/bin/iigcd II gcd
ingres 22085 21968 0 23:00 pts/0 00:00:00 grep iigcd
[ingres@pitingrestemp ~]$


2. Get a listing of sessions which are linked to that process ID
see this link for copy of iisess tool
http://community.actian.com/w/index.php/Iisess


[ingres@pitingrestemp ~]$ iisess -c

======Server : 55003 \c

B7EA8C00:2395597712 ingres imadb batch CS_EVENT_WAIT
Conn : ingresitingrestempitingrestemp:5567:imadb/ingres
8DFD0100:2382162832 ingres imadb batch CS_EVENT_WAIT
Conn : ingresitingrestempitingrestemp:5567:imadb/ingres

[some lines removed. These sessions are linked to DAS]

80B600C0:2344520592 ingres logistic2006 batch CS_EVENT_WAIT
Conn : ingresitingrestempitingrestemp:5551:logistic20 06
80BA4100:2350140304 ingres logistic2006 batch CS_EVENT_WAIT
Conn : ingresitingrestempitingrestemp:5551:logistic20 06
81ABDE20:2173705104 ingres logistic2006 batch CS_EVENT_WAIT
Conn : ingresitingrestempitingrestemp:5551:logistic20 06
82BF9B60:2365995920 ingres logistic2006 batch CS_EVENT_WAIT
Conn : ingresitingrestempitingrestemp:5551:logistic20 06
82C7C100:2379684752 ingres batch CS_COMPUTABLE ty: (Monitor
Session
Conn :
30 Sessions
[ingres@pitingrestemp ~]$


Or do it the hard way.

[ingres@pitingrestemp ~]$ iinamu
Ingres NAME SERVICE MANAGEMENT UTILITY --
-- Copyright (c) 2004 Ingres Corporation
IINAMU> show
INGRES * 55003 (sole server)
IINAMU> quit
[ingres@pitingrestemp ~]$ iimonitor 55003
IIMONITOR> show sessions
Session B7EA8C00:2395597712 (ingres ) cs_state:
CS_EVENT_WAIT (BIOR) cs_mask: CS_INTERRUPT_MASK,CS_NOXACT_MASK OS_
tid: 5568
Session 8DFD0100:2382162832 (ingres ) cs_state:
CS_EVENT_WAIT (BIOR) cs_mask: CS_INTERRUPT_MASK OS_tid: 5569

[these are the ones]

Session 82BD0100:2365193104 (ingres ) cs_state:
CS_EVENT_WAIT (BIOR) cs_mask: CS_INTERRUPT_MASK,CS_NOXACT_MASK OS_
tid: 21944
Session 80B600C0:2344520592 (ingres ) cs_state:
CS_EVENT_WAIT (BIOR) cs_mask: CS_INTERRUPT_MASK,CS_NOXACT_MASK OS_
tid: 22055
Session 80BA4100:2350140304 (ingres ) cs_state:
CS_EVENT_WAIT (BIOR) cs_mask: CS_INTERRUPT_MASK,CS_NOXACT_MASK OS_
tid: 22057
Session 81ABDE20:2173705104 (ingres ) cs_state:
CS_COMPUTABLE cs_mask: OS_tid: 22083

[Note the process ID below]

IIMONITOR> format 80BA4100
)
User: ingres (ingres
)
User Name at Session Startup: ingres
Terminal: batch
Group Id:
Role Id:
Application Code: 00000000 Current Facility: CLF (00000001)
Client user: ingres
Client host: pitingrestemp
Client tty: pitingrestemp
Client pid: 5551
Client connection target: logistic2006
Client information:
user='ingres',host='pitingrestemp',tty='pitingrest emp',pid=5551,conn='logist
ic2006'
Description:
Query:
Last Query: SELECT originator_id, name, auth_group_id, default_dept_id
FROM originator WHERE originator = 'paul' and password = 'print12'
IIMONITOR> quit



3. You can connect directly to DAS and manage sessions there.
This tells you the location of the .Net client. In this case it is the web
server.


[ingres@pitingrestemp ~]$ iinamu
Ingres NAME SERVICE MANAGEMENT UTILITY --
-- Copyright (c) 2004 Ingres Corporation
IINAMU> show dasvr
DASVR * 59637
IINAMU> quit
[ingres@pitingrestemp ~]$ iimonitor 59637
IIMONITOR> show user sessions
Session 9889ba0:3 (srprod ) Type: USER state: WAIT i/o:
CLIENT
IIMONITOR> format 9889ba0
Database: srprod
Connection type: Remote
Client username: NETWORK SERVICE, host: peercoresvr01.peercore.local,
address: 10.10.10.17
Network protocol: TCP_IP, node: , port:
IIMONITOR> remove 9889ba0
Pool session(s) removed
IIMONITOR>

IIMONITOR> quit
[ingres@pitingrestemp ~]$


-----Original Message-----
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Martin
Crouch
Sent: Wednesday, 16 November 2011 9:07 PM
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: [Info-Ingres] Is there any way...

Hi group,

Is there any way to list the sessions currently connected to an Ingres
installation that connected via the Ingres Data Access server (iigcd)?

Cheers,

Martin
_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres

Also this query in imadb seems to work ok:
select * from ima_server_sessions where client_pid=n;
(where n = the pid of the iigcd server process).


--
geraintjones

Hello,

you can try this :
SELECT *
FROM ima_server_sessions
WHERE client_pid = 'your DAS pid'

HTH
--
Jean-Pierre Zuate
La Fage Conseil
01 47 96 30 69
jean-pierre.zuate (AT) lafageconseil (DOT) fr
http://lafageconseil.fr/


2011/11/16 Martin Crouch <spamspamspam (AT) spaml (DOT) com>

I'd just highlight what Jeremy mentioned here.
Yes, you can run iimonitor for DAS server, but you need to be on Ingres
9.2 or more recent release.


--
bilgihan

On 16/11/2011 11:06, Martin Crouch wrote:
could run iimonitor against anything else but a DBMS server.

Hi Group,

We recently moved from Ingres 2.6 on OpenVMS alpha to an Ingres 9.2.1
server installation on Linux but with the clients still on VMS. Along
the way we (I) missed the implications of having having
ii_charset=DECMULTI on the client side and ISO88591 on the server side.
So far the only issue I know of occurs with ABF and table_key variables
which don't always match when you try to use them to update tables,
depending on the actual value.

My question for the gurus out there is whether I can just change
config.dat and restart the clients (gcc,gcd,gcn) on the VMS node or is
there more that needs to be done?

Thanks for any advice,

Mike

On Nov 17, 11:19*am, Mike <r... (AT) upei (DOT) ca> wrote:
There is more to be done :-( Mostly related to data cleansing/sanity
checks.

As the version you have is likely under a support contract I'd
recommend raising a support issue at http://servicedesk.actian.com/

To get you started, things to consider/research:

1) How was the migration from VMS to Linux done? Was the data
transliterated?
2) How much data has been added with the new (bad charset setting)
setup? Can it be identified?
3) What character set is the VMS clients really using? For instance
are the VMS clients really using DEC terms or Putty?
4) Is the VMS client still running a DBMS server? If so, the charset
can NOT be changed.
5) related to #2, if the charset is changed non-ASCII data will be
coming back in a different form, is this an issue?
6) Related to #3 and #5, how much non-ASCII data is there? Can you
identify it quickly and how much data is in the database?

Chris