qbf, (i)sql, report, sreport utilities and vnodes to different versions of ingres

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Dennis Roesler - 22 Jul 2006 01:21 GMT

Why is it the utilities such as qbf and (i)sql don't behave the same
when connecting through vnodes to different versions of ingres?

On linux I have Ingres 2006 Version II 9.0.4 (int.lnx/103)NPTL
and on the other end of a vnode is Ingres HP-UX Version II 2.6/0305
(hpb.us5/00).

If I try to use qbf from 9.0.4 to 2.6 I get a message about updating
catalogs. If I use (i)sql I have no problems. Perl DBI has no problems
between 9.0.4 and 2.6. I've run into this problem with (s)report as
well. copydb also works from 9.0.4 to 2.6. Does one access a certain
area of the catalogs that the other doesn't?

Cheers

Dennis

Reply to this Message

Betty & Karl Schendel - 22 Jul 2006 02:06 GMT

>Why is it the utilities such as qbf and (i)sql don't behave the same
>when connecting through vnodes to different versions of ingres?

qbf and the report utilities do access more of the front-end catalogs.
There's a semi-generic "front end connect" call that qbf, rbf, and
the like use, that give a required minimum catalog version. [i]sql,
copydb, unloaddb and other simple utilities don't deal in the
front-end catalogs and so they don't use that call.
I forget what exactly changed in the ingres2006 catalogs; I think it
had to do with the 1024 column change.

Karl

Reply to this Message

Dennis Roesler - 22 Jul 2006 03:09 GMT

>> Why is it the utilities such as qbf and (i)sql don't behave the same
>> when connecting through vnodes to different versions of ingres?
[quoted text clipped - 8 lines]
>
> Karl

Thanks Karl, and the best in your new job.

Dennis

Reply to this Message