Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

while upgrading the database from verison (MonetDB-11.27.13) to (MonetDB-11.33.3) we are unable to bring up the database #6740

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2019-07-30 08:38:26 +0200
From: bharath <<bharath.thamanna>>
To: Merovingian devs <>
Version: 11.33.3 (Apr2019)
CC: @PedroTadim

Last updated: 2019-11-28 10:00:03 +0100

Comment 27192

Date: 2019-07-30 08:38:26 +0200
From: bharath <<bharath.thamanna>>

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
Build Identifier:

While upgrading the database from verison (MonetDB-11.27.13) to (MonetDB-11.33.3) we are unable to bring up the database

Error details:
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: Running database upgrade commands:
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: set schema "sys";
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: drop function sys.dependencies_functions_os_triggers();
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: CREATE FUNCTION dependencies_functions_on_triggers()
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: RETURNS TABLE (sch varchar(100), usr varchar(100), dep_type varchar(32))
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: RETURN TABLE (SELECT f.name, tri.name, 'DEP_TRIGGER' from functions as f, triggers as tri, dependencies as dep where dep.id = f.id AND dep.depend_id =tri.id AND dep.depend_type = 8);
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: updat
2019-07-29 23:33:15 MSG merovingian[450405]: database 'DB_GRM_P_B' (450467) has crashed (dumped core)
2019-07-29 23:33:15 ERR control[450405]: (local): failed to fork mserver: database 'DB_GRM_P_B' has crashed after starting, manual intervention needed, check monetdbd's logfile (merovingian.log) for details

could you help us how to migrate our databases to newer version and also we have 100+ database to migrate.

Thanks
Bharath

Reproducible: Always

Steps to Reproduce:

1.Bring up any DB running on (MonetDB-11.27.13) to (MonetDB-11.33.3)
2.
3.

Actual Results:

Thrown below error:
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: Running database upgrade commands:
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: set schema "sys";
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: drop function sys.dependencies_functions_os_triggers();
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: CREATE FUNCTION dependencies_functions_on_triggers()
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: RETURNS TABLE (sch varchar(100), usr varchar(100), dep_type varchar(32))
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: RETURN TABLE (SELECT f.name, tri.name, 'DEP_TRIGGER' from functions as f, triggers as tri, dependencies as dep where dep.id = f.id AND dep.depend_id =tri.id AND dep.depend_type = 8);
2019-07-29 23:33:11 MSG DB_GRM_P_B[450467]: updat
2019-07-29 23:33:15 MSG merovingian[450405]: database 'DB_GRM_P_B' (450467) has crashed (dumped core)
2019-07-29 23:33:15 ERR control[450405]: (local): failed to fork mserver: database 'DB_GRM_P_B' has crashed after starting, manual intervention needed, check monetdbd's logfile (merovingian.log) for details

Expected Results:

DB to be come to the latest version (MonetDB-11.33.3)

Comment 27193

Date: 2019-07-30 10:33:28 +0200
From: MonetDB Mercurial Repository <>

Changeset 07dbcfe06f1e made by Pedro Ferreira pedro.ferreira@monetdbsolutions.com in the MonetDB repo, refers to this bug.

For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=07dbcfe06f1e

Changeset description:

The history environment variable doesn't exist anymore. This should fix part of bug #6740.

Comment 27194

Date: 2019-07-30 10:40:47 +0200
From: @sjoerdmullender

If this is indeed the problem, upgrading in smaller steps should work.

That's a good idea anyway. We only tests upgrades from one release to the next. We do not test (and therefore not "guarantee" (we don't really guarantee anything)) upgrades that skip releases.

You shouldn't have to do all point releases (the SPs), but go through all major releases between 11.27.13 and 11.33.3.

Comment 27195

Date: 2019-07-30 11:43:00 +0200
From: MonetDB Mercurial Repository <>

Changeset 15b4657ff7d3 made by Pedro Ferreira pedro.ferreira@monetdbsolutions.com in the MonetDB repo, refers to this bug.

For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=15b4657ff7d3

Changeset description:

SQL upgrade code runs inside a transaction now, so there is no need to call commit inside each upgrade.

This fixes upgrade from Jul2017 to Apr2019 in bug #6740.

Comment 27196

Date: 2019-08-01 09:56:45 +0200
From: MonetDB Mercurial Repository <>

Changeset 90eb914c2b2a made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.

For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=90eb914c2b2a

Changeset description:

Backport changeset [93bd9c6b2342](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=93bd9c6b2342) 
This fixes bug #6740.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant