Question :Yes, this should be sufficient -- Using Oracle EBS with a Split Configuration Database Tier on 11gR2 [ID 946413.1], "(Option D) Migrate database on other platforms to IBM Linux on System z, Linux x86-64, Solaris x86-64, HP Itanium, or Windows x64".
- Using the above note and export/import path, can we achieve all 3 database tasks in one go?
1. Windows to Linux migration for database
2. 32-bit to 64-bit migration (by installing 64 bit version on linux)
3. Exporting database from 32-bit Windows on 188.8.131.52 and Importing it to 64-bit Linux on 184.108.40.206.
This confirms moving from Windows (32-bit) to Linux (64-bit) using export / import. Just a quick question on database version before I close this thread.There should not be any issues if you meet all the requirements and follow the steps in the export/import doc.
- Do you see any issue with import to 220.127.116.11 database from export dump based on 18.104.22.168?
For database preparation, I see some different O/S patches when we install 22.214.171.124 compared to 126.96.36.199. We plan toYes.
- prepare source database as per the export/import note. (MOS 557738.1)
- install 188.8.131.52 database as per Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0) [ID 881505.1] instead of following 184.108.40.206 Interoperability Notes (ie. Note:1367654.1).
- Import the database to the new target RDBMS_HOME (220.127.116.11)
Should that be fine?
Do you think if RMAN convert database is an option for EBS database migration instead of export import? Just curious to know if this method is better and if it saves any time with 11gR2 version of database migration.I believe RMAN is not supported to migrate Oracle EBS database and you will have to use export/import instead.
Thanks and sorry to re-open this thread.You're welcome and please do not be sorry!