This content has been marked as final. Show 6 replies
This sounds more like a corrupt dump file. or something similar. Are you changing versions from the export database to the import database? If you are importing on the same database, have you tried using network import to see if that works?
Please post the true versions of the databases. LIke 220.127.116.11, not 11gr2.
Both source and target are - 18.104.22.168.1202.
Please note that
1. I am using WINSCP to copy the dump file to a WINDOWS box and then transferring the dump to target.
2. I am getting the same error when I am trying to import the dump to a windows installation.
You need to tell winscp do to the transfer as 'binary' - it's likely doing it as ascii and corrupting the file.
Much thanks for your reply. Yes, I tried with binary option also. No luck yet.
There is a bug with a certain version of winscp that correupts the file ( i know because we hit it ) - have you got the very latest version of winscp?
Much thanks for your replies.
Would like to add just a simple line that if I do the import on the same server (source and destination is same box), the impdp works just fine.
I would update after changing the version of WINSCP.