Thanks Roberto,

I’ll check that the source code we have built includes the fix for 3375.

Best regards, John

From: users-list [mailto:users-list-bounces+john.burgess=pb.com@monetdb.org] On Behalf Of Roberto Cornacchia
Sent: 07 March 2016 12:45
To: Communication channel for MonetDB users <users-list@monetdb.org>
Subject: Re: BATfetchjoin does not hit always => can't use fetchjoin

You may be experiencing this bug: https://www.monetdb.org/bugzilla/show_bug.cgi?id=3375

Tip: when you search for a bug from the quick search on https://www.monetdb.org/bugzilla/ this searches by default only in Open bugs (that have status UNCONFIRMED | NEW | ASSIGNED | REOPENED). The bug report above was closed (has status RESOLVED) so it won't be found that way.

For a more customised search, use the link "Search" below in the page.

On 7 March 2016 at 13:16, John Burgess <john.burgess@pb.com> wrote:

Hi,

I'm completely new to monetdb and have been dropped in at the deep end with an application support issue at a customer site.
The release running is FEB2013 SP6 on Windows Server 2012 64 bit.
There are customizations including aggregate functions written in MAL so the issue may not derive from monetdb source.

I have searched bug lists but not found an obvious match for the error that is being reported, so I'm wondering whether anyone has experienced similar symptoms and found a solution. (Bug 3375 is the closest match and was fixed in the release in use)

The reported problem is that the application works normally for a period until something causes monetdb to consistently report errors:

Error: GDK reported error.
SQLState:  22000
ErrorCode: 0
Error: BATfetchjoin(tmp_3662,tmp_4362) does not hit always (|bn|=0 != 2660745=|l|) => can't use fetchjoin.
SQLState:  22000
ErrorCode: 0

It has been noted that the error appears to be in response to some SQL which up to that point had been working :

select count(*) as "_m1_",  avg("B"."C") as "_m2_"
from "A"
left outer join "B" on "A"."A_ID" = "B"."A_ID"

Further, there is a foreign key relationship defined:
ALTER TABLE "B" ADD CONSTRAINT fk_B FOREIGN KEY ("A_ID") REFERENCES "A"("A_ID")
and dropping the index corresponding to the foreign key causes monetdb to recover. i.e. drop index fk_B


All suggestions would be gratefully appreciated. In the meantime, I will try to reproduce the issue in house.

Thanks,
John Burgess

________________________________

_______________________________________________
users-list mailing list
users-list@monetdb.org
https://www.monetdb.org/mailman/listinfo/users-list

---