NetXMS 2.2.6 DB Upgrade Fails

Reply to NetXMS 2.2.6 DB Upgrade Fails on Wed, 13 Jun 2018 01:46:06 GMT

Staj — Wed, 13 Jun 2018 01:46:06 GMT

We're using MariaDB, ALTER TABLE eventually failed, we just cleared the table in the end.
It would be useful if nxdbmgr check [check.cpp CheckDatabase() ?] would do a schema sanity check to see if the database matches the version is claims to be, I don't think it does this?

Reply to NetXMS 2.2.6 DB Upgrade Fails on Tue, 12 Jun 2018 05:11:09 GMT

Tursiops — Tue, 12 Jun 2018 05:11:09 GMT

Hi,

Not sure what database system you are using. Just adding the column to the table did not take any time at all in our case despite the 100+ million rows (we're using Postgres). It was the subsequent updating of the column with actual data that took forever. Probably more of a developer question at this point, as other db systems might behave differently?

Cheers

Reply to NetXMS 2.2.6 DB Upgrade Fails on Tue, 12 Jun 2018 04:40:46 GMT

Staj — Tue, 12 Jun 2018 04:40:46 GMT

After looking at upgrade_v22.cpp I think I know what happened.
When the installer automatically tried to upgrade the database, it got stuck on ALTER TABLE syslog ADD zone_uin integer which caused the installer to exit abnormally and the subsequent errors from that.
I believe this happened because the syslog table is so large that ALTER TABLE syslog ADD zone_uin integer was taking a long time and the installer didn't like that too much. Is there an installer option to run the install without it doing the database upgrade within the installer? I think we'd prefer to run it manually ourselves in the future.

Reply to NetXMS 2.2.6 DB Upgrade Fails on Tue, 12 Jun 2018 03:25:31 GMT

Staj — Tue, 12 Jun 2018 03:25:31 GMT

Unfortunately it doesn't (continue from where it left off) and the system remains down. Message remains the same on reruns, I'm running nxdbmgr.exe online-upgrade -t -X now.

Reply to NetXMS 2.2.6 DB Upgrade Fails on Fri, 08 Jun 2018 05:19:28 GMT

Tursiops — Fri, 08 Jun 2018 05:19:28 GMT

No sure about that one.
After the db upgrade I started our server and triggered the online upgrade. It ran in the background for about three days (we have tables with 100+ million rows), but finished ok.
I am assuming the database connection didn't drop out during the upgrade?
From what I understood, it should be safe to re-run the online-upgrade. It is not altering tables, but populating the new zone_uin fields with the correct data, so should just pick up where it left when it failed.

Reply to NetXMS 2.2.6 DB Upgrade Fails on Fri, 08 Jun 2018 02:42:23 GMT

Staj — Fri, 08 Jun 2018 02:42:23 GMT

You were right, I tried again with the -X flag and it finished (more or less) but it says an online-upgrade is still required (which fails)

C:\NetXMS\bin>nxdbmgr.exe online-upgrade -t
NetXMS Database Manager Version 2.2.6 Build 9513 (2.2.6) (UNICODE)

>>> SELECT var_value FROM metadata WHERE var_name='PendingOnlineUpgrades'
Running online upgrade procedure for version 22.21
Updating zone UIN in table alarms...
Updating zone UIN in table event_log...
Updating zone UIN in table snmp_trap_log...
Updating zone UIN in table syslog...
Online upgrade procedure for version 22.21 failed
>>> SELECT var_value FROM metadata WHERE var_name='PendingOnlineUpgrades'

WARNING: Online upgrades pending. Please run nxdbmgr online-upgrade when possible.

Reply to NetXMS 2.2.6 DB Upgrade Fails on Thu, 07 Jun 2018 12:19:50 GMT

Tursiops — Thu, 07 Jun 2018 12:19:50 GMT

That looks like it already tried the upgrade once before. The zone_uin column didn't exist in the alarms table until 2.2.6, so there shouldn't be a duplicate column.
Not sure if it's safe to simply drop that column from the database manually, so the upgrade can re-add it - or if you need to restore your database to a stage prior to the first upgrade.