July 2009 - users-list

[MonetDB-users] can not delete data
by Allen Zhang 28 Jul '09

28 Jul '09

Hi, We had such a weird issue here, we are using Feb2009-SuperBall package, we managed get our data into monetdb, but some how when we try to delete data, it reappears under single user or readonly mode. Here is what we did, we put database in normal mode without gdk_single_user and gdk_readonly in monetdb5.conf. Issue a delete sql statement in mclient, now we query the data, seem the data is gone, and then we stop the database server, and start it in readonly mode. Then query the data again, the data come back!!! Seems to us the monetdb did not sync the memory with disk. Any ideas? Allen

1 0

[MonetDB-users] XRPC issues
by Roy Walter 28 Jul '09

28 Jul '09

Hi A couple of tijah related issues with query modules. 1. The following query when run from xrpc.html appears to ignore the $term argument and returns a very large result! module namespace tj = "tj"; declare function tj:tijahSearch($term as xs:string) as node()* { tijah:queryall("//speech[about(., $term)]") }; 2. Running the above query sometimes produces the following error: !ERROR: interpret: no matching MIL operator to 'tj_query_handler(bit BAT[void BAT], ... Thanks, Roy

2 10

[MonetDB-users] string coercion error
by Alex Bo. 27 Jul '09

27 Jul '09

Hi, What does the following exception mean: !SyntaxException: convertConstant: no string coercion for 'any' !SyntaxException:convertConstant:conversion error !SyntaxException efConstant:constant coercion error from void to any I can't reproduce it - I am getting this from time to time on simple queries that usually work. Thanks. -- View this message in context: http://www.nabble.com/string-coercion-error-tp24684760p24684760.html Sent from the monetdb-users mailing list archive at Nabble.com.

2 1

Re: [MonetDB-users] result cache?
by Allen Zhang 27 Jul '09

27 Jul '09

Thanks Milena, Is that means monetdb does not provide final result cache? We have sql client will query same query to the database multiple times, imaging each query took 2 minutes to run, that¹s will be really painful when the client ask 10 times, since our database is readonly, so a real result cache will really help us. Regards Allen

3 6

[MonetDB-users] Segfault interpreting sql query
by Franck Routier 27 Jul '09

27 Jul '09

Hi, Monetdb is segfaulting, probably while interpreting a query or planning it. I first thought it had to do with data, but after emptying the tables, the query still makes monetdb segfault. Error in syslog says: [ 1230.812708] mserver5[5369]: segfault at 7fab4c2b5ff8 ip 00007fab4f894285 sp 00007fab4c2b6000 error 6 in lib_sql.so.2.30.2[7fab4f7e3000+116000] Following is the faulty ddl / query. Is there anything I can do to help debug this ? Franck The ddl is the following: CREATE TABLE cabact ( cabactcsu integer NOT NULL, cabact___rforefide character varying(32) NOT NULL, cabact___rteprcide character varying(32) NOT NULL, cabact___rtestdide character varying(32) NOT NULL, cabact___rfovsnide character varying(32) NOT NULL, cabactlil character varying(100) NOT NULL, cabactlic character varying(32) NOT NULL, cabacttxt character varying(1500), cabact___rfontride character varying(32), cabact_f1rfodstide character varying(32), cabact_f2rfodstide character varying(32), cabact_f3rfodstide character varying(32), cabact_f4rfodstide character varying(32), cabact_f5rfodstide character varying(32), cabact_f6rfodstide character varying(32), cabact_f7rfodstide character varying(32), cabact_f8rfodstide character varying(32), cabact_f9rfodstide character varying(32), cabact_c1rfodstide character varying(32), cabact_c2rfodstide character varying(32), cabact_c3rfodstide character varying(32), cabact_c4rfodstide character varying(32), cabact_c5rfodstide character varying(32), cabact_c6rfodstide character varying(32), cabact_c7rfodstide character varying(32), cabact_c8rfodstide character varying(32), cabact_c9rfodstide character varying(32), cabactqte double, cabact___rfountide character varying(32), cabactdtd timestamp with time zone NOT NULL, cabactdtf timestamp with time zone NOT NULL, cabactax1 integer NOT NULL DEFAULT 1, cabactax2 integer NOT NULL DEFAULT 2, cabactax3 integer NOT NULL DEFAULT 3, cabactax4 integer NOT NULL DEFAULT 4, cabactax5 integer NOT NULL DEFAULT 5, cabactax6 integer NOT NULL DEFAULT 6, cabactax7 integer NOT NULL DEFAULT 7, cabactax8 integer NOT NULL DEFAULT 8, cabactax9 integer NOT NULL DEFAULT 9 ); CREATE TABLE rfoade ( rfoade___rforefide character varying(50) NOT NULL, rfoade___rfovdeide character varying(50) NOT NULL, rfoade_i_rfodstide character varying(50) NOT NULL, rfoadeaxe integer DEFAULT 0 NOT NULL, rfoadervs integer NOT NULL, rfoadenpm integer DEFAULT 1, rfoade_s_rfodstide character varying(32) NOT NULL, rfoadegch character varying(120) DEFAULT 'AAAAA' NOT NULL, rfoadedrt character varying(120) DEFAULT 'ZZZZZ' NOT NULL, rfoadeniv integer DEFAULT 0 NOT NULL, rfoadetxt character varying(1800), rfoadenum integer DEFAULT 99999 NOT NULL, rfoadeden integer DEFAULT 999 NOT NULL, rfoadechm character varying(5500) DEFAULT 'INVALID' NOT NULL, rfoadeord integer DEFAULT 999999 NOT NULL ); And the query is: select * from cabact where cabact___rforefide = 'FHSJ' and cabact___rteprcide = 'CPTANA' and cabact___rtestdide = '100' and cabact___rfovsnide = '200805_001' and (cabact_f1rfodstide IS NULL or cabact_f1rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_f2rfodstide IS NULL or cabact_f2rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_f3rfodstide IS NULL or cabact_f3rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_f4rfodstide IS NULL or cabact_f4rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_f5rfodstide IS NULL or cabact_f5rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_f6rfodstide IS NULL or cabact_f6rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_f7rfodstide IS NULL or cabact_f7rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_f8rfodstide IS NULL or cabact_f8rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_f9rfodstide IS NULL or cabact_f9rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_c1rfodstide IS NULL or cabact_c1rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_c2rfodstide IS NULL or cabact_c2rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_c3rfodstide IS NULL or cabact_c3rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_c4rfodstide IS NULL or cabact_c4rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_c5rfodstide IS NULL or cabact_c5rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_c6rfodstide IS NULL or cabact_c6rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_c7rfodstide IS NULL or cabact_c7rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1')) and (cabact_c8rfodstide IS NULL or cabact_c8rfodstide IN (select rfoade_i_rfodstide from rfoade where rfoade___rfovdeide='SECA' and rfoade___rforefide = 'FHSJ' and rfoadervs='1'))

5 13

[MonetDB-users] JDBC InvalidCredentialsException
by McKennirey.Matthew 27 Jul '09

27 Jul '09

2 3

[MonetDB-users] result cache?
by Allen Zhang 24 Jul '09

24 Jul '09

Hi, Does monetDB provide result cache? How to enable it? Best Regards Allen

2 1

[MonetDB-users] Segfaulting Embedded MonetDB/SQL
by Charles Samuels 23 Jul '09

23 Jul '09

Greetings, I ran the attached program. I compiled it like so: c++ -g3 monetembedded.cpp `monetdb-sql-config --cflags --libs` `monetdb- clients-config --cflags --libs` `monetdb-config --cflags --libs` `monetdb5-config --cflags --libs` -lMapi -lembeddedsql5 -lmutils MonetDB is compiled from MonetDB-May2009-SuperBall-SP1 And it segfaults before getting out of embedded_sql(). Is my program wrong, or is there a known (or unknown) problem in MonetDB with Embedded SQL? Here're the stack traces: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb169bb90 (LWP 20796)] 0xb7f039fc in sql_find_subtype () from /home/charles/.local/lib/libembeddedsql5.so.2 (gdb) bt #0 0xb7f039fc in sql_find_subtype () from /home/charles/.local/lib/libembeddedsql5.so.2 #1 0xb1c1af1e in SQLinitClient () from /usr/lib/MonetDB5/lib/lib_sql.so #2 0x09a8df68 in ?? () (gdb) info thr * 3 Thread 0xb169bb90 (LWP 20796) 0xb7f039fc in sql_find_subtype () from /home/charles/.local/lib/libembeddedsql5.so.2 1 Thread 0xb6ec78e0 (LWP 20792) 0xb7f68424 in __kernel_vsyscall () (gdb) thr 1 [Switching to thread 1 (Thread 0xb6ec78e0 (LWP 20792))]#0 0xb7f68424 in __kernel_vsyscall () (gdb) bt #0 0xb7f68424 in __kernel_vsyscall () #1 0xb7c9e48b in read () from /lib/i686/cmov/libc.so.6 #2 0xb7a24fdd in pipe_read () from /home/charles/.local/lib/libstream.so.1 #3 0xb7a238ac in stream_readSht () from /home/charles/.local/lib/libstream.so.1 #4 0xb7a23950 in bs_read () from /home/charles/.local/lib/libstream.so.1 Thanks for your help, Charles -- Charles Samuels

1 0

[MonetDB-users] put()
by Roy Walter 23 Jul '09

23 Jul '09

Hi What is the argument list for the fn:put() function? -- Roy

2 3

Re: [MonetDB-users] Database size
by Charles Samuels 22 Jul '09

22 Jul '09

On Wednesday 2009 July 22 12:25:23 pm Martin Kersten wrote: > Charles Samuels wrote: > > Hi, > > > > I have read previously that monetdb is intended to be used only when the > > data can fit in memory. I'm not sure how to interpret this statement - > > does this mean that the entire database must fit in memory, or does it > > mean that only the data being operated on when selected from the database > > must fit in memory? > > MonetDB does *not* limit your database to fit in main memory. > > However, it uses main memory techniques to address the elements in > tables loaded for processing. This means that the hot-set accessed > during query execution is limited when you run on 32-bit machines. Can you elaborate a little bit? Does hot-set mean that a select on the database can only span the chunk that can fit in a 32-bit process's address space? (This seems like a perfectly reasonable limitation, I'm just making sure). > > > We are wanting to store *huge* amounts of data, ultimately several TBs. > > The actual data being select at any given time will only be several > > hundred MBs, however. Is this a reasonable usage of MonetDB? > > The largest database we use internally to experiment with is a 6TB > astronomical database. It contains two large tables, one with 400M rows of > 500 columns and another of 20 B rows and 6 columns. Both tables are larger > then 1TB each. That's really great to hear :) > > This runs on a Linux dual quadcore with 64G Ram and lots of disk space. > Ofcourse, at some point you well notice IO behavior ;) For what kind of operations do you need that amount of memory? If you were to do a select on just a few thousand rows on that same mega-database, would it be happy with more "mundane" amounts of memory? > > > But most importantly, I have noticed that all the row ID indexes are > > "int" - why the 32 bit limitation? This just seems like a symptom of the > > above problem; that the entire database must fit in memory. > > You can use the system with both 32- and 64- bit oids. Ah, I previously had a bit of a brain failure. When reading Mapi.h, I noticed that "mapi_get_row_count" returned an int - obviously you wouldn't want select to return 2^32 rows, which is what this function counts the rows of. Thanks Martin (and also Lefteris), Charles -- Charles Samuels

2 1