How to Validate and Verify Oracle Dump Files for Corruption

You received a .dmp file from another team or vendor, tried to import it, and got errors. The first step is to verify whether the file is corrupted.

This article covers several methods to validate .dmp file integrity.

Common Causes of Dump File Corruption

• Transfer errors: FTP not set to binary mode, incomplete downloads, network interruptions
• Export interruption: Disk full, process killed during export
• Split/merge failures: Incorrectly reassembled split files
• Compression errors: Extraction from corrupted ZIP/GZIP archives

Method 1: Validate with OraDB DUMP Viewer (Recommended)

The quickest and most reliable method. No Oracle environment needed.

1. Open the .dmp file in OraDB DUMP Viewer
2. Check:
   • Does the file parse without errors?
   • Does the schema and table tree appear?
   • Can you preview table data normally?
   • Is the dump format (EXP/EXPDP) correctly detected?

Diagnosis:

• ✅ Table tree displays, data preview works → File is OK
• ⚠️ Some tables unreadable → Possible partial corruption
• ❌ Can't open file, parse error → Corrupted or unsupported format

Method 2: File Size and Checksum Verification

Basic integrity check by comparing before and after transfer.

File Size Comparison

# Source (Linux)
ls -la export.dmp

# Destination (Windows PowerShell)
Get-Item export.dmp | Select-Object Length

Size mismatch = incomplete transfer.

Checksum (Hash) Comparison

# Linux
sha256sum export.dmp

# Windows PowerShell
Get-FileHash export.dmp -Algorithm SHA256

# macOS
shasum -a 256 export.dmp

Matching hashes confirm the file is intact.

Method 3: Validate with impdp (Requires Oracle)

With an Oracle environment, use impdp's SQLFILE parameter for a quick check:

impdp user/pass DIRECTORY=dump_dir DUMPFILE=export.dmp SQLFILE=verify.sql

If SQL output generates successfully, the file is readable. Error messages provide clues about corruption location.

Method 4: Quick Check with strings

strings export.dmp | head -20

EXP format files should show EXPORT:V near the beginning. No output may indicate an invalid file format.

File Transfer Best Practices

Item	Recommendation
FTP	Always use binary mode
Checksums	Compare SHA-256 before and after transfer
Compression	Compress with GZIP/ZIP before transfer
Splitting	Transfer as a single file when possible
Storage	Verify disk space at destination before transfer

Summary

The easiest way to check .dmp file integrity is to open it in OraDB DUMP Viewer. If the file parses correctly and you can preview table data, it's fine. For transfers, always use binary mode and compare checksums.

→ Get your free license