September 3rd, 2012, 08:41 AM
Importing from a .dmp file - incompatible versionnumber
import from dump (.dmp) file. I'm running Oracle database 11g Enterprise edition release 220.127.116.11.0.
the import statement I'm using is
and the error I'm getting is "incompatible versionnumber 3.1 in the dumpfile mydmpfile.dmp"
impdp system/password@orcl full=Y DIRECTORY=data_pump_dir dumpfile=mydmpfile.dmp logfile=min.log
The dump file was exported using oracle 18.104.22.168.0.
I tried to download/unzip the client version of instantclient 22.214.171.124 and add it to the PATH variable in windows and then re-run the script, but it didn't work.
Anyone have a suggestion on how I should go from here to import this dump file without reinstalling the whole database?
Thanks in advance!
September 3rd, 2012, 03:08 PM
Was the correct value used on the version parameter on the export?
And is the correct value being used on the version parameter on the import?
September 4th, 2012, 02:40 AM
Thanks for the quick reply. There was no version parameters used on the export.
I tried adding a "version=126.96.36.199.0" (I also tried with version=LATEST) on the end of the impdp statement, however I still get the same error.
Any other ideas?
September 4th, 2012, 09:57 AM
Data Pump Import cannot read dump file sets created by a database release that is newer than the current database release, unless those dump file sets were created with the VERSION parameter set to the release of the target database. Therefore, the best way to perform a downgrade is to perform your Data Pump export with the VERSION parameter set to the release of the target database.
So the VERSION parameter should be used used in EXPORT.
And if you wan to use it in import then,
This parameter can be used to load a target system whose Oracle database is at an earlier compatibility release than that of the source system.
So if you want to down grade use the parameter in EXPORT.