EBS 12.1.1 upgrade to EBS 12.2.6

[Raja]

Hi Erman

server a
 
I have ebs 12.1.1 and 11.2.0.1 running. Now i want to upgrade it to EBs 12.2.6

My approach

In server B

using active duplicate database feature, i will migrate the Db(11.2.0.1)from server A to new server B. In server B, i will upgrade the Database to 12.1.0.2. Then i will layout the EBS 12.2.0 file system and then upgrade

In this case, users will be able to use the existing EBS 12.1.1 and in parallel we can accomplish our upgrade


Is my approach correct?

[ErmanArslansOracleBlog]

in parallel?
what do you mean in parallel?

What about the transactions? Will you migrate them (load them) from your current instance to the upgraded one?

[Raja]

Hi Erman

Sorry for the confusion. When i say in parallel, i meant to say that once i create a database in destination server using active duplication(for development phase only), users will be accessing the existing EBS 12.1.1 env and DBAs will be doing the upgrade activity in the destination server. And in destination server, we will layout the EBS 12.2 file system using the existing database(created by active duplicate method) and proceed with rest of the steps.

basically we are doing a migrate and upgrade method for our first development phase. Is this feasible?

[Raja]

These are the high level steps i have sorted out so far

1. EBS 12.1.1 is running with DB 11.2.0.1. First i will migrate the database to the new server using expdp/active duplicate and then upgrade the database to 12.1.0.2

2. next, i will lay out the 12.2 file system using the existing ORACLE HOME.

3. And start the upgrade process.

Please let me know if this is the right approach or not.

I just wanted to minimize the downtime as much as possible.


Thanks

[ErmanArslansOracleBlog]

Migration is not related with the upgrade.
It is an optional thing, and an extra. But I think you want to a platform migration in the fist place.


However, what do you mean expdp active duplicate? expdp means datapump export. Duplicate is an rman term.
As long as you are aligned with the documents, it is okay, your approach is correct.

--The minimum downtime can be obtained using the dataguard switchover/failover.