2.0.0.6 Database Restore Problems

[FL Coast]

Getting ready to try out RadioDJ version 2.0.0.7, so the first thing I do is backup the current database from 2.0.0.6.  according to the database utility the backup went fine.  Just to make sure, I tried to re-import the backup back into RadioDJ 2.0.0.6 and received the following message:

Completed with error(s).MySql.Data.MySqlClient.MySqlEcption (0x80004005): packets larger than max_allowed_packet are not allowed.

This is the database that was upgraded from 1.8.2 to 2.0.0.0 then 2.0.0.3 to 2.0.0.4.  RadioDJ 2.0.0.6 has been operating without error since it was updated.

I created a New Database in 2.0.0.6, imported the current database from 1.8.2 then ran the updates again up to 2.0.0.4.  I opened RadioDJ 2.0.0.6 and everything functioned fine.  Exported the fresh database and tried to re-import it back into 2.0.0.6 and had the same problem!     And YES, it was all done as "Run As Administrator".

This is on my test machine and the only copy of 2.0.0.6 running at the time since I am still using 1.8.2 on my playout machine. Anyone have any Ideas?

Thanks in advance for the help.

Wayne

[Marius]

If you are collecting the history for long time, the database will become very large and at a point it will exceed a setting named "max_allowed_packet" from MySQL server.
It's pretty tricky to change it. Some say that running the following query will change that setting to 1GB:

Code Select Expand

SET GLOBAL max_allowed_packet=1024*1024*1024;
In my case it didn't worked despite the fact that i got the confirmation that the setting was changed.

The only workaround that worked for me was to create a file named "my.ini" in the "MySQL\data folder" with the following content:

Code Select Expand

[mysqld]
datadir=G:/08 - Server/MariaDB/data
port=3309
sql_mode="STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION"
default_storage_engine=innodb
innodb_buffer_pool_size=443M
innodb_log_file_size=50M
character-set-server=utf8
max_allowed_packet=1024M
[client]
port=3309

However, notice the first line, that is pointing to my location of "data" folder, which you should change it to your path.
PS: I recommend you to make the file changes with the MySQL server stopped (on Windows 10 search for "services" and in the services window locate MySQL and press stop the service) and after the changes, start again the service.

[FL Coast]

Hi Marius,

Neither one of those options worked for me.  It shows exporting the file and reports back the "Backup Complete".  But when I open the folder where the file is, the file size is only 574 KB where the original import from 1.8.2 was 10,489 KB. So the problem is with the export.

My work around to get 2.0.0.7 going was to import the same 1.8.2 backup into 2.0.0.7 and do the database updates to current version.  That worked. 2.0.0.7 is up and running. So I decided to export the 2.0.0.7 database to see if it would import back in, but that backup size was also 574 KB.  Not sure what is going on?   

Wayne

[rkriggs]

I would double check and make sure I am updating and exporting the same file.. I would go and delete all other backups.. maybe back up to the desktop to tb be certain. and then restore from the desktop..
At this point try anything.
Randy