Re: Regarding 'invalid argument: b must have a dense head'

Hi Stefan, Sorry for the lack of information. I'm pretty sure that the database was originally created before the most recent (Oct2014) update, then went through the update process. So, I was using that updated version (not SP1) when the messages appeared. The database is indeed started with monetdb but there are no messages in the merovingian log file except the message identifying the mapi client and the fact that it's connecting via a UNIX domain socket. The database is quite small, containing CERT vulnerability data. Because the NVD database is updated every two hours or so, and there is no way to know which fields will be changed, instead of an UPDATE I just delete any existing record and re-insert the new one, so the commands look like this: DELETE from cve where id='CVE-2014-6609'; INSERT INTO cve VALUES ('CVE-2014-6609',...); I suspect you are right that the database has become corrupted because the same code, executed today, works fine on *different* CVE ID values, but attempting to re-execute the above code fails with the same "must have a dense head" message. If there is a setting I can use to generate more debug output in the merovingian log, just let me know. At this point the problem is easy to reproduce. Thanks for looking at this! Tim On 11/27/2014 05:03 PM, Stefan Manegold wrote:

Hi Tim,

The error might mean that (part of) your database got somehow corrupted.

To find out whether, and if so how/why, could you check your server's merovingian log (assuming you start your server using monetdbd & monetdb) or even share (the respective part of) it with us?

Also, which version/release of MonetDB are you using, did you initially create your database with this or an older MonetDB, and of which kind are your updates (updates, inserts, deletes)?

Thanks! Stefan

On November 27, 2014 5:41:24 AM CET, Tim Burress wrote:

...

Hello,

I have a database that I've been using for a while and which is updated several times a day. Recently when trying to insert records, there is an error:

GDK reported error: BATsubselect: invalid argument: b must have a dense head.

Could someone explain what this means, and how/if there is a way to fix the problem?

The command that produces the error is quite simple:

INSERT INTO sometable VALUES (blah,blah,blah...);

and since it's part of an automated process I don't think anything has changed. It was successful up to a two days ago.

Thanks!

Tim

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

-- | Stefan.Manegold@CWI.nl | DB Architectures (DA) | | www.CWI.nl/~manegold/ | Science Park 123 (L321) | | +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |