This content has been marked as final. Show 6 replies
Yes there is...
while using expdp you have to mention the VERSION clause i.e. VERSION=<your full import database server version>
then you can easily import that dump into the lower version.
however, i can't access the enviroments now.
so i can't use expdp while specifying the version parameter.
If you can access only the import database server then also you can do that using basic EXP and IMP command.1 person found this helpful
I hope the two database servers are connected using network.
Then you can use the EXP command from the import database server, and doing so the dump file will be R1 compatible and then you can easily import that using IMP command.
Try to :1 person found this helpful
First check what is output at target database by :
show parameter compatible;
expdp ... version=<above output>
In this case your dump file will have only database objects and attributes that are compatible with the specified release will be exported. Since you are not using transportable option, so platform don't matters.
You are getting error because you have exported all/some objects which are compatible in 11.2 but when you are going to import them into 11.1 then oracle is saying ORA-39142. So, just try to use version=<target database's compatible parameter value> and you done.
Is this related to your other thread - Re: Does Oracle sample schemas HR/OE overwrite APPS' alike schemas? ?1 person found this helpful
If so, as noted in the other thread, you cannot export/import individual EBS schemas between two different EBS instances.
If this is a separate issue, you will need to perform the expdp with the VERSION parameter - AFAIK, there is no workaround.
Exactly the same issue.
probably this won't make the EBS env all right, but i learned something.