This content has been marked as final. Show 3 replies
I never prefer to use imp/exp for EBS system. Its very hard to check all objects are valid or find to define which object missing.
I suggest follow Note 881505.1 and make directly upgrade instead of export-import
You could lay down 11gR2 ORACLE_HOME on the target node and create a clean 11g database then use export/import to move the database from 10g to 11g using (Export/import notes on Applications 11i Database 11g [ID 557738.1]). This way you do not have to export/import the 10g database then upgrade it to 11g.
Thanks for the reply . I saw in the following export/import parameter file ($AU_TOP/patch/115/import/auexpdp.dat ) that the sys and system schema's are also imported into the new db.
Is this not a probleme? Because I am importing into a 11g db from 10g. Will the "old" sys/system objects that is brought over not create problems for my 11g db?
I have done a network import like I described above (excluding sys en system, and afterwards recreated all the missing objects) but the EBS work flow is not working 100%
So I think if I include sys and system this will also work, but what about the 10g sys objects in my 11g db? Is there not a better way to recreate all these objects?
Phillip du Plooy