Hi Pierre, This is known bug on pre Oct2015 release AFAIK. In my case I was instructed to delete table directly from system catalog: "likely the last (highest id) is the one to keep. so a delete from _tables where id in (16884, ..);" The usual disclosure applies, backup etc.
I have a cookbook for upgrade on ubuntu: 1. drop view storage a storagemodel, if they exist dictionary. ( select * from _tables where name like 'storage%'; delete from _tables where id in (30501,30512); ) 2. upgrade to Jan2014 release: sudo apt-get install monetdb5-sql=11.17.21-20140725 monetdb-client=11.17.21-20140725 monetdb5-server=11.17.21-20140725 startup database and connect to it. Upgrade data dictionary runs at first connection. upgrade to the lastest release: sudo apt-get update; sudo apt-get install monetdb5-sql monetdb-client
Best of luck.
Radovan
On Wed, 2014-11-26 at 10:01 +0100, Pierre-Adrien Coustillas wrote:
Hello,
we have again duplicated table on version Oct2014.
pcoustillas@monetdb:~$ mclient lemonde Welcome to mclient, the MonetDB/SQL interactive terminal (Oct2014) Database: MonetDB v11.19.3 (Oct2014), 'mapi:monetdb://monetdb:50000/lemonde' Type \q to quit, ? for a list of available commands auto commit mode: on sql>\d src__at__lm__visites_agregees table sys.src__at__lm__visites_agregees is not unique, corrupt catalog? sql>
echo "SELECT name FROM SYS.TABLES WHERE system=false;" | mclient lemonde | grep " " | grep -v " name " | grep -v " tuple" | sed 's/[| ]//g' | sort | uniq -c | grep -v " 1 " 2 src__at__lm__visites_agregees 2 src__at__tra__visites_agregees 2 tmp_lm_suppr_id 4 tmp_lm_suppr_id_unique 2 tmp_tra_suppr_id 4 tmp_tra_suppr_id_unique
we do a lot of drop and create table. Is the trouble can come of it ? it must take a sleep after a drop?
Pierre
-- 1G6 52 route de bischwiller 67300 Schiltigheim Société de Services et de Formations en Logiciels Libres http://1g6.biz Tél : 06 64 63 70 35
users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list