If your source server was on Linux, you could just use Rapid Clone to change the instance name and server names on the new server after you copy the files over per the 12.2 cloning note:
Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)
Please check the below notes to migrate ebs to exadata
Migrating an Oracle E-Business Suite Database to Oracle Exadata Database Machine (Doc ID 1133355.1)
Database Patches Required by Oracle EBusiness Suite on Exadata Database Machines (Doc ID 1392527.1)
Oracle E-Business Suite on Exadata Resources (Doc ID 1512711.1)
You can do the following -
1Q: As we are migrating the EBS application, do we have to clone the application on the new server by just coping the EBSapps directory(10.1.2,appl,comn) ? OR
we have to copy the complete run edition file system(EBSapps,FMW_Home,inst) and build the new XML files.
- You need to clone the instance on target server.
- Run adcfgclone apps_tier on target server by giving new server name.
- inst and FMW_HOME you don't need to copy, it will create while running adcfglcone.
Thanks for all your replies appreciate.
But the oracle document for the application migration (section 2: Migration Tasks) says the different steps, so I was little confusing.
Application Tier Platform Migration with Oracle E-Business Suite Release 12.2 (Doc ID 2048954.1)
Will follow the cloning method (Doc ID 1383621.1) to do the migration as it is comfortable.
Yes, that is for
- The application tier services should not be started up on the Target System until all the steps for platform migration have been completed.
In your case application platform is same if I am not wrong.
Let us know if you have any questions.
Yes in my case application platform is same Oracle PCA and we are migrating to new servers. The database platform is different it is from VMWare to Exadata on Linux.
Will follow the Cloning document for doing the application migration.