Here you can select build a new data export operation or execute data export operation accord the prior-saved export configuration file.
If you select execute export operation accord the prior export configuration file, you should click the Select Config File button to select the prior-saved export configuration file. Attention, if you execute export operation by prior-saved export configuration file, you will cannot change the export type, source database connection url and properties, and target database connection url and properties, but you can reselect the tables or views you want to exported.
After do this step, please click the Next button to go to the next step.
Here you can select the export type, for example, select the source database and the target database or table format.
If you have built the source database connection , you cannot change the export type when you return this step by click the prior button .
After do this step, please click the Next button to go to the next step.
Here you should assign which Driver Config used for building the source database connection.
All the Oracle JDBC Driver configs configged before will be showed in the JDBC Driver list,
After you have selected the JDBC Configs, the window will show the information about this JDBC Configs, and show a JDBC URL example for build a connection, and the properties you can set when build connection.
Input the url and the properties, then click the Next.
After do this step, please click the Next button to go to the next step. This application will try to build the source database connection, if cannot build connection successly, it will show a dialog to tell you why cann't build the connection
After you have built the source database connection , you cannot change source connection information(JDBC URL or connection properties). So, if you want change database connection url or properties, you must open a new export window.
Here you should assign which Driver Config used for building the target database connection.
All the dBASE, Foxbase, Foxpro, and VFP JDBC Driver configs configged before will be showed in the JDBC Driver list.
After you have select the JDBC Configs, the window will show the information about this JDBC configs, and show a JDBC URL example for build connection, and the properties you can set when build connection. Here you should assign the target dBASE, Foxbase, Foxpro, and VFP database connection url and properties.
After do this step, please click the Next button to go to the next step. This application will try to build the target database connection, if cannot build connection successly, it will show a dialog to tell you why cann't build the connection
After you have built the target database connection , you cannot change target connection information(JDBC URL or connection properties). So, if you want change target database connection url or properties, you must open a new export window.
The first step, you should select the schema. All schemas your connection can access will show in the Select Source Catalogs List. If you change the selected item at this list, you will find the tables in "Table List" would change, it will list all tables owned by your selected schema.
If you are using the Enterprise version to export, here you can export data from view. Just click the show all views checkbox, it will show all views in the schema you selected. Attention, DBF(or Foxpro,DBase), Paradox, Text(CSV), Excel don't support VIEW.
show this is a table
show this is a viewYou should assign the selected table would export to which catalog or schema in target database. All catalogs will been showed in the "Select Dest" list.
The >> button(
)
will export the tables/views your selected in the source list to the target
.The >>> button(
)
will export all tables/views in the source list to the target .The << button(
)
will remove the export items you selected .The <<< button(
)
will remove all export items .You must select at lease one table or view to execute export operation.
You can modify table structure when the target table doesn't existed in target database or view the table structure by click the Modify button.
If there are multi table exported to one same table which doesn't existed and you want to change the table structure which would created in target database, you just and should click the Modify of the first export item which export to the same target table, or else, it will auto create the table and your setting will ignore.
You can chenge the order in the Export Item List, but is only change the order for see and not change the export operation order. It means, this program will always export the first table your selected to export, and then the second.
You can execute export operation even if the source table and target table have the diffirent columns' count, but you can assign one column will export to which column, the first column in source table always export to the first column in target table.
The image left the export item shows the information about the export item.
It will tell you if export item exported to a new table or existed table, if this table export to multi target table, or other table will export to the same target table, and data compatiable accord the table structure ( for example, varchar2(20) can export to varchar(20) safely, varchar2(20) can export to varchar(5) but lose some data, varchar2(20) can export to numeric(10,2) but maybe produce error).
After you confirm all export item is correct, you can click the "Next" button in the bottom panel to execute export operation.
This step will execute the export operation .
Here you can config whether continue export the rest table when error happened in the procedure for exporting tables, if you set continue export the rest table, you can config whether export the rest records of the table when error happened.
Only after you check "Continue export the other table when error happens", you can checked "Continue expor the rest records when export a record failue".
The "Continue export the other table when error happens" checkbox is used to set whether continue export the rest tables when error happened. The "Continue expor the rest records when export a record failue" checkbox is used to set whether export the rest records of the table when error happened.
OR DEFINED(Oracle2Text) OR DEFINED(Oracle2Excel) You can set how to handle the BFILE column type if this column type exists in the export tables. In default, this data in BFILE column will export to the table as a BLOB field. You can set saving the data in BFILE column to a directory, the filename will named as nn@tablename_filename (nn i s the rownum of this record in the table) .
OR DEFINED(Oracle2Text) OR DEFINED(Oracle2Excel) If you check "Oracle BFILE type save to local disk" checkbox,you can and should click the set button and assign where the BFILE type data should save.
After you configed,you can click the "Do Export" button,it will show the last dialog to let you confirm whether really export data, if you click the "Yes" , the export procedure will execute and the exporting information will show in the textbox.
After complete export operation, you can find the Prior button is contained enabled , so you can return the prior steps, and reselect the tables or view for export. Maybe it is unnecessary, but if you forget to export some tables, it is useful.
You also can click the "Save config to a file" button,it will show a save file dialog to let you choose a file name to save this export config for next usage. If you do so, then you can do export accord this config file in GUI application(Here for detail) or NON-GUI application(Here for detail).
