Windows server 2008 to Oracle Linux 7 - EBS databases and application Migration

[karthikmca.bhc]

Hi Erman,

Your blog is very much useful to me to grow more on apps dba. Need you help. My client needs to migrate their production EBS system which is running currently on windows and that needs to be migrated to Oracle Linux 64bit platform. Please tell me which method i should follow for the below migration of theri EBS production to the Linux environment,

Please provide me oracle recommended roadmap/method to achieve below task.

Windows server to Oracle Linux EBS Migration:

Source:
-----------
Operating System : Windows server 2008 64-bit
Database Version : 11.2.0.2
Database Size : 700 GB
EBS Application version : 12.1.2
EBS Schemas : Standard+Custom

Target:
----------
Operating System : Oracle Linux 7.4 64-bit
Database Version : 12.1.0.2
EBS Application version : 12.2.5

Thanks
Karthik

[ErmanArslansOracleBlog]

Hi,

thanks for the feedback.

Basically, you will migrate your db using rman  (supposing all EBS requirements and RDBMS requirements are already met on your new Linux Server -- like rpms, like Database examples installation and etc..)

You will then migrate your apps tier except the techstack. -- You will install the techstack using the Linux techstack installer.

However, I see that you need an application upgrade + db upgrade during this migration.
These needs make the process highly complex.
EBS application upgrade is a big thing.
Db upgrade is also a big thing.
In addition, you have custom codes and you are migrating from Windows to Linux.

In this case, you better split this work in to phases.
First you migrate your db to linux.
Then upgrade your db
Then migrate your apps tier to linux (take care of the customizations in this phase, as well..)
And lastly upgrade your EBS (a big work)

If you need more questions, please ask them clearly. enumerate them and please be specific. (ask specific questions)

[karthikmca.bhc]

Hi Erman,

Thanks a lot for the information  you shared on my query.

Client said they need their production ebs application and database in the new linux os with ebs version 12.2.5 and database 12c(12.1.0.2) . Please clarify/confirm whether below task/method will work perfectly without any issues:

Testing phase:
----------------

Step 1:
Create clone of existing production which is running on Windows server 2008 in any of test Windows server2008

Step 2:
Build/freshly install one ebs 12.2.5 application with 12c database(12.1.0.2) on test Oracle linux 7.4 server

Step 3:
Login to windows clone instance and Using datapump method export all the standard, custom schemas and keep the dump file ready

Step 4:
Copy the dumpfiles from windows to test oracle linux and Login to 12.2.5 instance as db user(sys) and Using impdp utility import the dump files and make sure import of schemas are successful

Step 5:
Create one custom top in test 12.2.5 instance and copy all the custom rdf and fmb's from windows clone instance to newly installed 12.2.5 instance and perform all customization tasks

Step 6:
Fix the downtime and repeat all the above for production migration as well

Please tell me the above method is possible and will work perfectly without any issues? and where i will face the complexity if I go with above strategy?

Thanks
Karthik

[ErmanArslansOracleBlog]

No, this is not correct.
You can't just export data from an early release of EBS and import it to 12.2.5. ( you can't just exp-imp standard data from earlier release to new release)

If you want to export - import EBS database, then your source and target EBS instance should be in  the same level (for ex: 12.2 to 12.2 ) -- I m not talking about the db version here.

Now.. I need to understand your need.
There are 3 methods for using EBS 12.2.5.
 
1) Fresh EBS 12.2.5 installation (new install, empty in terms of data)
2) Fresh EBS 12.2.5 installation + load data from your early EBS to this new EBS suite. (this is called migration as well)
3)Upgrade your early relase EBS suite to EBS 12.2.5 (this is called upgrade, and it is done using EBS upgrade methodology)  

Which one you need?

[karthikmca.bhc]

Hi Erman

Thanks a lot for making me understand my queries. Now i understood that I can't just exp-imp standard data from earlier(12.1.x) release to new release(12.2.x).

My customer need is the below one:

2) Fresh EBS 12.2.5 installation + load data from your early EBS to this new EBS suite.

Can you please make me understand what is mean by standard data and standard shemas and modules that I needs to be considered and convey to my client that direct export import will not be possible when these standard things are involved on their existing 12.1.2 production ebs suite

What I should do if their above needs to be achieved?

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: "ErmanArslansOracleBlog [via Erman Arslan's Oracle Forum]" <[hidden email]>

Date: 9/8/17 11:59 AM (GMT+04:00)

To: "karthikmca.bhc" <[hidden email]>

Subject: Re: Windows server 2008 to Oracle Linux 7 - EBS databases and application  Migration

No, this is not correct.
You can't just export data from an early release of EBS and import it to 12.2.5. ( you can't just exp-imp standard data from earlier release to new release)

If you want to export - import EBS database, then your source and target EBS instance should be in  the same level (for ex: 12.2 to 12.2 ) -- I m not talking about the db version here.

Now.. I need to understand your need.
There are 3 methods for using EBS 12.2.5.
 
1) Fresh EBS 12.2.5 installation (new install, empty in terms of data)
2) Fresh EBS 12.2.5 installation + load data from your early EBS to this new EBS suite. (this is called migration as well)
3)Upgrade your early relase EBS suite to EBS 12.2.5 (this is called upgrade, and it is done using EBS upgrade methodology)  

Which one you need?

---

If you reply to this email, your message will be added to the discussion below:

http://erman-arslan-s-oracle-forum.2340467.n4.nabble.com/Windows-server-2008-to-Oracle-Linux-7-EBS-databases-and-application-Migration-tp3408p3427.html

To unsubscribe from Windows server 2008 to Oracle Linux 7 - EBS databases and application Migration, click here.
NAML

[ErmanArslansOracleBlog]

EBS standard schemas are the schemas that are deployed with the EBS installation.
These are EBS standard schemas that store the module's data. (such as AR, AP, PO etc..)
APPS schema is a specialized one.
Custom schemas, are the schemas that you create, later after the installation.. You use this schemas for putting your customizations. (db tier)
So, it is a long story really.

If you are interested, I recommend you get my book. We explained all of these in that book.

http://www.apress.com/br/book/9781484214237

In your case, you need to the following- >

Install EBS 12.2.0 on Linux
Upgrade it to EBS 12.2.6 (latest release currently) on Linux
Apply localization and NLS translation patches on Linux
Lastly, transfer your data + application tier customizations + db tier customizations from the earlier release of EBS to your new release (using DB editor programs, EBS specific tools  and APIs.. -- get the help of developer and functional team in this phase) -- from Windows to Linux..

[karthikmca.bhc]

Thanks for the valuable points. 

"In your case, you need to the following- >

Install EBS 12.2.0 on Linux
Upgrade it to EBS 12.2.6 (latest release currently) on Linux
Apply localization and NLS translation patches on Linux
Lastly, transfer your data + application tier customizations + db tier customizations from the earlier release of EBS to your new release (using DB editor programs, EBS specific tools  and APIs.. -- get the help of developer and functional team in this phase) -- from Windows to Linux.. "

As per  your above workaround I can EBS 12.2.0 and can upgrade it to 12.2.5 by 12.2.5RUP patch and will apply localization and NLS translation patches on Linux and then I'll start data migration.

here(data migration) is my question ,As you advised above, how I can transfer my data (standard + custom schemas of earlier ebs release(12.1.2) to my new 12.2.5 release. But your earlier response you advised me that transferring standard&custom schemas from old release(12.1.x) to new release (12.2.x) is not allowed and not possible. 

My client need two things to be completed at same migration time. Client need is to migrate their old ebs data which is running on Windows server to  linux server that runs new 12.2.5 ebs now. 

After freshly installing 12.2.5 ebs on linux, how it is possible to transfer old release data to this newly installed 12.2.5 release?

Please provide me a concrete solution for this requirement.

Thanks

Karthik 

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: "ErmanArslansOracleBlog [via Erman Arslan's Oracle Forum]" <[hidden email]>

Date: 9/9/17 12:04 PM (GMT+04:00)

To: "karthikmca.bhc" <[hidden email]>

Subject: Re: Windows server 2008 to Oracle Linux 7 - EBS databases and application  Migration

EBS standard schemas are the schemas that are deployed with the EBS installation.
These are EBS standard schemas that store the module's data. (such as AR, AP, PO etc..)
APPS schema is a specialized one.
Custom schemas, are the schemas that you create, later after the installation.. You use this schemas for putting your customizations. (db tier)
So, it is a long story really.

If you are interested, I recommend you get my book. We explained all of these in that book.

http://www.apress.com/br/book/9781484214237

In your case, you need to the following- >

Install EBS 12.2.0 on Linux
Upgrade it to EBS 12.2.6 (latest release currently) on Linux
Apply localization and NLS translation patches on Linux
Lastly, transfer your data + application tier customizations + db tier customizations from the earlier release of EBS to your new release (using DB editor programs, EBS specific tools  and APIs.. -- get the help of developer and functional team in this phase) -- from Windows to Linux..

---

If you reply to this email, your message will be added to the discussion below:

http://erman-arslan-s-oracle-forum.2340467.n4.nabble.com/Windows-server-2008-to-Oracle-Linux-7-EBS-databases-and-application-Migration-tp3408p3441.html

To unsubscribe from Windows server 2008 to Oracle Linux 7 - EBS databases and application Migration, click here.
NAML

[ErmanArslansOracleBlog]

Hi,

I said it is not allowed because you said that you are planning to transfer the data using export/import, which means - > exp/imp , expdp/imptp or datadupmp.

for custom schemas , it may work but for standard schemas, you need to transfer data using an APPS/EBS aware method..

Same for your customizations, you need to transfer your customizations (forms, reports,plsql, java etc) using a APPS/EBS aware way. You need to modify the customizations according to the EBS 12.2 's requirements and the changes in EBS 12.2.

As I said earlier, work with the developer and functional teams for this data migration. (for custom schemas, you can use exp/imp, but for standard data, you should not.)

[Karthik]

Hi Erman

Thanks a lot for your points. Now I understood and made me clear that datapump is only applicable for custom schemas migration and not for standard ebs schemas such as AP,AR,GL,OM etc..

Please can you make me understand on what is mean by APPS/EBS aware methods to migrate standard schemas from older release (12.1.2) to newer release (12.2.5) ?

EBS aware method you mean platform migration(migrate the existing ebs prod system from windows to linux as it is) and upgrading the older ebs release to newest releases (12.1.2-->12.2.0-->12.2.5) ?

[ErmanArslansOracleBlog]

No.
You said you are planning to install EBS 12.2, and transfer your data , which is residing in older version of EBS to this new EBS 12.2, right?
By this approach, you also do a platform migration, because you probably, get the data from the old version of EBS and you still start using the new version (EBS 12.2)

So you will do a fresh EBS 12.2 installation on Linux and then your functional teams do the EBS setups, your developers will transfer the customizations (modify them according to the new release) and then you will transfer the data from your old versioned EBS (running on windows) to this new EBS 12.2 ( running on Linux)
So, your infra will be new and you will load the data to this new infra/application (EBS 12.2 in this case)

The process of this data transfer is done using APPS/EBS aware methods. Your developers and functional guys should check the new release and get the data from the old version accordingly.
In one of the cases, we did it using db links and APIs. We get the data from the old release using a db link, we transformed in using plsql(when needed) and loaded it with EBS APIs.

So, there may be other way which can be implemented in other cases as well. This is not an Apps DBA work bytheway.