drop ima_dbms_fis;
\p\g
register table ima_dbms_fis (
        server varchar(64) not null not default is
                'SERVER',
        id integer4 not null not default is
                'exp.adf.adg.fi_id',
        complement integer4 not null not default is
                'exp.adf.adg.fi_cmplmnt',
        type varchar(20) not null not default is
                'exp.adf.adg.fi_type',
        flags integer4 not null not default is
                'exp.adf.adg.fi_flags',
        opid integer4 not null not default is
                'exp.adf.adg.fi_opid',
        args integer4 not null not default is
                'exp.adf.adg.fi_numargs',
        dtresult integer4 not null not default is
                'exp.adf.adg.fi_dtresult',
        dtarg1 integer4 not null not default is
                'exp.adf.adg.fi_dtarg1',
        dtarg2 integer4 not null not default is
                'exp.adf.adg.fi_dtarg2',
        dtarg3 integer4 not null not default is
                'exp.adf.adg.fi_dtarg3',
        dtarg4 integer4 not null not default is
                'exp.adf.adg.fi_dtarg4'
)
as import from 'tables'
with dbms = IMA,
structure = sortkeyed,
key = (server);
\p\g
grant all on ima_dbms_fis to ingres;
\p\g
grant select on ima_dbms_fis to public;
\p\g

Adding this table to ima_dbms_types and ima_dbms_operators adds the ability to retrieve the list of functions and their signatures.  The query makes use of an internal function iitypename which translates the numeric type code into a name.

select
    a.name,
    case when a.type='COMPARISON' then
        trim(iitypename(b.dtresult)) + ' = ( ' +
        trim(iitypename(b.dtarg1)) + ' ' +
        a.name + ' ' +
        trim(iitypename(b.dtarg2)) + ' )'
        when a.type='OPERATOR' then
        trim(iitypename(b.dtresult)) + ' = ( ' +
        trim(iitypename(b.dtarg1)) + ' ' +
        a.name + ' ' +
        trim(iitypename(b.dtarg2)) + ' )'
    else
        trim(iitypename(b.dtresult)) + ' = ' +
        a.name + '( ' +
            case when b.dtarg1 != '' then trim(iitypename(b.dtarg1)) else '' end +
            case when b.dtarg2 != '' then ', ' + trim(iitypename(b.dtarg2)) else '' end +
            case when b.dtarg3 != '' then ', ' + trim(iitypename(b.dtarg3)) else '' end +
            case when b.dtarg4 != '' then ', ' + trim(iitypename(b.dtarg4)) else '' end
        + ' )'
    end as signature
from
    ima_dbms_operators a,
    ima_dbms_fis b
where
    a.opid = b.opid
group by a.name, 2
order by a.name

Some sample output from this query:

|name                          |signature                       |
|soundex                       |char = soundex( text )          |
|soundex                       |char = soundex( varchar )       |
|sqrt                          |float = sqrt( float )           |
|squeeze                       |nvarchar = squeeze( nchar )     |
|squeeze                       |nvarchar = squeeze( nvarchar )  |
|squeeze                       |text = squeeze( c )             |

So in answer to my own question; yes, it is useful.  I’ll be trying this on an IngresGeospatial build when I get my hands on one.

Related posts

• Debugging the Hibernate project with Eclipse
• Hibernate 3.5.0-Final released
• Google Summer of Code (GSoC) 2008
• IMA Guru (Pronounced, I’m A Guru) – I definitely am not
• Data Access Message Protocol – Wireshark dissector

Data types
The following registration will create a table that contains data type name and the data type description bits.

drop ima_dbms_datatypes;
\p\g
register table ima_dbms_datatypes (
	server varchar(64) not null not default is
		'SERVER',
	name varchar(30) not null not default is
		'exp.adf.adg.dt_name',
	id integer4 not null not default is
		'exp.adf.adg.dt_id',
	stat integer4 not null not default is
		'exp.adf.adg.dt_stat'
)
as import from 'tables'
with dbms = IMA,
structure = sortkeyed,
key = (server);
\p\g
grant all on ima_dbms_datatypes to ingres with grant option;
\p\g
grant select on ima_dbms_datatypes to public;
\p\g

The data type description bits should match the definitions in adf.h. Use the hex function in the select to make the values easier to read.
select id, hex(stat) as stat, name from ima_dbms_datatypes;

Operators
The following registration will create a table containing information about the operators available in the DBMS.

drop ima_dbms_operators;
\p\g
register table ima_dbms_operators (
	server varchar(64) not null not default is
		'SERVER',
	name varchar(30) not null not default is
		'exp.adf.adg.op_name',
	opid integer4 not null not default is /* order within the constructed operator list */
		'exp.adf.adg.op_id',
	type varchar(20) not null not default is /* type of operator */
		'exp.adf.adg.op_type',
        use varchar(30) not null not default is /* where in an expression the operator is used */
                'exp.adf.adg.op_use',
        qlang integer not null not default is /* the query language where the operator is permitted 1=QUEL, 2=SQL*/
                'exp.adf.adg.op_qlangs',
        cntfi integer not null not default is /* count of function instances */
                'exp.adf.adg.op_cntfi'
)
as import from 'tables'
with dbms = IMA,
structure = sortkeyed,
key = (server);
\p\g
grant all on ima_dbms_operators to ingres with grant option;
\p\g
grant select on ima_dbms_operators to public;
\p\g

A query of the table produces an indiscriminate list of functions defined in the DBMS.

I’ve only tried to register these tables on Ingres II 9.2.0 and if you are considering trying them out the usual disclaimers apply.

So, useful or useless?

Related posts

• Useful or useless? Follow on post …
• IMA Guru (Pronounced, I’m A Guru) – I definitely am not

The weakness of IMA is the lack of documentation and the reason? There are over 1700 parameters, maybe more, that cover many aspects of the internal control structures. The meaning of each of the values and their inter-relationship is usually locked within the mind of the person who decided to exposed it. The strength of IMA is the ability to extract these values as queries into the DBMS. This means that DBMS values can be exposed via any client technology that can issue queries.

There have been a few attempts to start the documentation of each parameter yet the projects have been stifled by the sheer volume of information and knowledge that is required.

Some attempts have been made to define a standard schema with the assistance of thrid party vendors and partners whilst maintaining some degree of client confidentiality. Inevitably, with each new version of Ingres some subtle change in the control structure reduces one or more of these monitoring queries to return zero rows.

I shall leave the vagaries of registering IMA tables for someone else or to a later post (much later).

For the inquisitive, this sample query returns a list of the sessions that are using an Ingres lock, those that are waiting and the one that is granted together with the query text. I’ve only tried it on Ingres 2006. Hope you find it useful, usual disclaimers apply.
select
a.server, a.session_id, db_name, _bintim() - session_time as duration,
session_cpu as cpu, session_query, session_lquery, resource_id, lock_state from
ima_server_sessions a, ima_server_sessions_extra b,
ima_server_sessions_desc e, ima_locklists c, ima_locks d, ima_server_sessions_query q
where
a.session_id = q.session_id and
resource_id in
(select
b.resource_id
from
ima_locklists a, ima_locks b
where
a.locklist_wait_id = b.lock_id)
and c.locklist_id = d.locklist_id
and a.session_id = c.locklist_session_id
and a.session_id = b.session_id
and a.session_id = e.session_id \p\g

In order to see the last query a table is added to include a field that is included in Ingres but is not yet exposed. The session_lquery field provides the text of the previously executed query for the session.
/*
** Add ima_server_sessions_query table.
**
** This script should be run as $ingres.
** e.g.
** sql -u"\$ingres" imadb
**
** Add session_lquery. For imadb created with 4k pages the field could
** fit in the ima_server_sessions table.
*/
drop table ima_server_sessions_query;
\p\g
register table ima_server_sessions_query(
server varchar(64) not null not default is
'SERVER',
session_id varchar(32) not null not default is
'exp.scf.scs.scb_index',
session_lquery varchar(1000) not null not default is
'exp.scf.scs.scb_lastquery' )
as import from 'tables' with dbms = IMA,
structure = unique sortkeyed,
key = (server, session_id)
\p\g
grant select on ima_server_sessions_query to public with grant option;
\p\g


Related posts

• Useful or useless? Follow on post …
• Data Access Message Protocol – Wireshark dissector
• Ingres Migration Toolset
• Ingres command line RPM installation
• Ingres doc search plug-in updated