Q: If there is an expression in ‘Default’ clause of a table column in the source database, what can I do? For example: There is a table defined as “create table a1 (f1 varchar(120) default to_char(sysdate,’yyyy’))” in an Oracle DB.
A: Before CUBRID 9.0.0.x, a table column’s ‘Default’ value must be a constant value, so users should change this expression to a constant value in column mapping UI.
Q: If i want to export many SQL tables into one file, what should i do?
A: There are two ways: One is unchecking the option "One table one file" which is in the second step of migration wizard; Another way is changing the SQL tables' target name to same, for example:
Q: How to create a migration script and run it in the migration console tool?
A: First of all, at the confirm page, you can find a button "Export Script" as follows,
Clicking it will pop a saving dialog and you should specify a XML file which the migration configurations will be saved into.
Then you should copy the XML migration script file to the remote server where you want to run it.
Make sure that the migration console tool has been installed in the remote server.
Call the migration.bar(windows) or migration.sh(linux) and send the full name of the migration scirpt file as its latest parameter. For example:
You can add "-sd" parameter to specify the source database's JDBC driver file, For example:
"migration.sh -sd /home/cubrid/jdbc.jar /home/cmt/console/migration_script.xml"
You can add "-td" parameter to specify the target database's JDBC driver file, For example:
"migration.sh -td /home/cubrid/jdbc.jar /home/cmt/console/migration_script.xml"
You can add "-tp" parameter to specify where the output files will be saved if you have set the target is CUBRID dump/CSV/SQL/XLS files, For example:
"migration.sh -tp /home/cubrid/output /home/cmt/console/migration_script.xml"