Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
error Migrating Historical Data to the NoSQL Database
-
It looks like it'll create an empty database at the path rather than only accept existing databases. I have opened a github issue for it:
https://github.com/infiniteautomation/ma-core-public/issues/631 -
Hi Phil,
if i leave the username and pasword blank i got an error, if i have mango mango then i got the error as described above.
In the properties.env file the paswordt is blank....i dont understand the github page, what can i find there ?
-
It's just a habit of mine to acknowledge accepting some behavior as a bug with a link.
What version of the NoSQL module are you using?
-
the version that is in the mango 2.7 update, i tried to install only that module with the update function, but then i got an version check error. In the 2.5 version i use i never downloaded the no sql module.
-
Your error resembles an empty database (Or one not set up for Mango). I mentioned the github issue because the migration tool will create this empty database if your connection string has the wrong path. It will create the database with the credentials specified the first time, probably.
Please check that the path to your mango/databases/mah2 is correct in the connection string. Bearing in mind that an empty database may have been created by a migration attempt. Some other folders in the mango/ directory are web, bin, logs, and lib.
-
Hi Phil,
i finaly gave up.
i stick with V2.5 for some unknown reasson i am not able to make a migration. -
Well, if you feel like giving it another go, this still sounds like the connection string is wrong. If it doesn't detect a DATAPOINTS table, that tells me it isn't pointed to the right database.
You can also use Mango 2.7 on H2, you just have to remove the MangoNoSql module and then you can get the new features without having to cross this bridge.
-
how do i do that ?
if i use the update function, the nosql module is installed. -
If you do not have data in your nosql database, you can just delete the folder Mango/web/moduels/mangoNoSqlDatabase, or use the delete button on the modules page.
If you do have data you'd like to keep in there, there is unfortunately no very easy tool to perform the conversion the opposite direction. You'd have to export all your data to excel or csv and then reimport it after removing the module.
If NoSql wasn't installed on your 2.5 Mango, it shouldn't have the module automatically checked in the upgrades section, I believe.
-
my 2.5 version does not have the nosql.
if i email my mango folder can you perform the upgrade for me ?
i dont mind missing some date when the sun doesn;t shine here -
It doesn't set my favorite precedent. Not downloading the NoSQL module would avert the need to migrate the data, which i still believe to be the core issue of this thread (and I still believe the connection string is the origin of the problem).
If you point the migration tool at C:\mah2 or /opt/mah2 you're likely to get a blank database there. You could then delete that, knowing that the connection string points to that exact place, and copy your real database there, then run the migration again.
I would rather you played with it and found a solution, honestly. You could 1) figure out why the connect string is mistaken, 2) not use the NoSQL module, 3) run up the newest Mango in parallel on a different port and experiment with removing the NoSQL module (which is as simple as not having the module in your Mango/web/modules/ directory).
If you would like to contact Joel and attempt to purchase some direct support of that nature, you can, but I suspect for the smallness of the task the largeness of the cost will seem disproportionate.
-
just trying to update again.
my steps:
copied the content of c:\mango to c:\mango_org
in mango modules i used check for update.
selected al modules, waited for the update to take place and after a while it was done.
logged in to mango no graphical view no datapoints
in mango modules check for updates again and core v 2.7.6 was available
selected that waited until restart, log in no graphical views no datapoints.no i am really confused.
ill think i need to upgrade manualy is there a good step by step guide ?
-
It sounds like you need to clear your browser's cache, perhaps.
We do have some instructions: http://infiniteautomation.com/wiki/doku.php?id=system_admin:upgrading&s[]=upgrade#upgrade_for_windows_systems
-
ok i am getting somewhere, manual update and then the no sql migration.
now i found out that i need a license for the nosql module....
mango 2.5.2 was running perfect without the no sql, i needed the no sql for my historical data.i really cannot affort 5000 for the no sql database, do i really need it for the historicaldat after the upgrade to 2.7 ?
-
Why would you need the NoSql database for your historical data? You can start it up on your old database if you do not have the NoSql module installed and all your old data should already be there.
-
i posted a message that al my historical data was gone afer an update, i got the response that i have to do the migration to the nosql
now i understand that dont need the nosql.i will do the whole excercise again and dont install the nosql module,
ill hope that wil do the trick, -
You shouldn't have to redo anything. Deleting the NoSql module from your web/modules directory and restarting should be sufficient to use H2 for your pointValues again
