JMyETL, an easy to use ETL tool that supports 10 different RDBMS

JMyETL is a very useful and simple Java based application for Windows OS which allows users to import and export data from/to various database systems. For example:

• CUBRID --> Sybase ASE, Sybase ASA, MySQL, Oracle, PostgreSQL, SQL Server, DB2, Access, SQLite
• MySQL --> Sybase ASE/ASA, Oracle, Access, PostgreSQL, SQL Server, DB2, SQLite, CUBRID
• Sybase ASE --> Sybase ASA, MySQL, Oracle, Access, PostgreSQL, SQL Server, DB2, SQLite, CUBRID
• Sybase ASA --> Sybase ASE, MySQL, Oracle, Access, PostgreSQL, SQL Server, DB2, SQLite, CUBRID
• Oracle --> Sybase ASA, Sybase ASE, MySQL, Access, PostgreSQL, SQL Server, DB2, SQLite, CUBRID
• Access --> Sybase ASE, Sybase ASA, MySQL, Oracle, PostgreSQL, SQL Server, DB2, SQLite, CUBRID
• PostgreSQL --> Sybase ASE, Sybase ASA, MySQL, Oracle, Access, SQL Server, DB2, SQLite, CUBRID
• SQL Server --> Sybase ASE, Sybase ASA, MySQL, Oracle, PostgreSQL, Access, DB2, SQLite, CUBRID
• DB2 --> Sybase ASE, Sybase ASA, MySQL, Oracle, PostgreSQL, SQL Server, Access, SQLite, CUBRID
• SQLite --> Sybase ASE, Sybase ASA, MySQL, Oracle, PostgreSQL, SQL Server, DB2, Access, CUBRID

The installation of JMyETL is fairly easy. You just need to follow a few simple steps.

First, download JMyETL and extract it. In the extracted folder, find jmyetl.ini configuration file and edit it to adjust the value of vm.location to your {JAVA_HOME}jrebinserverjvm.dll.

Make sure that the path correctly points to a jvm.dll file from a Java 32 bit version otherwise you will keep getting a "Error starting Java VM." error. Usually the 32 bit version is located in C:Program Files (x86) directory. If you already have a 64 bit version of JDK, you will also need to download the 32 bit version. The recommended JDK version is 1.6 or above.

The final confirmation file will look something like:

main.class=com.sql9.jmetl.MainFrame
classpath.1=*.jar;.
splash.image=SplashScreen.bmp
vm.location=c:Program Files (x86)Javajdk1.7.0_07jrebinserverjvm.dll
vmarg.1=-Xms64M
vmarg.2=-Xmx512M

Optionally, in jmyetl.ini configuration file you can also set the memory limitation for Java Virtual Machine (JVM). The default values are:

vmarg.1=-Xms64M
vmarg.2=-Xmx512M

Now open JmyETL.exe program. The following window will show up.

Choose SourceDB and Targetdb from the dropdown list.

For both fill out the {host}, {database}, {port} values and enter user and password information in the next two text fields. For example, CUBRID database connection URL should look like jdbc:cubrid:localhost:33000:demodb::: and user is dba with an empty password. MySQL connection URL should look like jdbc:mysql://localhost:3306/hibernate.

When connecting to a CUBRID database, make sure it has been started. For Access Database, you don't need to create the mdb file in advance. If it doesn't exist, JMyETL will create it for you.

Then click the Test Connect buttons to ensure both connection URLs are correct. If the connection has been successfully established, first, you will notice that Test Connect button becomes green. Second, on the left panel you will see a list of tables from the source database.

Now select all or some of tables which you would like to export from SourceDB to TargetDB. Once ready, click the Start Import button. Done! This will automatically create corresponding tables in the TargetDB and import all records from SourceDB.

We would like to thank Xiong He for adding CUBRID support to JMyETL. He has also reported an important bug that he had found in CUBRID JDBC driver. We have already fixed it in the upcoming (September 2012) CUBRID release.

When we contacted Xiong He to learn about his CUBRID experience, he told us that after reading the online manuals, it was not hard to add CUBRID support to JMyETL. He things CUBRID is a very strong DBMS. There were difficulties using BLOB/CLOB APIs in JDBC driver. Since LOB data in CUBRID is implemented differently, he had to implement a custom code to handle LOB data. Xiong He suggests for users who want to add CUBRID support to read the admin/dev manuals and pay attention to non-standard usages specific to CUBRID.

If you know Chinese, Xiong He manages his develop blog at http://blog.csdn.net/iihero and available on Twitter.

Information for our readers!

If you develop an open source application and would like to become a CUBRID Partner by supporting CUBRID Database in your project, contact us by email affiliates@cubrid.org. In your letter please provide an overview of your software, project links, and your statement on behalf of your project. We will be very glad to have you onboard!