[cseymour]

Hi Peter,

Just a quick follow-up. Hosting company ran the script and all is working fine now.

Thanks again for your help.

Cheers.

Chris

[cseymour]

Hi Peter,

Thanks for looking into that for me. I will touch base with my hosting company and see if they have run the script you have mentioned.

Thanks again for you help.

Best regards.

Chris Seymour

[cseymour]

Hi Peter,

Here is the dump files I have created from the remote and local copies of the database I was trying to synch.

Thanks for looking into this for me.

Cheers.

Chris

[cseymour]

Hi Peter,

I uninstalled version 5.22 Enterprise and re-installed version 5.0 enterprise.

I am able to Synch the databases as I had in the past.

I am using MySQL version 5.0.24a on Windows and the same version is on a Linux remote host.

Thanks.

Chris

[cseymour]

peterlaursen wrote on Jan 23 2007, 05:50 AM:

“the database I am trying to synch with does not contain the table mysql.proc”

If that is the situation with MySQL 5.x, then you have probably upgraded the server from a previous version (and did incorrectly!) and you should absolutely run the “mysql_fix_privilege_tables.sql” script! You always should when performing a major upgrade of the MySQL server. Read the MySQL docs on how to upgrade MySQL. But basically you can do this (on Windows):

1) Find the “mysql_fix_privilege_tables.sql” file (in the /scripts -folder).

2) Copy to C:

3) Start mysql command line client

4) Execute “source c:mysql_fix_privilege_tables.sql”

(you cannot use SQLyog because the script generates a lot of errors and SQLyog will abort!)

5) It is consider 'good practice' to 'check/repair tables' after that. You can do from SQLyog.

The most recent MySQL versions ship with a 'mysql_upgrade' program (in the /bin -folder) that does this automatically.

I cannot tell for sure if this is the porblem here (will need a complete test case). But with a `mysql` database that has not what tables and columns it should have for a specific MySQL version, we cannot guarantee anything!

Thanks Peter,

The remote database is on a hosted provider, so I probably will not get access to the main MySQL database. But I have run , as you suggested.

I tried to do a synch and got the same error. Is there anyway to determine what database is being found as missing the mysql.proc table (local or remote)?

Thanks.

Chris

[cseymour]

peterlaursen wrote on Jan 22 2007, 09:21 AM:

is there a LETTERCASE mismatch between two tables on the server(s)?

like 'tablename' and 'TABLENAME' ??

We know that this is an issue, but we have not yet quite decided on the future of how to handle such LETTERCASE issues with the SYNC tools.

No, the funny part is the database I am trying to synch with does not contain the table mysql.proc.

Thanks.

Chris

[cseymour]

Thanks Ritesh,

I think I need to use the same version as my Prod machine on my desktop.

Thanks again.

Can't tell you how much sqlYog has helped me. Best money I have ever spent.

Thanks.

Chris

[cseymour]

Sure,

Here is what I am getting if I export a table to a script:

drop table if exists `test1`;

CREATE TABLE `test1` (

`col1` int(11) NOT NULL auto_increment,

`col2` int(11) NOT NULL default '0',

PRIMARY KEY (`col1`),

KEY `col2` (`col2`)

) TYPE=ISAM;

This is fine if I import it to my test machine (MySQL4). However in Prod we still have MySQL3 and it does not seem to like the '' around the field names.

I go in and manually edit the script now, but was wondering if there was a seeting somewhere to turn it off when the script is generated.

Thanks.

Chris

[Author]

Posts