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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 06/08/15 16:35, Ashish Kumar Singh wrote:

Hi Jennie,

Any idea when Jul2015 is going to be released?

The intention is very soon. I intend to create a release candidate tomorrow.

Regards, Ashish

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

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.

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 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

- -- Sjoerd Mullender -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVw3ONAAoJEISMxT6LrWYg5wsIALh2tkcySYrkvZzRUURoZjMu syFqN0wJMsNq86s43mjxlDhY0W9zE9gXvUgZAXffzIZAjKV1iU1tTJr0oqitd3aa Omx32K2L65tzT8is34Pgz7gliJBcZuUkvPTtQfyt1JZxm7+kZ+eNehNJhim1Uv5E zJ1EuYD/38UHi77Cp6OdQREDVo58I1FUHRjxpMAEd9K9K+O6OQC3/bxqvEaXbNu2 nBLFlW+8gDxNjWK37Qh0VCZAZrsQL5rgBk/cHCUl47+h7uGB9wn4LAKcHxJW+nIj 9ZBlwdWCZWPrAfuyYIqlgGcEdfGLYHd7SWBSs6hdS9sPVLuy3QV8d0Yg4G8MoWw= =htyT -----END PGP SIGNATURE-----