3 Replies Latest reply on May 18, 2016 2:49 AM by Beauty_and_dBest

    How to find or identify error in adop

    Beauty_and_dBest

      Hi ALL,

       

      EBS R12.2.4

      OL6

      11gR2

       

       

      I run adop phase=prepare   but I got error,

      I check the logs but I do not know which one is causing the error. and there are lots of errors listed

      Is there a tip or guidelines on how to find the real error?

      ==================

       

      [appprod@app ~]$  adopscanlog -latest=yes

      \

      Scanning /home/appprod/PROD/fs_ne/EBSapps/log/adop/7/ directory ...

      /home/appprod/PROD/fs_ne/EBSapps/log/adop/7/adop_20160517_133118.log:

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

      Lines #(158-162):

                    [EVENT]     Calling: /home/appprod/PROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl

                    [STATEMENT] Output directory: /home/appprod/PROD/fs_ne/EBSapps/log/adop/7/prepare_20160517_133118/PROD_app

                    [UNEXPECTED]Error occurred while executing "perl /home/appprod/PROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/home/appprod/PROD/fs1/inst/apps/PROD_app/appl/admin/PROD_app.xml -patchcontextfile=/home/appprod/PROD/fs2/inst/apps/PROD_app/appl/admin/PROD_app.xml -promptmsg=hide -console=off -mode=migrate -sessionid=7 -timestamp=20160517_133118 -outdir=/home/appprod/PROD/fs_ne/EBSapps/log/adop/7/prepare_20160517_133118/PROD_app"

                    [UNEXPECTED]Error occurred while CONFIG_CLONE Patch File System from Run File System using command: "perl /home/appprod/PROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/home/appprod/PROD/fs1/inst/apps/PROD_app/appl/admin/PROD_app.xml -patchcontextfile=/home/appprod/PROD/fs2/inst/apps/PROD_app/appl/admin/PROD_app.xml -promptmsg=hide -console=off -mode=migrate -sessionid=7 -timestamp=20160517_133118 -outdir=/home/appprod/PROD/fs_ne/EBSapps/log/adop/7/prepare_20160517_133118/PROD_app".

                    [STATEMENT] SQL statement : "  update ad_adop_session_patches

       

      Lines #(159-163):

                    [STATEMENT] Output directory: /home/appprod/PROD/fs_ne/EBSapps/log/adop/7/prepare_20160517_133118/PROD_app

                    [UNEXPECTED]Error occurred while executing "perl /home/appprod/PROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/home/appprod/PROD/fs1/inst/apps/PROD_app/appl/admin/PROD_app.xml -patchcontextfile=/home/appprod/PROD/fs2/inst/apps/PROD_app/appl/admin/PROD_app.xml -promptmsg=hide -console=off -mode=migrate -sessionid=7 -timestamp=20160517_133118 -outdir=/home/appprod/PROD/fs_ne/EBSapps/log/adop/7/prepare_20160517_133118/PROD_app"

                    [UNEXPECTED]Error occurred while CONFIG_CLONE Patch File System from Run File System using command: "perl /home/appprod/PROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/home/appprod/PROD/fs1/inst/apps/PROD_app/appl/admin/PROD_app.xml -patchcontextfile=/home/appprod/PROD/fs2/inst/apps/PROD_app/appl/admin/PROD_app.xml -promptmsg=hide -console=off -mode=migrate -sessionid=7 -timestamp=20160517_133118 -outdir=/home/appprod/PROD/fs_ne/EBSapps/log/adop/7/prepare_20160517_133118/PROD_app".

                    [STATEMENT] SQL statement : "  update ad_adop_session_patches set status='F'

       

      Lines #(165-169):

        patch_file_system_base = '/home/appprod/PROD/fs2' and bug_number='CONFIG_CLONE' and status <> 'C'

        and appltop_id=196 and node_name='app'"

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

                    [UNEXPECTED]Error while runPendingConfigClone sub-routine is called

                    [PROCEDURE] [START 2016/05/17 15:36:28] Check and Stop Patch Admin Server

       

      Lines #(166-170):

        and appltop_id=196 and node_name='app'"

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

                    [UNEXPECTED]Error while runPendingConfigClone sub-routine is called

                    [PROCEDURE] [START 2016/05/17 15:36:28] Check and Stop Patch Admin Server

                      [EVENT]     [START 2016/05/17 15:36:29] Check and Stop Patch FS Admin Server

       

      Lines #(176-180):

                      [STATEMENT] Skipping Check and Stop Patch Node Manager Step.

                    [PROCEDURE] [END   2016/05/17 15:36:33] Check and Stop Patch Node Manager

                    [ERROR]     Prepare phase completed with errors or warnings. Please check logfiles.

                    [STATEMENT] SQL statement : "  update ad_adop_sessions

        set status='F'

       

      /home/appprod/PROD/fs_ne/EBSapps/log/adop/7/prepare_20160517_133118/PROD_app/TXK_SYNC_migrate_Tue_May_17_13_34_56_2016/txkADOPPreparePhaseSynchronize_Tue_May_17_13_34_56_2016.log:

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

      Lines #(376-378):

      TIME    : Tue May 17 15:36:28 2016

      FUNCTION: main::migrateCloneComponentApply [ Level 1 ]

      ERRORMSG: /home/appprod/PROD/fs1/EBSapps/comn/adopclone_app/bin/adclone.pl did not go through successfully.

       

      /home/appprod/PROD/fs_ne/EBSapps/log/adop/7/prepare_20160517_133118/PROD_app/TXK_SYNC_migrate_Tue_May_17_13_34_56_2016/wlsConfig_apply/FSCloneApplyAppsTier_05171336.log:

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

      Lines #(181-183):

      Running /home/appprod/PROD/fs2/FMW_Home/oracle_common/bin/pasteConfig.sh -javaHome /home/appprod/PROD/fs2/EBSapps/comn/util/jdk64 -al /home/appprod/PROD/fs1/EBSapps/comn/adopclone_app/FMW/WLS/EBSdomain.jar -tdl /home/appprod/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain_PROD -tmw /home/appprod/PROD/fs2/FMW_Home -mpl /home/appprod/PROD/fs1/EBSapps/comn/adopclone_app/FMW/WLS/plan/moveplan.xml -ldl /home/appprod/PROD/fs1/inst/apps/PROD_app/admin/log/clone/wlsT2PApply -silent true -debug true -domainAdminPassword /home/appprod/PROD/fs1/EBSapps/comn/adopclone_app/FMW/tempinfo.txt

      Script Executed in 7200097 milliseconds, returning status -1

      ERROR: Script timed out.

      =================

       

       

      Current Patching Session ID: 7

       

      Node Name       Node Type       Phase           Status          Started                        Finished                       Elapsed

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

      app             master          PREPARE         FAILED          17-MAY-16 01:32:48 +08:00      17-MAY-16 03:36:33 +08:00      2:03:45

                                      APPLY           NOT STARTED

                                      FINALIZE        NOT STARTED

                                      CUTOVER         NOT STARTED

                                      CLEANUP         NOT STARTED

       

      File System Synchronization Used in this Patching Cycle: Full

       

      File System Information:

      ========================

      File System: SINGLE NODE INSTANCE

       

      Node Name   Node Type   Current Base               Other Base              Non Editioned Base        Inst Top

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

      app         master      /home/appprod/PROD/fs1    /home/appprod/PROD/fs2   /home/appprod/PROD/fs_ne  /home/appprod/PROD/fs1/inst/apps/PROD_app


      Custom File System Synchronization script: /home/appprod/PROD/fs_ne/EBSapps/appl/ad/custom/adop_sync.drv

       

      Patch Stage Top: /home/appprod/PROD/fs_ne/EBSapps/patch

       

      Online Patching Log base: /home/appprod/PROD/fs_ne/EBSapps/log/adop/7

      =========================================================================

      =             Patches Applied in the Current Patching Cycle

      =========================================================================

      =========================================================================

      =             ADADMIN actions in the Current Patching Cycle

      =========================================================================

      =========================================================================

      =                 Summary of the Last 10 ADOP Cycles

      =========================================================================

      Session

      ID      Node Name  Node Type Started   (Prepare) (Cutover) (Cleanup) (Apply)  Status Patches Applied  Session Type

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

            7 app        master    17-MAY-16 2:03:45   0:00:00   0:00:00    0:00:00 FAILED CONFIG_CLONE     CONFIG_CLONE

                         master              0:00:00   0:00:00   0:00:00    0:00:00 FAILED CONFIG_CLONE     CONFIG_CLONE

            6 app        master    17-MAY-16  0:00:00  0:00:00   0:00:00    0:00:00 COMPLETE      CLONE            CLONE

            5 appp       master    17-DEC-15  0:00:00  0:00:00   0:00:46    0:00:58 COMPLETE   18481499         HOTPATCH

            4 appscrp    master    07-JAN-15  0:00:00  0:00:00   0:00:46    0:26:26 COMPLETE   18237014         HOTPATCH

                         master                                             0:00:36 COMPLETE     18955265       HOTPATCH

            2 crp2       master    05-NOV-14  0:00:00  0:00:00   0:00:59    0:13:19 COMPLETE     17204589             --

                         master                                             0:23:18 COMPLETE     18283295        ADPATCH

                         master                                             0:23:18 COMPLETE     19581770        ADPATCH

                         master                                             0:11:28 COMPLETE     18288881       HOTPATCH

                         master                                             0:11:28 COMPLETE     19445058       HOTPATCH

                         master                                            10:42:11 COMPLETE     17919161       DOWNTIME

       

       

       

      Kind regards,

        • 1. Re: How to find or identify error in adop
          Poorvika

          Hello,

           

          The below error stack is the main issue. Concentrate on this part

           

          Running /home/appprod/PROD/fs2/FMW_Home/oracle_common/bin/pasteConfig.sh -javaHome /home/appprod/PROD/fs2/EBSapps/comn/util/jdk64 -al /home/appprod/PROD/fs1/EBSapps/comn/adopclone_app/FMW/WLS/EBSdomain.jar -tdl /home/appprod/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain_PROD -tmw /home/appprod/PROD/fs2/FMW_Home -mpl /home/appprod/PROD/fs1/EBSapps/comn/adopclone_app/FMW/WLS/plan/moveplan.xml -ldl /home/appprod/PROD/fs1/inst/apps/PROD_app/admin/log/clone/wlsT2PApply -silent true -debug true -domainAdminPassword /home/appprod/PROD/fs1/EBSapps/comn/adopclone_app/FMW/tempinfo.txt



          Check the latest log file under INST_TOP/admin/log/clone. This will give you where the phase has struck

          If there are any huge files under $EBS_DOMAIN_HOME. try deleting them and then do


          1) run adpreclone on FMW_HOME using below command

          perl adpreclone.pl FMW_HOME


          2) Rerun the failed prepare phase


          Let us know if this works


          Thanks


          1 person found this helpful
          • 2. Re: How to find or identify error in adop
            Poorvika

            Are there any errors in the latest log file under $INST_TOP/admin/log/clone

            1 person found this helpful
            • 3. Re: How to find or identify error in adop
              Beauty_and_dBest

              Thanks ALL,

               

              This adop thing has weird behavior. I just rerun again the adop=prepare and  it went okay now?

              Does this mean you have to run it twice?

               

              Although I tried to run this task, I do not know if they helped?

               

              # chmod -R 777 /tmp   /usr/tmp    /var/tmp

              su - applmgr

              $ export CONFIG_JVM_ARGS="-Xms1024m -Xmx2048m"