• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

MySQL database migration problem (auto_increment)

T

tmr_leon

Guest
We recently had to migrate our sites off of a Linux machine that we rebuilt, so we used the migration manager to move sites from the Plesk 8.1.1 installation in it to a temporary server that has Plesk 8.2.1.

When the time came to move the sites back to our freshly-rebuilt server, which now hosts Plesk 8.2.1, we started encountering database errors.

Upon inspection, it seems that the auto_increment property of the MySQL tables aren't being set. We didn't experience this in the 8.1.1 -> 8.2.1 move. Only now, with a migration from 8.2.1 -> 8.2.1.

It would be a real pain to have to manually do mysqldumps to migrate the databases one by one, as we have a lot in the server. Has anybody who's experienced this problem found a solution that would fix the migration manager's behavior?
 
Found a fix

After a little searching, I found this:

http://forum.swsoft.com/showthread.php?s=&threadid=43750&perpage=15&pagenumber=1

Though the posts were about MySQL4 -> MySQL5 migrations, I thought I'd try it out since the symptoms were the same.

And it worked.

To summarize, here is what I did:

1. Open /usr/local/psa/PMM/agents/shared/Db/MysqlShellBackend.pm in an editor.
2. Search for "mysql323". Search should reveal only one instance of the string in that file. In my case, it was at line 85.
3. Commented out the line by putting a "#" at the start of the line.
4. Redo my migration.

I found the solution in the Plesk 8.1 forums. Though the original posts talked about MySQL4 -> MySQL5 migrations, it's sad that this problem made it through to Plesk 8.2.1 in a MySQL5 -> MySQL5 migration.

Anyway, hope that helps somebody.
 
This totally screwed me with wordpress not being able to post on any of my domains.
 
This totally screwed me with wordpress not being able to post on any of my domains.

Hi, what exactly broke wordpress? Migration or recommendations from tmr_leon?
What error do you get when trying to post on a domain?
 
after a migration using 8.2.1, all of the software on my domains (such as wordpress) that relies on the auto_increment field in a MySQL database broke. Any feature making use of auto_increment (for example, the ability to create a new post) was unusable.

I dug around in the databases and compared them to another host and discovered that the failure to correctly copy this attribute on any of the databases for any of the domains was the problem.
 
You can try using solution suggested by tmr_leon to migrate databases with auto_increment.
 
Update on this issue to help people find it

After spending a full day and several hundred dollars we found and fixed this issue, but we did not find it searching on the errors we were getting, so I am adding them here in the hopes of helping others.

We did a migration from Plesk 8.1 to 8.3 and had lots of trouble with mysql. The one db that we manually dumped and imported worked fine. That gave us a clue and we finally figured out the problem. What I don't understand is if this bug has been around for a while, why haven't they fixed it or added info to their documentation? This has been an absolute nightmare.
mySQL query error: INSERT INTO xxx

... more codes here ...

mySQL error: Duplicate entry '0' for key 1
mySQL error code:
Date: Monday 17th of March 2008 03:06:54 PM
 
Same problem using migration manager from 8.2.1 to 8.3.0
Ths bug made it to 8.3 also, i'm still histeric about this! o god! pleeeeaase swsoft/parallels, try your things!! omg
 
They don't even have to try it, just read their own forums. Bugs happen, but it is dissapointing to know they have so little regard for their clients that the same reported bug would be in several consecutive versions.
 
Migrating almost any data

I use data loader for migrating almost any data, it helps me to convert MSSQL to MYSQL, MS access to MSSQL, mysql, csv loader, foxpro and MSSQL to MS access, MYSQl, CSV, foxpro etc. In my view this is a best Data Migration Tool


Download Free : http://www.dbload.com
 
Back
Top