2 Replies Latest reply on Nov 6, 2015 11:05 AM by Bashar.

    Migration of EBS Application Tier (12.1.3) during production code freeze

    2801509

      In most cases, it is preferential to migrate the application tier during a production outage to minimize risk and limit the impact of change.

       

      I'm thinking of taking a copy of the application tier during production code freeze, but before the production downtime begins. What are the drawbacks and risks associated with this approach?

      Is there a preferred way of migrating to another platform, that allows me to eliminate some of the migration tasks from the production outage window?

       

      Our current approach is a database migration (small version upgrade via datapump export and import - 11.1.0.7 to 11.2.0.4), followed by an apps tier migration. All while the production application services are down to prevent user interaction.

       

      What is the risk of running pre-clone scripts on the source environment during a prior weekend, and using a copy of that source for my migrated environment? Assume that there will be no patches, code migrations, or other such changes to the production environment during the period after the apps tier backup is taken. The following weekend, we would migrate the database and then bring up the already copied application tier after running the post-copy rapid clone steps.

       

      Your comments are much appreciated.

       

      Joe

        • 1. Re: Migration of EBS Application Tier (12.1.3) during production code freeze
          Jignesh Makwana

          Hi Joa,

           

          Our current approach is a database migration (small version upgrade via datapump export and import - 11.1.0.7 to 11.2.0.4), followed by an apps tier migration. All while the production application services are down to prevent user interaction.

           

          Are you doing the platform migration of EBS DB / Application? if not then you don't need to do export / import and it will save your time.

           

          What is the risk of running pre-clone scripts on the source environment during a prior weekend

           

          There is no risk in running pre-clone on source instance; it's safe and you can run online.

           

           

          The following weekend, we would migrate the database and then bring up the already copied application tier after running the post-copy rapid clone steps.

          This should be ok if you are not applying any patches after application copy.

           

          Regards,

          Jignesh

          • 2. Re: Migration of EBS Application Tier (12.1.3) during production code freeze
            Bashar.

            Hi,

             

            To add to what has been said already, you might only need to copy the concurrent log and output files generated after you copied the application tier.

            It depends on your policy for how long to retain the files.

             

            Regards,

            Bashar