Data loss caused by incorrect Excel column format during database migration-Oracle-Datapump

Data loss caused by incorrect Excel column format during database migration-Oracle-Datapump cause: export data from the old SQLServer database to Excel and save the data as a file in DBase 3 format using Excel, use Datapump to change DBase III (*. dbf. Www.2cto.com all went smoothly, but after a week of basic data migration, many records with a total material usage of 0 were found on the new application interface. How is it possible? If the total usage is 0, it indicates that the materials are not used. Such materials are certainly not stored in the database. Process: 1. After all, we finally find that there are many records with a total usage of 0 in the Oracle database. If this is 0, the data will be migrated once, and the processing result will certainly be 0. 2. Continue tracing and find that there is no zero record in the Excel data file exported from SQLServer. 3. However, it is found that 0.017 of the data used is converted to data in the format of 1.70E-02 (this is also true in dbf). Therefore, it is suspected that Datapump cannot recognize such a data format. Www.2cto.com 4. Change the format of the data column from scientific notation to regular. It will take a long time to re-convert the data column and then be normal (simply put, it will take almost a week). Conclusion: 1. Data verification is very important, including the format (because, after all, we want to use ready-made tools, which do not guarantee the business nature of data ). 2. sort and sort operation logs during database migration so that you can repeat them again in case of an accident. 3. database migration is not as easy as you think. Author: noodle123