URGENT - EXPORT IMPORT PROBLEM
Posted on 2003-02-27
1) We have DB2 7.2 EE server on win NT 4 and 2000.
2) We have received a non-delimited ascii text based file of data exported from remote source database table.
3) The table at both ends has same structure which cannot be changed i.e. 8 columns of integer, varchar, decimal, date and char(1) variety. The last column is of char(1) variety. There is no primary & foreign key and check constraints and all are not null.
3) We tried to import it but since data was missing for the last column it failed. Now if there was a default value it would have succeeded.
4) The date format of data in ascii file was not available in drop down of date while importing. So, we edited the ascii file to match one. If we keep date, timestamp and datetime drop downs as null, what happens. Will DB2 understand the date from start and end co-ordinate. What if we choose timestamp/datetime and there was no time component in ascii date values.
5) So we assumed that there will be a space(s) there and created a single space in text pad and imported using positional co-ordinates for the columns and were successful.
6) There were 2 rows only in the ascii file but it showed 4 rows imported, 2 successful and 2 failed. We found that correct data is imported in command center. In control center, for varchar columns data appeared as 123,456,789 instead of 123456789 in ascii file. In CLP, all
data is okay but last column(char(1)) shows value 4 for all rows which is incorrect.
7) Why is this difference in display and which do we beleive to be correct data in the table.
8) Now we tried to export data in table as to how it appears in ascii file. To our surprise, there is no non-delimited ascii file as an option. Then how come such a file was exported from remote source database table. Could this be a difference in VERSION/TYPE/PLATFORM(OS) of DB2 that they are having w.r.t. us.
9) I know that .ixf dump files are not portable across platforms but ascii text based files are. Will there be difference in export/import features across VERSION/TYPE/PLATFORM(OS).
10) Will export from higher version source be acceptable to lower version target or the other way round?
11) Will LOAD be more useful in this case over IMPORT.
12) There is a worksheet format(WSF) also for export/import. Worksheet means MS-Excel which has extension of .xls. Then how come .wsf.
13) Export/import of .ixf was successful at our end itself. Do you think next time round, if they send a .ixf dump from remote source database table, there are higher chances of it getting imported at our end. What will be effect of VERSION/TYPE/PLATFORM(OS) of DB2 differences from source to target in this case.