Hi All,
I'm in the process of testing a migration of my database (14 Gig of it) from 1.6 to 2.
I have dumped out the database from the production server and have updated it to the 1.8 schema on a separate system.
I then hit bug ZBX-5125 when taking it up to the 2.0 schema. I guess the SQL script has run as far as line 695, where the errant SQL line is, and then it quit..
There is a work around described here -> https://support.zabbix.com/browse/ZBX-5125
Am I safe to apply that work around and then run the 1.8 to 2.0 upgrade again on a partially upgraded db? Would running the script again be a stupid idea?
Or should I adapt the script to continue from where it stopped, after applying the fix?
Thanks
Ken
I'm in the process of testing a migration of my database (14 Gig of it) from 1.6 to 2.
I have dumped out the database from the production server and have updated it to the 1.8 schema on a separate system.
I then hit bug ZBX-5125 when taking it up to the 2.0 schema. I guess the SQL script has run as far as line 695, where the errant SQL line is, and then it quit..
There is a work around described here -> https://support.zabbix.com/browse/ZBX-5125
Am I safe to apply that work around and then run the 1.8 to 2.0 upgrade again on a partially upgraded db? Would running the script again be a stupid idea?
Or should I adapt the script to continue from where it stopped, after applying the fix?
Thanks
Ken
Comment