Wednesday, May 16, 2018

EBS -- Upgrading EBS 12.1.3 to 12.2 -- the general steps

In this blog post, I want to give you a list which includes the general steps that can be included in the project plan of an EBS 12.1.3 to 12.2 upgrade project.

By taking the following phases and the related steps into account, you may calculate your effort and do your project plan accordingly.

I wanted to use EBS 12.1.3 as the source version because it is a very common version in EBS customer environments. While giving the steps, I also wanted to highlight the teams responsible for completing those steps. (apps DBA team, Functional team, core business users etc..).

Of course, some of these steps like the "upgrade database step" is optional .( if your db release is up-to-date enough.)

Phase 1      
  • Upgrade the database on the existing EBS 12.1: apps DBA team      
  • Execute a functional test: EBS functional team
Phase 2      
  • Install all application pre-upgrade patches: apps DBA team      
  • Verify the instance: EBS functional team
Phase 3      
  • Execute all functional pre-upgrade tasks including customizations: functional team      
  • Perform a full system backup: System and apps DBA team   
 Phase 4      
  • Apply localization and 12.2 pre-upgrade patches: apps DBA team      
  • Upgrade to 12.2.0: apps DBA team      
  • Enable online patching: apps DBA team      
  • Apply tech stack patches: apps DBA team      
  • Upgrade to 12.2.6/12.2.7: apps DBA team      
  • Perform all post-upgrade tasks: apps DBA and functional teams      
  • Application function test cases: core business users       

4 comments :

  1. Hi Erman,
    Do you have an approx time table for the detailed steps of this upgrade process?

    ReplyDelete
  2. Is there a methodolgy to minimize the downtime of this upgrade process

    ReplyDelete
  3. can i Upgrading EBS 12.1.3 to 12.2 without closing balance what risk if i do this behavior can you help me plz

    ReplyDelete
  4. Hi,
    I am upgrading our EBS 12.1.3 with RAC 12c 2-node DB to EBS 12.2.9....as per the upgrade guide ..in the rapid install...Database Node Configuration screen....Database SID is Important: The database name specified in this field is used to determine the database SID. The database SID may vary depending on your environment.

    In an environment that does not use Oracle RAC, the database SID is the same as the database name.

    In an Oracle RAC environment, the instance number is appended to the database name to form the database SID for each Oracle RAC node.......

    What do you suggest to upgrade with RAC 2 nodes or just use one node for the upgrade without specifying the rac nodes....scan host ..scan port

    ReplyDelete

If you will ask a question, please don't comment here..

For your questions, please create an issue into my forum.

Forum Link: http://ermanarslan.blogspot.com.tr/p/forum.html

Register and create an issue in the related category.
I will support you from there.