How To Validate A DataPump Export (EXPDP) Dump File ? (文档 ID 2113967.1) 转到底部 -------------------

How To Validate A DataPump Export (EXPDP) Dump File ? (文档 ID 2113967.1)

转到底部

---

In this Document Goal   Solution Applies to: Oracle Database - Enterprise Edition - Version 10.2.0.1 and later Information in this document applies to any platform. Goal How to confirm that expdp dump files are valid and can be successfully imported into a target environment? Solution To validate the dump files generated by the DataPump export, run a test import with SQLFILE parameter. The SQL is not actually executed, and the target system remains unchanged. The file is written to the directory object specified in the DIRECTORY parameter, unless another directory_object is explicitly specified here. Example: > impdp username/password directory=<directory_name> dumpfile=<dumpfile_name> sqlfile=<sqlfile_name>.sql   A successful import confirms the fact that the dump files are in a consistent status. In case the SQLFILE command fails with errors, it is an indication that there is an actual problem with the dump files. Note: A. There are numerous causes as to why a dumpfile got corrupted and it may not be due to the DataPump engine. Some possible causes could be:            1. The files are invalidated by non-binary ftp transfer. If you transferred a dump file from one machine to another via FTP, make sure that the file is transferred in binary mode.            2. The transfer of the dump files from source environment to target environment has been interrupted.            3. The dump file are truncated by disk space of file system size limitations.            4. The export job has not been completed successfully. B. Unix commands (csum) or md5 can be used to ensure that the file checksum on source matches with file checksum on target.