You can probably use SQuirreL SQL client (in Java) to export tables and then import them into MySQL via JDBC . I doubt there is a ODBC method of doing what you need.
Also, you could export the SQL database to a CSV file and then import to MySQL using the command:
LOAD DATA LOCAL INFILE C:\test.csv
INTO TABLE tbl_temp_data
FIELDS TERMINATED BY ','
LINES TERMINATED BY '\r\n'
I think I see the problem
You have the following in your question:
Replicate_Do_DB: db1; db2
That is not supposed to be a semicolon-separated list. It is supposed to be a comma-separated list.
My guess is your have this in your slave's /etc/my.cnf
replicate-do-db=db1; db2
The correct way to set this up is
replicate-do-db=db1
replicate-do-db=db2
Please adjust this in the slave's /etc/my.cnf and restart mysql on the slave
Give it a Try !!!
UPDATE 2011-10-31 15:20 EDT
You may want to clear out the relay log by doing this
STOP SLAVE;
CHANGE MASTER TO master_log_file='mysql-bin.000008',master_log_pos-98;
START SLAVE;
then run SHOW SLAVE STATUS\G and make sure replication is running by making sure you see this
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
just as you posted in your question
Best Answer
With Mysql Community server (common version), it is possible to setup replication of databases.
It could be set as master-slave or master-master. The best guide I've seen for those are Master-Slave replication howto and Master-Master replication howto.
The option chosen mainly depends on whether you need your second server to be able to do updates to the DB. A master-master replication requires a bit more effort to implement and to troubleshoot, but is as stable.
Note that this does not allow to select tables, just the database. Doing that would require custom replication (outside the database engine) which would be slower and less reliable than the built-in option.