Hi, if this can help (I faced the same kind of issue as I forgot to run the updatedb stuff after upgrading...) here is a small procedure I tested on production environments to update the DB schema and structure to your current NeDi files and scripts version.
1/ Identify the current version of NeDi DB
Go to System/Database, find the System table and click on Show icon (eye icon) and take a note of the current NeDi DB structure version.
All the trick is done by replacing your current /nedi/inc/libdb.pm with an older version so that this older version will do the required database upgrade for you without touching the other NeDi files.
I have attached to the post the original libdb.pm files for NeDi version 1.7 and 1.8.
If you prefer to extract them on your own, you have to download the NeDi install files for both 1.7C and 1.8C from
www.nedi.ch, extract them and get the libdb.pm in the /inc directory.
2/ Please make a backup of your current libdb.pm file:
# cp -p libdb.pm libdb.pm.bak
3/ Stop all NeDi active background processes.
4/ If your current version of NeDi (files and scripts) is 1.8:
If the version shown in the NeDi DB is 1.6xx or 1.7
--> copy libdb.pm.
1.7 to /nedi/inc/
Replace the current libdb.pm with the libdb.pm.
1.7 file:
# cp libdb.pm.
1.7 libdb.pm
Go to the NeDi web interface in System/NeDi and select "reset" after making sure that the login field contains "updatedb" and then execute.
The DB should update correctly to the 1.7.100 version
Then, copy libdb.pm.
1.8 to /nedi/inc/
Replace the current libdb.pm with the libdb.pm.
1.8 file:
# cp libdb.pm.
1.8 libdb.pm
Go to the NeDi web interface in System/NeDi and select "reset" after making sure that the login field contains "updatedb" and then execute.
The DB should update correctly to the 1.8.100 version.
Do not forget at the end to recover your original libdb.pm file:
# cp libdb.pm.bak libdb.pm
Hope this will help you and will avoid you to go through all files upgrade process that is very impacting if you made any customisation to your def files...