1 Reply Latest reply on Oct 4, 2016 3:33 AM by Narsi M-Oracle

    ADOP Prepare Failed R12.2.5 Upgrade

    Ramaraju

      Hi,

      We are upgrading EBS 11i to R12.2.5, after applying Online Patching enablement patch 13543062:R12.AD.C using adpatch, we are running prepare phase but it is failing with following error. Please help on this issue.

       

      Creating the new APPL_TOP Context file from :

        /oracle_homes/finupgr12/fs1/EBSapps/comn/clone/context/apps/adxmlctx.tmp

       

      Exception in thread "main" java.lang.NoSuchMethodError: oracle.apps.ad.clone.util.CloneUtil.fileEditionTypeReplacement(Loracle/apps/ad/context/AppsContext;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;

        at oracle.apps.ad.context.CloneContext.replaceRunBaseWithPatchBase(CloneContext.java:5409)

        at oracle.apps.ad.context.CloneContext.restoreDataInCloneContext(CloneContext.java:5301)

        at oracle.apps.ad.context.CloneContext.dependencyUpdate(CloneContext.java:5163)

        at oracle.apps.ad.context.CloneContext.doClone(CloneContext.java:884)

        at oracle.apps.ad.clone.FSCloneApplyAppsTier.cloneRunContext(FSCloneApplyAppsTier.java:700)

        at oracle.apps.ad.clone.FSCloneApplyAppsTier.doCloneContext(FSCloneApplyAppsTier.java:292)

        at oracle.apps.ad.clone.FSCloneApplyAppsTier.<init>(FSCloneApplyAppsTier.java:187)

        at oracle.apps.ad.clone.FSCloneApplyAppsTier.main(FSCloneApplyAppsTier.java:1003)

       

       

      Enabling EBS_LOGON trigger

       

       

      ERROR while running FSCloneApply...

      Mon Oct  3 08:56:26 2016

      *******FATAL ERROR*******

      PROGRAM : (/oracle_homes/finupgr12/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl)

      TIME    : Mon Oct  3 08:56:26 2016

      FUNCTION: main::checkCloneContext [ Level 1 ]

      ERRORMSG: Cloning of context file FAILED. Cannot proceed further. Check log file for details.

       

       

                    [ERROR]     Error occurred while executing <perl /oracle_homes/finupgr12/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/oracle_homes/finupgr12/fs1/inst/apps/FINUPG_finupgapp64/appl/admin/FINUPG_finupgapp64.xml -patchcontextfile=/oracle_homes/finupgr12/fs2/inst/apps/FINUPG_finupgapp64/appl/admin/FINUPG_finupgapp64.xml -promptmsg=hide -console=off -mode=create -sessionid=6 -timestamp=20161003_085145 -outdir=/oracle_homes/finupgr12/fs_ne/EBSapps/log/adop/6/prepare_20161003_085145/FINUPG_finupgapp64>

                    [ERROR]     Error occurred while CLONE PATCH FS with RUN FS using command: <perl /oracle_homes/finupgr12/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/oracle_homes/finupgr12/fs1/inst/apps/FINUPG_finupgapp64/appl/admin/FINUPG_finupgapp64.xml -patchcontextfile=/oracle_homes/finupgr12/fs2/inst/apps/FINUPG_finupgapp64/appl/admin/FINUPG_finupgapp64.xml -promptmsg=hide -console=off -mode=create -sessionid=6 -timestamp=20161003_085145 -outdir=/oracle_homes/finupgr12/fs_ne/EBSapps/log/adop/6/prepare_20161003_085145/FINUPG_finupgapp64>.

                    [STATEMENT] fs_clone phase completed with errors/warnings. Please check logfiles

                    [ERROR]     Error while runPendingClone sub-routine is called

                    [STATEMENT] [START 2016/10/03 08:56:29] Check and Stop Patch Admin Server

                      [STATEMENT] There is a pending clone session for /oracle_homes/finupgr12/fs2.

                      [STATEMENT] Skipping Check and Stop Patch Admin Server Step.

                    [STATEMENT] [END   2016/10/03 08:56:32] Check and Stop Patch Admin Server

                    [STATEMENT] Prepare phase completed with errors/warnings. Please check logfiles

                    [STATEMENT] PREPARE Phase END TIME: 03-10-2016 08:56:36

                    [STATEMENT] [START 2016/10/03 08:56:37] Unlocking sessions table

                    [STATEMENT] [END   2016/10/03 08:56:38] Unlocking sessions table

                    [STATEMENT] Log file: /oracle_homes/finupgr12/fs_ne/EBSapps/log/adop/6/adop_20161003_085145.log

      adop exiting with status = 1 (Fail)

       

      We found the following error in 'adConfigChanges.log' file. Please check it and update the SR.

      Executing command :

      /oracle_homes/finupgr12/fs1/EBSapps/comn/util/jdk32/jre/bin/java -classpath /oracle_homes/finupgr12/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/oracle_homes/finupgr12/fs1/EBSapps/comn/java/classes -mx256m oracle.apps.ad.tools.configuration.ConfigChangeDetector -detectConfigChanges -contextfile /oracle_homes/finupgr12/fs1/inst/apps/FINUPG_finupgapp64/appl/admin/FINUPG_finupgapp64.xml -backupdir /oracle_homes/finupgr12/fs1/inst/apps/FINUPG_finupgapp64/appl/admin/cutover -nodename finupgapp64 -log /oracle_homes/finupgr12/fs_ne/EBSapps/log/adop/7/prepare_20161003_102039/FINUPG_finupgapp64/adConfigChanges.log -promptmsg hide 

       

       

      Validated the passed arguments for the option -detectConfigChanges

       

        /oracle_homes/finupgr12/fs1/inst/apps/FINUPG_finupgapp64/appl/admin/cutover directory not found, so configuration changes cannot be detected.

      The directory may have been deleted intentionally or accidentally. Or, if this is the first adop cycle, the directory will only be created after cutover.

       

      Without this directory, the configuration changes will be propagated to the patch file system forcefully.

       

      Program exiting with status 2

       

      $ adop -status

       

       

      Enter the APPS username: apps

      Enter the APPS password:

       

       

       

       

      Current Patching Session ID: 7

       

       

      Node Name Node Type Phase    Status    Started   Finished  Elapsed

      --------------- --------------- ----------- --------------- ------------------------------ ------------------------------ ------------

      finupgapp64 master PREPARE     FAILED    03-OCT-16 10:21:20 -04:00   03-OCT-16 10:25:16 -04:00  0:03:56

        APPLY    NOT STARTED

        CUTOVER     NOT STARTED

        CLEANUP     NOT STARTED

       

      File System Synchronization Used in this Patching Cycle: None

       

      For more information, see the full ADOP Status Report.

      Generating full ADOP Status Report at location: /oracle_homes/finupgr12/fs_ne/EBSapps/log/status_20161003_104523/adzdshowstatus.out

      Please wait...

      Done...!

       

      adop exiting with status = 0 (Success)

       

      $ adopscanlog -latest=yes

      -bash: adopscanlog: command not found

       

      Thanks,

      Ramaraju