
Hello - My understanding is you should not run a new monetdb version with a dbfarm created from an older version. We have just updated our system from a Jul2015-SP3 version to the latest Jun2016-SP2 version. I have created a new db farm and plan to recreate the tables in the new farm. My question; How do you remove the old dbfarm? Our data is quite large (1.8 T) and I'd like to retrieve this space for other use. While I can start the db against the new farm, I can find no method of removing the old dbfarm to reclaim this space. Thanks - Lynn

You can just delete the dbfarm directory. So, are you re-creating your data instead of migrating data to new version? I’m interested in how to upgrade to a new version without recreating the data. Vince From: users-list <users-list-bounces+vincent.sheffer=sysorex.com@monetdb.org> on behalf of Lynn Carol Johnson <lcj34@cornell.edu> Reply-To: Communication channel for MonetDB users <users-list@monetdb.org> Date: Friday, October 14, 2016 at 1:27 PM To: Communication channel for MonetDB users <users-list@monetdb.org> Subject: new monetdb version, old farm Hello - My understanding is you should not run a new monetdb version with a dbfarm created from an older version. We have just updated our system from a Jul2015-SP3 version to the latest Jun2016-SP2 version. I have created a new db farm and plan to recreate the tables in the new farm. My question; How do you remove the old dbfarm? Our data is quite large (1.8 T) and I’d like to retrieve this space for other use. While I can start the db against the new farm, I can find no method of removing the old dbfarm to reclaim this space. Thanks - Lynn The information transmitted, including any attachments, is intended only for the individual or entity to which it is addressed, and may contain confidential and/or privileged information. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by individuals or entities other than the intended recipient is prohibited, and all liability arising therefrom is disclaimed. If you have received this communication in error, please delete the information from any computer and notify the sender.

Upgrade paths are automatic from the previous feature release, unless we have announced that a re-create is necessary due to internal changes that can not be handled automatically. Upgrades from bug-fix releases never require a database re-creation. Upgrading over multiple feature releases, i.e. a very old dbfarm, is not supported. A dump and restore is the way to go. regards, Martin On 14/10/16 22:27, Lynn Carol Johnson wrote:
Hello -
My understanding is you should not run a new monetdb version with a dbfarm created from an older version. We have just updated our system from a Jul2015-SP3 version to the latest Jun2016-SP2 version.
I have created a new db farm and plan to recreate the tables in the new farm.
My question; How do you remove the old dbfarm? Our data is quite large (1.8 T) and I’d like to retrieve this space for other use. While I can start the db against the new farm, I can find no method of removing the old dbfarm to reclaim this space.
Thanks - Lynn
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

To verify: You¹re saying my upgrade from Jul2015-SP3 to Jun2016-SP2 does not require a database recreation as the farm is not that old? This would be great. Thanks - Lynn On 10/14/16, 5:08 PM, "users-list on behalf of Martin Kersten" <users-list-bounces+lcj34=cornell.edu@monetdb.org on behalf of martin@monetdb.org> wrote:
Upgrade paths are automatic from the previous feature release, unless we have announced that a re-create is necessary due to internal changes that can not be handled automatically. Upgrades from bug-fix releases never require a database re-creation.
Upgrading over multiple feature releases, i.e. a very old dbfarm, is not supported. A dump and restore is the way to go.
regards, Martin
On 14/10/16 22:27, Lynn Carol Johnson wrote:
Hello -
My understanding is you should not run a new monetdb version with a dbfarm created from an older version. We have just updated our system from a Jul2015-SP3 version to the latest Jun2016-SP2 version.
I have created a new db farm and plan to recreate the tables in the new farm.
My question; How do you remove the old dbfarm? Our data is quite large (1.8 T) and I¹d like to retrieve this space for other use. While I can start the db against the new farm, I can find no method of removing the old dbfarm to reclaim this space.
Thanks - Lynn
_______________________________________________ users-list mailing list 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

Hi Lynn, Like Soerjd mentioned previously you should upgrade in sequence so try not get behind in releases. Also as I found out the hard way it's impossible to downgrade. It plays havoc with your BBP version and catalog from memory. Regards, Brian Good On Oct 16, 2016 1:21 PM, "Lynn Carol Johnson" <lcj34@cornell.edu> wrote:
To verify: You¹re saying my upgrade from Jul2015-SP3 to Jun2016-SP2 does not require a database recreation as the farm is not that old? This would be great.
Thanks - Lynn
On 10/14/16, 5:08 PM, "users-list on behalf of Martin Kersten" <users-list-bounces+lcj34=cornell.edu@monetdb.org on behalf of martin@monetdb.org> wrote:
Upgrade paths are automatic from the previous feature release, unless we have announced that a re-create is necessary due to internal changes that can not be handled automatically. Upgrades from bug-fix releases never require a database re-creation.
Upgrading over multiple feature releases, i.e. a very old dbfarm, is not supported. A dump and restore is the way to go.
regards, Martin
On 14/10/16 22:27, Lynn Carol Johnson wrote:
Hello -
My understanding is you should not run a new monetdb version with a dbfarm created from an older version. We have just updated our system from a Jul2015-SP3 version to the latest Jun2016-SP2 version.
I have created a new db farm and plan to recreate the tables in the new farm.
My question; How do you remove the old dbfarm? Our data is quite large (1.8 T) and I¹d like to retrieve this space for other use. While I can start the db against the new farm, I can find no method of removing the old dbfarm to reclaim this space.
Thanks - Lynn
_______________________________________________ users-list mailing list 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
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

I”m confused now. Our db has already been upgraded. We went directly from Jul2015-Sp3 to Jun2016-SP2. Was there a feature release in-between these 2? Am I ok using the same dbfarm for both these releases? I will try to schedule upgrades as the fixes come out in the future. Thanks - Lynn From: users-list <users-list-bounces+lcj34=cornell.edu@monetdb.org<mailto:users-list-bounces+lcj34=cornell.edu@monetdb.org>> on behalf of Brian Hood <brianh6854@googlemail.com<mailto:brianh6854@googlemail.com>> Reply-To: Communication channel for MonetDB users <users-list@monetdb.org<mailto:users-list@monetdb.org>> Date: Sunday, October 16, 2016 at 2:30 PM To: Communication channel for MonetDB users <users-list@monetdb.org<mailto:users-list@monetdb.org>> Subject: Re: new monetdb version, old farm Hi Lynn, Like Soerjd mentioned previously you should upgrade in sequence so try not get behind in releases. Also as I found out the hard way it's impossible to downgrade. It plays havoc with your BBP version and catalog from memory. Regards, Brian Good On Oct 16, 2016 1:21 PM, "Lynn Carol Johnson" <lcj34@cornell.edu<mailto:lcj34@cornell.edu>> wrote: To verify: You¹re saying my upgrade from Jul2015-SP3 to Jun2016-SP2 does not require a database recreation as the farm is not that old? This would be great. Thanks - Lynn On 10/14/16, 5:08 PM, "users-list on behalf of Martin Kersten" <users-list-bounces+lcj34=cornell.edu@monetdb.org<mailto:cornell.edu@monetdb.org> on behalf of martin@monetdb.org<mailto:martin@monetdb.org>> wrote:
Upgrade paths are automatic from the previous feature release, unless we have announced that a re-create is necessary due to internal changes that can not be handled automatically. Upgrades from bug-fix releases never require a database re-creation.
Upgrading over multiple feature releases, i.e. a very old dbfarm, is not supported. A dump and restore is the way to go.
regards, Martin
On 14/10/16 22:27, Lynn Carol Johnson wrote:
Hello -
My understanding is you should not run a new monetdb version with a dbfarm created from an older version. We have just updated our system from a Jul2015-SP3 version to the latest Jun2016-SP2 version.
I have created a new db farm and plan to recreate the tables in the new farm.
My question; How do you remove the old dbfarm? Our data is quite large (1.8 T) and I¹d like to retrieve this space for other use. While I can start the db against the new farm, I can find no method of removing the old dbfarm to reclaim this space.
Thanks - Lynn
_______________________________________________ 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<mailto:users-list@monetdb.org> https://www.monetdb.org/mailman/listinfo/users-list
_______________________________________________ users-list mailing list users-list@monetdb.org<mailto:users-list@monetdb.org> https://www.monetdb.org/mailman/listinfo/users-list

Dear Lynn et al. to summarise, unless stated differently in the respective release notes, MonetDB supports database upgrades from an older to a newer version in the following cases: - from a feature release or bugfix release to a newer bugfix release of the same feature release, e.g., from the Jul2015 feature release to its second bugfix release Jul2015-SP2; - from a feature release or bugfix release to the next feature release or one of its bugfix releases, e.g., from the Jul2015-SP3 bugfix release to the Jun2016 feature release or its Jun2016-SP2 bugfix release (as in your case). We strong recommend, though, to backup your data/database(s) (i.e., dbfarm) before any upgrade. We never support downgrades from a newer to any older version of MonetDB. Feature releases are identified by a release name without "-SPx" (SP as in service pack) suffix, while the release name of bugfix releases has such suffix. Hence, between the Jul 2015-SP3 bugfix release and the Jun2016-SP2 bugfix release was the Jun2016 feature release. And: "upgrading databases" refers to continuing using the same dbfarm (exclusively) with a newer version of MonetDB. I hope, this helps to clarify. Best, Stefan On October 17, 2016 12:00:24 AM GMT+02:00, Lynn Carol Johnson <lcj34@cornell.edu> wrote:
I”m confused now. Our db has already been upgraded. We went directly from Jul2015-Sp3 to Jun2016-SP2. Was there a feature release in-between these 2? Am I ok using the same dbfarm for both these releases?
I will try to schedule upgrades as the fixes come out in the future.
Thanks - Lynn From: users-list <users-list-bounces+lcj34=cornell.edu@monetdb.org<mailto:users-list-bounces+lcj34=cornell.edu@monetdb.org>> on behalf of Brian Hood <brianh6854@googlemail.com<mailto:brianh6854@googlemail.com>> Reply-To: Communication channel for MonetDB users <users-list@monetdb.org<mailto:users-list@monetdb.org>> Date: Sunday, October 16, 2016 at 2:30 PM To: Communication channel for MonetDB users <users-list@monetdb.org<mailto:users-list@monetdb.org>> Subject: Re: new monetdb version, old farm
Hi Lynn,
Like Soerjd mentioned previously you should upgrade in sequence so try not get behind in releases.
Also as I found out the hard way it's impossible to downgrade.
It plays havoc with your BBP version and catalog from memory.
Regards,
Brian Good
On Oct 16, 2016 1:21 PM, "Lynn Carol Johnson" <lcj34@cornell.edu<mailto:lcj34@cornell.edu>> wrote:
To verify: You¹re saying my upgrade from Jul2015-SP3 to Jun2016-SP2 does not require a database recreation as the farm is not that old? This would be great.
Thanks - Lynn
On 10/14/16, 5:08 PM, "users-list on behalf of Martin Kersten" <users-list-bounces+lcj34=cornell.edu@monetdb.org<mailto:cornell.edu@monetdb.org> on behalf of martin@monetdb.org<mailto:martin@monetdb.org>> wrote:
Upgrade paths are automatic from the previous feature release, unless we have announced that a re-create is necessary due to internal changes that can not be handled automatically. Upgrades from bug-fix releases never require a database re-creation.
Upgrading over multiple feature releases, i.e. a very old dbfarm, is not supported. A dump and restore is the way to go.
regards, Martin
On 14/10/16 22:27, Lynn Carol Johnson wrote:
Hello -
My understanding is you should not run a new monetdb version with a dbfarm created from an older version. We have just updated our system from a Jul2015-SP3 version to the latest Jun2016-SP2 version.
I have created a new db farm and plan to recreate the tables in the new farm.
My question; How do you remove the old dbfarm? Our data is quite large (1.8 T) and I¹d like to retrieve this space for other use. While I can start the db against the new farm, I can find no method of removing the old dbfarm to reclaim this space.
Thanks - Lynn
_______________________________________________ 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<mailto:users-list@monetdb.org> https://www.monetdb.org/mailman/listinfo/users-list
_______________________________________________ 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
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Thank you very much - Lynn From: Stefan Manegold <stefan.manegold@cwi.nl<mailto:stefan.manegold@cwi.nl>> Date: Monday, October 17, 2016 at 2:38 AM To: Communication channel for MonetDB users <users-list@monetdb.org<mailto:users-list@monetdb.org>>, Lynn Carol Johnson <lcj34@cornell.edu<mailto:lcj34@cornell.edu>> Subject: Re: new monetdb version, old farm Dear Lynn et al. to summarise, unless stated differently in the respective release notes, MonetDB supports database upgrades from an older to a newer version in the following cases: - from a feature release or bugfix release to a newer bugfix release of the same feature release, e.g., from the Jul2015 feature release to its second bugfix release Jul2015-SP2; - from a feature release or bugfix release to the next feature release or one of its bugfix releases, e.g., from the Jul2015-SP3 bugfix release to the Jun2016 feature release or its Jun2016-SP2 bugfix release (as in your case). We strong recommend, though, to backup your data/database(s) (i.e., dbfarm) before any upgrade. We never support downgrades from a newer to any older version of MonetDB. Feature releases are identified by a release name without "-SPx" (SP as in service pack) suffix, while the release name of bugfix releases has such suffix. Hence, between the Jul 2015-SP3 bugfix release and the Jun2016-SP2 bugfix release was the Jun2016 feature release. And: "upgrading databases" refers to continuing using the same dbfarm (exclusively) with a newer version of MonetDB. I hope, this helps to clarify. Best, Stefan On October 17, 2016 12:00:24 AM GMT+02:00, Lynn Carol Johnson <lcj34@cornell.edu<mailto:lcj34@cornell.edu>> wrote: I”m confused now. Our db has already been upgraded. We went directly from Jul2015-Sp3 to Jun2016-SP2. Was there a feature release in-between these 2? Am I ok using the same dbfarm for both these releases? I will try to schedule upgrades as the fixes come out in the future. Thanks - Lynn From: users-list <users-list-bounces+lcj34=cornell.edu@monetdb.org<mailto:users-list-bounces+lcj34=cornell.edu@monetdb.org>> on behalf of Brian Hood <brianh6854@googlemail.com<mailto:brianh6854@googlemail.com>> Reply-To: Communication channel for MonetDB users <users-list@monetdb.org<mailto:users-list@monetdb.org>> Date: Sunday, October 16, 2016 at 2:30 PM To: Communication channel for MonetDB users <users-list@monetdb.org<mailto:users-list@monetdb.org>> Subject: Re: new monetdb version, old farm Hi Lynn, Like Soerjd mentioned previously you should upgrade in sequence so try not get behind in releases. Also as I found out the hard way it's impossible to downgrade. It plays havoc with your BBP version and catalog from memory. Regards, Brian Good On Oct 16, 2016 1:21 PM, "Lynn Carol Johnson" <lcj34@cornell.edu<mailto:lcj34@cornell.edu>> wrote: To verify: You¹re saying my upgrade from Jul2015-SP3 to Jun2016-SP2 does not require a database recreation as the farm is not that old? This would be great. Thanks - Lynn On 10/14/16, 5:08 PM, "users-list on behalf of Martin Kersten" <users-list-bounces+lcj34=cornell.edu@monetdb.org<mailto:cornell.edu@monetdb.org> on behalf of martin@monetdb.org<mailto:martin@monetdb.org>> wrote:
Upgrade paths are automatic from the previous feature release, unless we have announced that a re-create is necessary due to internal changes that can not be handled automatically. Upgrades from bug-fix releases never require a database re-creation.
Upgrading over multiple feature releases, i.e. a very old dbfarm, is not supported. A dump and restore is the way to go.
regards, Martin
On 14/10/16 22:27, Lynn Carol Johnson wrote:
Hello -
My understanding is you should not run a new monetdb version with a dbfarm created from an older version. We have just updated our system from a Jul2015-SP3 version to the latest Jun2016-SP2 version.
I have created a new db farm and plan to recreate the tables in the new farm.
My question; How do you remove the old dbfarm? Our data is quite large (1.8 T) and I¹d like to retrieve this space for other use. While I can start the db against the new farm, I can find no method of removing the old dbfarm to reclaim this space.
Thanks - Lynn
_______________________________________________ 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<mailto:users-list@monetdb.org> https://www.monetdb.org/mailman/listinfo/users-list
_______________________________________________ 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<mailto:users-list@monetdb.org> https://www.monetdb.org/mailman/listinfo/users-list -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
participants (5)
-
Brian Hood
-
Lynn Carol Johnson
-
Martin Kersten
-
Stefan Manegold
-
Vincent Sheffer