Re: possible monetdb catalogue corruption and how to recover from it?

On 09/07/15 10:38, Ashish Kumar Singh wrote:

Hi Jennie,

Thanks for reply!

Drop table is a single statement transaction. Problem is not reproducible though easily. We encountered it after 150 iterations of drop and create table each happening in 1 hour interval but our ETL tool. We did a restart and after this problem was resolved. I think database was able to do a cleanup.

What will be a recommended way of doing a health check on database catalogue when such problem happens as practically problem does happen right?

Thanks for the heads up on upcoming release we shall plan to upgrade to it.

Regards, Ashish

From: users-list on behalf of Ying Zhang Reply-To: "users-list@monetdb.org mailto:users-list@monetdb.org" Date: Thursday, 9 July 2015 1:27 pm To: "users-list@monetdb.org mailto:users-list@monetdb.org" Subject: Re: possible monetdb catalogue corruption and how to recover from it?

Hai Ashish,

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.

Regards,

Jennie

On 08 Jul 2015, at 12:37, Ashish Kumar Singh mailto: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. Could not be reproduced on Jul2015 using either 2000 separate sessions and a single session with 2000 create/drop pairs

...

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?

That's on our wishlist for future tools/extensions.

regards, Martin

...

We have not tried restarting monetdb instance yet.

Regards, Ashish Kumar Singh Mobile: +91-9972045095 Skype: toashishk@gmail.com mailto:toashishk@gmail.com

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

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