Greetings, Long ago i used MySQL Migration Toolkit to migrade from MS Access to a simple .sql file, and i remenber it had many source and destination options. The latest Toolkit for windows has many sources, but only MySQL as destination, and it won't allow Agent-based migration. Maybe i have a wrong version?
I tried the "Generic x86/64 Linux TAR (bundled dependencies)", which needed some changes but didn't work: - with JRE_LIB_BASE set to "/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/" i got: The connection to the MS Access database could not be established. The following error occured. "sun.jdbc.odbc.JdbcOdbcDriver" "java.net.URLClassLoader$1.run(URLClassLoader.java:217) java.security.AccessController.doPrivileged(Native Method) java.net.URLClassLoader.findClass(URLClassLoader.java:205) java.lang.ClassLoader.loaPress enter to continue. - with JRE_LIB_BASE set to "/usr/lib/jvm/java-6-sun-1.6.0.16/jre/lib/amd64/" i got: The connection to the MS Access database could not be established. The following error occured. "[unixODBC][Driver Manager]Data source name not found, and no default driver specified" "sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6957) sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7114) sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(JdbcOdbc.java:3073) sun.jdbc.odbc.JdbcO ...both using ./run_migration and ./run_migration_simple. I did some searches in the repos but found very little on unixODBC and Access, and the mysql site isn't exactly easy to search... I've also done an apt-get dist-upgrade a few days ago so i assume all the Java stuff i loathe is up to date. I remember i was really pleased with MySQL's Migration Toolkit and all its options but now i'm kind of stranded. The destination DB will eventually be MySQL[1], but i'd like to use a .sql file so i can make all the changes i want to. It's not a direct migration, i must adapt the source/destination schemas and to 'migrate' from the horrid latin1_sweedish_ci (or anyway Access's latin1) to my utf8_bin in the process. I'm only specifying the .mdb file in the scripts, skipping username/pass and conn string. The file has 666 perms and, except for 3 pop-ups warning about insecure objects, opens without issues. Trying to open the .mdb with OpenOffice kinda freezes it. Can anyone suggest a workaround for this *or* another tool to do the job? Thanks, Nuno [1] in that case i'd have to open the server up to external connections and expect the XP VM to handle it properly which isn't happening - only sees the 'Net, not LAN... weird virtualbox stuff i haven't figured out yet -- () ascii-rubanda kampajno - kontraŭ html-a retpoŝto /\ ascii ribbon campaign - against html e-mail -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
