Do you happen to have any more detailed info of the crash? Such as was the drop table a single statement transaction, or part of a multi statement transaction? Is the problem reproducible?

Can you please try to restart the server to see if it helps cleaning up?

Jan2014 is a pretty old version. I'd highly recommend you to upgrade. Jul2015 will be released later this month.

On 08 Jul 2015, at 12:37, Ashish Kumar Singh <ashishkumar.singh@altair.com> wrote:

Hi List,

We are seeing a situation with monetdb v11.17.17 "Jan2014-SP2” release where at the time of dropping table , data base got crashed. After that we are not able to drop this table.

Any command to drop this table is returning with success but we can not create same table again as it complains about table exists/ in use.

But when we try to select * from this table or do a count on this it does complains saying No Such Table exist.

My hunch is somehow database catalogue got corrupted, what is recommended way to bring back database to good health after any such condition occurs?

We have not tried restarting monetdb instance yet.

Regards,

Ashish Kumar Singh

Mobile: +91-9972045095

Skype: toashishk@gmail.com

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