 Re: [Info-Ingres] VDBA weirdness -
01-09-2009
, 10:49 AM
Thanks Marty. I'm looking into it right now...
Roger Whitcomb | Architect, Engineering | Roger.Whitcomb (AT) ingres (DOT) com|
Ingres | 500 Arguello Street | Suite 200 | Redwood City | CA | 94063 |
USA
<http://www.google.com/maps?f=q&hl=en...llo+Street+%7C
+Suite+200+%7C+Redwood+City+%7C+CA+%7C+94063+%7C+U SA+&sll=37.0625,-95.67
7068&sspn=50.557552,73.037109&ie=UTF8&t=h&z=16&iwl oc=addr> | +1
650-587-5596 | fax: +1 650-587-5550
________________________________
From: Martin Bowes [mailto:martin.bowes (AT) ctsu (DOT) ox.ac.uk]
Sent: Friday, January 09, 2009 2:19 AM
To: Ingres and related product discussion forum
Cc: Roger L. Whitcomb
Subject: RE: [Info-Ingres] VDBA weirdness
Done. Issue 133414.
Marty.
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of
Roger L. Whitcomb
Sent: 08 January 2009 17:18
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] VDBA weirdness
Marty -
I'm fairly certain this is a VDBA bug, so please open a service desk
issue and we'll deal with it. Thanks.
Roger Whitcomb | Architect, Engineering | Roger.Whitcomb (AT) ingres (DOT) com|
Ingres | 500 Arguello Street | Suite 200 | Redwood City | CA | 94063 |
USA
<http://www.google.com/maps?f=q&hl=en...llo+Street+%7C
+Suite+200+%7C+Redwood+City+%7C+CA+%7C+94063+%7C+U SA+&sll=37.0625,-95.67
7068&sspn=50.557552,73.037109&ie=UTF8&t=h&z=16&iwl oc=addr> | +1
650-587-5596 | fax: +1 650-587-5550
________________________________
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of
Martin Bowes
Sent: Thursday, January 08, 2009 7:28 AM
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] VDBA weirdness
Hi All,
I've just upgraded Ingres on my PC to 9.1.1 + p13186 and the problem
persists.
Marty
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of
Martin Bowes
Sent: 08 January 2009 10:10
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: [Info-Ingres] VDBA weirdness
Hi All,
I'm using VDBA version 9.1.0 to connect via a vnode to an Ingres2006 R1
installation (II 9.0.4 (a64.lnx/105)NPTL). The proble also occurs if the
target installation is II 9.1.1 (a64.lnx/103)NPTL.
I'm looking at the two indexes on a table. One index has a single column
the other two columns.
If I use the 'Pages' button to examine the indexes...
The index with a single column has no problems
The index with two columns generates 'System error 34'.
It seems to be related to the amount of data in the index. Normally
these indexes store the details for a tad over 15000 rows. But when I
reduce the rows to around 3000 the Pages button has no problem with the
two column index.
Try this...
sql bowtest << SQL_END
\r
set autocommit on
\p\g
drop table x;
\p\g
create table x(id integer not null, a varchar(50), b varchar(50)) with
no journaling;
\p\g
create index x_idx on x (a, b) with structure = isam;
\p\g
insert into x values (1, 'asdfg', 'qwerty');
\g
insert into x select * from x;
\g\g\g\g\g\g\g\g\g\g /* You should now have 2048 rows in x */
modify x_idx to isam on a, b;
\p\g
SQL_END
Examine with VDBA at this point and index is cool.
Now add some extra rows...
sql bowtest <<SQL_END
\r
set autocommit on
\p\g
insert into x select * from x;
\g\g\g\g
modify x_idx to isam on a, b;
\p\g
SQL_END
Examine with VDBA and get System error 34.
Martin Bowes
 |
Linear Mode
