Page 1 of 1

Schema Version Difference

PostPosted: Wed Jul 22, 2015 5:25 am
by GDelkos
Hello there again.
First of all my specs:
ViciBox Redux v.6.0.3-141118
VERSION: 2.12-496a
BUILD: 150710-1120

Version: 2.4b0.5
SVN Version: 2336

I made a backup from a server that i had and tried to restore it to a new one (bigger machine).
The only problem i am facing is the DB schema everything looks and works good the only thing that its not is the difference on the DB schema and i get on Admin >>>System Settings this warning : DB Schema Version: 1416 WARNING: Code expects different schema: 1420.
Now on the Admin Interface i can see everything but i cant see the Users and i cant add or edit them as they are empty.
I would like to fix this and before posting here i tried to upgrade it using mysql -u root -p < updateXXX.sql starting from 2.6 and going all up to the latest one but i cant seem to get it working.
I would love to solve this and every help or info would be deeply appreciated.

Edit: on my phpMyAdmin or mysql i see everything there and correctly so i can only imagine that through the difference of the schema the queries that the GUI uses are not working correctly.

Thank you in advance

Re: Schema Version Difference

PostPosted: Wed Jul 22, 2015 9:19 am
by mflorell
If the admin.php says you are on version 1416, then you are missing the last several schema changes. Make sure you do an svn update then manually check the extras/upgrade_2.12.sql file for the schema version and run the missing ones manually if you have to.

Re: Schema Version Difference

PostPosted: Thu Jul 23, 2015 10:19 am
by GDelkos
i am looking at /trunk/extras/ on my upgrade_manifest.txt and i have

upgrade_2.0.5.sql 1074
upgrade_2.2.0.sql 1135
upgrade_2.4.sql 1193
upgrade_2.6.sql 1316
upgrade_2.8.sql 1347
upgrade_2.10.sql 1378
upgrade_2.12.sql 1403

sadly i need to take my schema to 1420.

any ideas ?

thank you in advance!

Re: Schema Version Difference

PostPosted: Thu Jul 23, 2015 10:39 am
by mflorell
That file shows the STARTING schema numbers, have you actually looked in the upgrade_2.12.sql file?

Re: Schema Version Difference

PostPosted: Thu Jul 23, 2015 10:44 am
by GDelkos
yes i have seen it and i know the last one is the 1420 but i cant come to that version cause using :
mysql -u root -p asterisk < upgrade_2.12.sql will throw me a error.

Re: Schema Version Difference

PostPosted: Thu Jul 23, 2015 10:50 am
by GDelkos
:ERROR 1060 (42S21) at line 5: Duplicate column name 'meetme_enter_login_filename'

Re: Schema Version Difference

PostPosted: Thu Jul 23, 2015 10:54 am
by GDelkos
also another weird thing is this on my login on the machine after the vicibox version

/usr/bin/manpath: can't set the locale; make sure $LC_* and $LANG are correct

weird things that i never had before thats why i am bit worried.

Re: Schema Version Difference

PostPosted: Fri Jul 24, 2015 6:24 am
by mflorell
I can't say I've ever seen those issues before. That would cause me to wipe and reinstall.

Re: Schema Version Difference

PostPosted: Fri Jul 24, 2015 6:40 am
by GDelkos
thank you firstly for the reply i managed to update my schema version by running just the last line of the upgrade_2.12.sql everything works fine but still i got that- ViciBox Redux v.6.0.3-141118
/usr/bin/manpath: can't set the locale; make sure $LC_* and $LANG are correct

Re: Schema Version Difference

PostPosted: Thu Jul 30, 2015 8:50 pm
by williamconley
Did you verify that this server was functional (in autodial and manual dial) before attempting the restore?

Re: Schema Version Difference

PostPosted: Tue Aug 04, 2015 3:52 am
by GDelkos
yes it was! fully functional i will wipe it tonight!

Re: Schema Version Difference

PostPosted: Thu Aug 27, 2015 9:27 pm
by williamconley
When I upgrade a Vicidial database, I always delete the "already run" mysql commands from the first upgrade file before I begin. IE: If the server is at schema 1388, I will delete the mysql lines that precede the one setting the schema value to 1388 before executing the file.

This has likely saved me hundreds of "challenges" with conflicts over the years. Note that it is pretty easy to kill a mysql file by attempting to add a column ... if the column was already added, same with indexes and with many other modifications. But if you start executing at the statement that sets the schema to the schema you are ON right now ... you've got pretty good odds. And we've NEVER had a conflict since I started doing that except with some freaky goautodial servers (or those who customize their DBs! LOL 8-) )

Re: Schema Version Difference

PostPosted: Tue Sep 20, 2016 1:03 am
by Sathiya
Hi,

I'm also facing the same mysql error while migrating the Vicidial database from 2.8 to 2.12. Kindly let me know how you fixed the issue.

========
RROR 1060 (42S21) at line 5: Duplicate column name 'meetme_enter_login_filename'
========

Thank You.

Re: Schema Version Difference

PostPosted: Tue Oct 18, 2016 8:37 pm
by williamconley
Sathiya wrote:Hi,

I'm also facing the same mysql error while migrating the Vicidial database from 2.8 to 2.12. Kindly let me know how you fixed the issue.

========
RROR 1060 (42S21) at line 5: Duplicate column name 'meetme_enter_login_filename'
========

Thank You.



When I upgrade a Vicidial database, I always delete the "already run" mysql commands from the first upgrade file before I begin. IE: If the server is at schema 1388, I will delete the mysql lines that precede the one setting the schema value to 1388 before executing the file.