ADOP PHASE=PREPRE FAILED

Ramaraju

    Hi All,

    While running adop prepare phase geting following error.

    EBS Version: R12.2.4

    $ adopscanlog -latest=yes

    Scanning /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/14/ directory ...

    /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/14/adop_20180131_173134.log:

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

    Lines #(145-149):

                  [EVENT]     Calling: /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl

                  [STATEMENT] Output directory: /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/14/prepare_20180131_173134/VISMA_hydaswini

                  [UNEXPECTED]Error occurred while executing "perl /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -patchcontextfile=/u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -promptmsg=hide -console=off -mode=migrate -sessionid=14 -timestamp=20180131_173134 -outdir=/u02/oracle/VISMA/fs_ne/EBSapps/log/adop/14/prepare_20180131_173134/VISMA_hydaswini"

                  [UNEXPECTED]Error occurred while CONFIG_CLONE Patch File System from Run File System using command: "perl /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -patchcontextfile=/u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -promptmsg=hide -console=off -mode=migrate -sessionid=14 -timestamp=20180131_173134 -outdir=/u02/oracle/VISMA/fs_ne/EBSapps/log/adop/14/prepare_20180131_173134/VISMA_hydaswini".

                  [STATEMENT] SQL statement : "  update ad_adop_session_patches

    Lines #(146-150):

                  [STATEMENT] Output directory: /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/14/prepare_20180131_173134/VISMA_hydaswini

                  [UNEXPECTED]Error occurred while executing "perl /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -patchcontextfile=/u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -promptmsg=hide -console=off -mode=migrate -sessionid=14 -timestamp=20180131_173134 -outdir=/u02/oracle/VISMA/fs_ne/EBSapps/log/adop/14/prepare_20180131_173134/VISMA_hydaswini"

                  [UNEXPECTED]Error occurred while CONFIG_CLONE Patch File System from Run File System using command: "perl /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -patchcontextfile=/u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -promptmsg=hide -console=off -mode=migrate -sessionid=14 -timestamp=20180131_173134 -outdir=/u02/oracle/VISMA/fs_ne/EBSapps/log/adop/14/prepare_20180131_173134/VISMA_hydaswini".

                  [STATEMENT] SQL statement : "  update ad_adop_session_patches

      set status='F'

    Lines #(152-156):

      patch_file_system_base = '/u02/oracle/VISMA/fs1' and bug_number='CONFIG_CLONE' and status <> 'C'

      and appltop_id=1045 and node_name='hydaswini'"

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

                  [UNEXPECTED]Error while runPendingConfigClone sub-routine is called

                  [PROCEDURE] [START 2018/01/31 17:39:20] Check and Stop patch Admin Server

    Lines #(153-157):

      and appltop_id=1045 and node_name='hydaswini'"

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

                  [UNEXPECTED]Error while runPendingConfigClone sub-routine is called

                  [PROCEDURE] [START 2018/01/31 17:39:20] Check and Stop patch Admin Server

                    [EVENT]     [START 2018/01/31 17:39:21] Check and Stop patch FS Admin Server

    Lines #(162-166):

                    [EVENT]     [END   2018/01/31 17:39:44] Check and Stop patch Node Manager

                  [PROCEDURE] [END   2018/01/31 17:39:44] 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'

    /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/14/prepare_20180131_173134/VISMA_hydaswini/TXK_SYNC_migrate_Wed_Jan_31_17_37_03_2018/txkADOPPreparePhaseSynchronize_Wed_Jan_31_17_37_03_2018.log:

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

    Lines #(337-339):

    TIME    : Wed Jan 31 17:39:20 2018

    FUNCTION: main::validateCloneStage [ Level 1 ]

    ERRORMSG: Could not find the log file under /u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/admin/log/clone.

     

    Thanks,

    Ramaraju

      • 1. Re: ADOP PHASE=PREPRE FAILED
        mdtaylor

        Source the patch filesystem.

         

            Stop the Oracle Weblogic Server Admin Server on the patch file system.

         

            UNIX:

            $ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh stop

         

            Stop the Oracle WebLogic Server Node Manager service on the patch file system.

         

            UNIX:

            $ sh $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

         

        Retry the adop phase=prepare command.

         

        Also provide adop --status to ensure previous adop session has completed successfully.

        • 2. Re: ADOP PHASE=PREPRE FAILED
          Rafi (Oracle DBA)

          Hi,

           

          Did you tried aborting the adop session with adop options=abort and starting again the prepare phase?

           

           

          Thanks,

          • 3. Re: ADOP PHASE=PREPRE FAILED
            Magnanimous

            Hello Rama,

             

            Please do the steps provided by Taylor.

             

            Prashant

            • 4. Re: ADOP PHASE=PREPRE FAILED
              Ramaraju

              Hi Taylor,

               

              Thanks,

              Ramaraju

              • 5. Re: ADOP PHASE=PREPRE FAILED
                Ramaraju

                Yes,

                I have tried with abort phase also. But still facing same issue.

                 

                Thanks,

                Ramaraju

                • 6. Re: ADOP PHASE=PREPRE FAILED
                  Ramaraju

                    E-Business Suite Environment Information

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

                    RUN File System           : /u02/oracle/VISMA/fs2/EBSapps/appl

                    PATCH File System         : /u02/oracle/VISMA/fs1/EBSapps/appl

                    Non-Editioned File System : /u02/oracle/VISMA/fs_ne

                   

                   

                   

                   

                    DB Host: hydaswini.srisys.com  Service/SID: VISMA

                   

                   

                   

                   

                    Sourcing the PATCH File System ...

                   

                   

                  [oracle@hydaswini PATCH(fs1)-VISMA ~]$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh stop

                   

                   

                  You are running adadminsrvctl.sh version 120.10.12020000.9

                   

                   

                  Enter the WebLogic Admin password:

                  Enter the APPS Schema password:

                   

                   

                  The AdminServer is already shutdown

                   

                   

                  adadminsrvctl.sh: exiting with status 2

                   

                   

                  adadminsrvctl.sh: check the logfile /u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/logs/appl/admin/log/adadminsrvctl.txt for more information ...

                   

                   

                  [oracle@hydaswini PATCH(fs1)-VISMA ~]$ sh $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

                   

                   

                  You are running adnodemgrctl.sh version 120.11.12020000.11

                   

                   

                  Enter the WebLogic Admin password:

                   

                   

                  The Node Manager is already shutdown

                   

                   

                  adnodemgrctl.sh: exiting with status 2

                   

                   

                  adnodemgrctl.sh: check the logfile /u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/logs/appl/admin/log/adnodemgrctl.txt for more information ...

                   

                   

                  $ adop phase=prepare

                   

                   

                  Enter the APPS password:

                  Enter the SYSTEM password:

                  Enter the WLSADMIN password:

                   

                   

                  Please wait. Validating credentials...

                   

                   

                   

                   

                  RUN file system context file: /u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml

                   

                   

                  PATCH file system context file: /u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml

                  Execute SYSTEM command : df /u02/oracle/VISMA/fs1

                   

                   

                  Worker count determination...

                   

                   

                  Validation successful. All expected nodes are listed in ADOP_VALID_NODES table.

                  [EVENT]     [START 2018/02/06 07:15:26] Performing database sanity checks

                  [EVENT]     [END   2018/02/06 07:15:27] Finished performing database sanity checks

                    There is already a session which is incomplete. Details are:

                          Session Id            :   15

                          Prepare phase status  :   RUNNING

                          Apply phase status    :   NOT COMPLETED

                          Cutover  phase status :   NOT COMPLETED

                          Abort phase status    :   NOT COMPLETED

                          Session status        :   FAILED

                    Will continue with previous session

                    [START 2018/02/06 07:15:28] adzdoptl.pl run

                      ADOP Session ID: 15

                      Phase: prepare

                      Log file: /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/adop_20180206_071511.log

                      [EVENT]     [START 2018/02/06 07:15:29] Calling task: "Executing txkADOPValidation script on hydaswini"; script: "/u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl"; args: " -contextfile=/u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -patchctxfile=/u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -phase=prepare -logloc=/u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini -promptmsg=hide"

                        [EVENT]     [START 2018/02/06 07:15:29] Executing txkADOPValidation script on hydaswini

                          [EVENT]     Calling: /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl

                  Oracle E-Business Suite Online Patching

                  RUN edition environment variables have been set.

                   

                   

                  calling: /u02/oracle/VISMA/fs2/FMW_Home/webtier/perl/bin/perl /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkValidateSetup.pl -contextfile=/u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -patchctxfile=/u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -logloc=/u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini -phase=prepare -promptmsg=hide

                   

                   

                  Program : txkValidateSetup.pl started @ Tue Feb  6 07:15:32 2018

                   

                   

                  *** Log File = /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/ADOPValidations_Tue_Feb_6_07_15_32_2018.log

                   

                   

                  SETUP VALIDATION is in progress. This may take few minutes to complete.

                   

                   

                  Completed execution of all tests. There are warnings.

                   

                   

                  =========================== START OF VALIDATION REPORT ====================

                   

                   

                  Validation Results for Node: hydaswini

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

                  [WARNING]: There could be issues while validating the ports used for E-Business Suite instance against ports used in /etc/services. Refer the log file for more details.

                   

                   

                  There are warnings in tests, please check /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/ADOPValidations_Tue_Feb_6_07_15_32_2018.log

                   

                   

                  =========================== END OF VALIDATION REPORT ======================

                        [EVENT]     [END   2018/02/06 07:17:14] Executing txkADOPValidation script on hydaswini

                      [EVENT]     [END   2018/02/06 07:17:14] Executing txkADOPValidation script on hydaswini

                      [START 2018/02/06 07:17:19] prepare phase

                        [EVENT]     [START 2018/02/06 07:17:20] Validating Configuration

                          [EVENT]     Calling: /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSanityCheck.pl

                   

                   

                  Program :  started @ Tue Feb  6 07:17:21 2018

                   

                   

                  *** Log File = /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/TXK_SANITY_filesystemcheck_Tue_Feb_6_07_17_21_2018/txkADOPPreparePhaseSanityCheck_Tue_Feb_6_07_17_21_2018.log

                   

                   

                  LOG FILE     : /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/TXK_SANITY_filesystemcheck_Tue_Feb_6_07_17_21_2018/txkADOPPreparePhaseSanityCheck_Tue_Feb_6_07_17_21_2018.log

                   

                   

                   

                   

                  Program :  completed @ Tue Feb  6 07:17:22 2018

                   

                   

                        [EVENT]     [END   2018/02/06 07:17:22] Validating Configuration

                        [EVENT]     [START 2018/02/06 07:17:22] Detecting config changes in FS

                          [EVENT]     Calling task: "Executing adConfigChangeDetector on hydaswini"; script: "/u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/adConfigChangeDetector.pl"; args: " -detectConfigChanges contextfile=/u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml promptmsg=hide log=/u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/adConfigChanges.log hostname=hydaswini"

                          [EVENT]     [START 2018/02/06 07:17:22] Executing adConfigChangeDetector on hydaswini

                            [EVENT]     Calling: /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/adConfigChangeDetector.pl

                  The log file is /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/adConfigChanges.log

                  Configuration change detected.

                          [EVENT]     [END   2018/02/06 07:17:25] Executing adConfigChangeDetector on hydaswini

                        [EVENT]     [END   2018/02/06 07:17:25] Detecting config changes in FS

                        [EVENT]     [START 2018/02/06 07:17:25] Performing check to see if pending cleanup actions exist

                          [EVENT]     No pending cleanup actions, proceeding with other steps

                        [EVENT]     [END   2018/02/06 07:17:25] Performing check to see if pending cleanup actions exist

                        [EVENT]     [START 2018/02/06 07:17:25] Performing DB Sanity checks

                        [EVENT]     [END   2018/02/06 07:17:25] Performing DB Sanity checks

                        [START 2018/02/06 07:17:25] Generating Tablespace Report

                            [EVENT]     Report: /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/sql/ADZDSHOWTS.sql

                   

                   

                            [EVENT]     Output: /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/adzdshowts.out

                   

                   

                        [END   2018/02/06 07:17:27] Generating Tablespace Report

                          [EVENT]     [START 2018/02/06 07:17:27] Start Apps Listner

                   

                   

                  adalnctl.sh version 120.3.12020000.2

                   

                   

                  Checking for FNDFS executable.

                  Listener APPS_VISMA has already been started.

                   

                   

                  adalnctl.sh: exiting with status 2

                   

                   

                   

                   

                  adalnctl.sh: check the logfile /u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/logs/appl/admin/log/adalnctl.txt for more information ...

                   

                   

                          [EVENT]     [END   2018/02/06 07:17:27] Start Apps Listner

                        [EVENT]     [START 2018/02/06 07:17:27] Run the ADZDPATCH concurrent program

                        [EVENT]     [END   2018/02/06 07:17:28] Run the ADZDPATCH concurrent program

                        [EVENT]     [START 2018/02/06 07:17:28] Generating ad_zd_logs before truncating

                            [EVENT]     Report: /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/sql/ADZDSHOWLOG.sql

                   

                   

                            [EVENT]     Output: /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/adzdshowlog_cleanup.out

                   

                   

                        [EVENT]     [END   2018/02/06 07:17:30] Generating ad_zd_logs before truncating

                        [EVENT]     [START 2018/02/06 07:17:30] Check and create Patch Edition (if required)

                          [EVENT]     [START 2018/02/06 07:17:30] Checking if Patch Edition already exists

                          [EVENT]     [END   2018/02/06 07:17:30] Check and create Patch Edition (if required)

                          [EVENT]     [START 2018/02/06 07:17:30] Performing steps to synchronise the FS

                              [EVENT]     [START 2018/02/06 07:17:30] Sync FS of RUN and PATCH

                                [EVENT]     Calling: /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl

                   

                   

                  Program :  started @ Tue Feb  6 07:17:31 2018

                   

                   

                  *** Log File = /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/TXK_SYNC_update_Tue_Feb_6_07_17_31_2018/txkADOPPreparePhaseSynchronize_Tue_Feb_6_07_17_31_2018.log

                   

                   

                  Oracle E-Business Suite Online Patching

                  PATCH edition environment variables have been set.

                  Oracle E-Business Suite Online Patching

                  RUN edition environment variables have been set.

                  cmd = /u02/oracle/VISMA/fs2/EBSapps/comn/util/jdk32/jre/bin/java -classpath /u02/oracle/VISMA/fs2/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/u02/oracle/VISMA/fs2/EBSapps/comn/java/classes -mx256m  oracle.apps.ad.tools.configuration.ADOPCustomSyncUp -contextFile /u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -custSyncDrv /u02/oracle/VISMA/fs_ne/EBSapps/appl/ad/custom/adop_sync.drv -logFile /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/TXK_SYNC_update_Tue_Feb_6_07_17_31_2018/txkADOPCustomSyncUp.log -promptmsg 'hide'

                  Removing <MSC_TOP> PS artifacts from PATCH fs

                  Copying <MSC_TOP> PS artifacts from RUN to PATCH fs for exectier

                  Removing <MSC_TOP> SNO artifacts from PATCH fs

                  Copying <MSC_TOP> SNO artifacts from RUN to PATCH fs for exectier

                  ADOP Custom Synchorization successfully run

                  LOG FILE     : /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/TXK_SYNC_update_Tue_Feb_6_07_17_31_2018/txkADOPPreparePhaseSynchronize_Tue_Feb_6_07_17_31_2018.log

                   

                   

                   

                   

                  Program :  completed @ Tue Feb  6 07:17:44 2018

                   

                   

                              [EVENT]     [END   2018/02/06 07:17:44] Sync FS of RUN and PATCH

                              There is a pending CONFIG_CLONE session for /u02/oracle/VISMA/fs1 file system, invoking FS Clone.

                                [EVENT]     [START 2018/02/06 07:17:49] CONFIG_CLONE Patch File System from Run File System

                                  [EVENT]     Calling: /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl

                   

                   

                  Program :  started @ Tue Feb  6 07:17:50 2018

                   

                   

                  *** Log File = /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/TXK_SYNC_migrate_Tue_Feb_6_07_17_50_2018/txkADOPPreparePhaseSynchronize_Tue_Feb_6_07_17_50_2018.log

                   

                   

                  The log file is /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/TXK_SYNC_migrate_Tue_Feb_6_07_17_50_2018/getCtxFileStatus.log

                  The log file is /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini/TXK_SYNC_migrate_Tue_Feb_6_07_17_50_2018/getWLSStatus.log

                  Configuration change detected.

                   

                   

                   

                   

                   

                   

                  Beginning application tier FSCloneStage - wlsConfig Tue Feb  6 07:18:29 2018

                   

                   

                  /u02/oracle/VISMA/fs2/EBSapps/comn/util/jdk32/bin/java -Xmx600M -DCONTEXT_VALIDATED=false -Doracle.installer.oui_loc=/oui -classpath /u02/oracle/VISMA/fs2/FMW_Home/webtier/lib/xmlparserv2.jar:/u02/oracle/VISMA/fs2/FMW_Home/webtier/jdbc/lib/ojdbc6.jar:/u02/oracle/VISMA/fs2/EBSapps/comn/java/classes:/u02/oracle/VISMA/fs2/FMW_Home/webtier/oui/jlib/OraInstaller.jar:/u02/oracle/VISMA/fs2/FMW_Home/webtier/oui/jlib/ewt3.jar:/u02/oracle/VISMA/fs2/FMW_Home/webtier/oui/jlib/share.jar:/u02/oracle/VISMA/fs2/FMW_Home/webtier/../Oracle_EBS-app1/oui/jlib/srvm.jar:/u02/oracle/VISMA/fs2/FMW_Home/webtier/jlib/ojmisc.jar:/u02/oracle/VISMA/fs2/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/u02/oracle/VISMA/fs2/FMW_Home/oracle_common/jlib/obfuscatepassword.jar  oracle.apps.ad.clone.FSCloneStageAppsTier -e /u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -targ /u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -stage /u02/oracle/VISMA/fs2/EBSapps/comn/adopclone_hydaswini -tmp /tmp -component wlsConfig -nopromptmsg

                  Log file located at /u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/admin/log/clone/FSCloneStageAppsTier_02060718.log

                  Completed FSCloneStage...

                  Tue Feb  6 07:19:24 2018

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

                  PROGRAM : (/u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl)

                  TIME    : Tue Feb  6 07:19:25 2018

                  FUNCTION: main::validateCloneStage [ Level 1 ]

                  ERRORMSG: Could not find the log file under /u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/admin/log/clone.

                   

                   

                                  [UNEXPECTED]Error occurred while executing "perl /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -patchcontextfile=/u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -promptmsg=hide -console=off -mode=migrate -sessionid=15 -timestamp=20180206_071511 -outdir=/u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini"

                                  [UNEXPECTED]Error occurred while CONFIG_CLONE Patch File System from Run File System using command: "perl /u02/oracle/VISMA/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/u02/oracle/VISMA/fs2/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -patchcontextfile=/u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/appl/admin/VISMA_hydaswini.xml -promptmsg=hide -console=off -mode=migrate -sessionid=15 -timestamp=20180206_071511 -outdir=/u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/prepare_20180206_071511/VISMA_hydaswini".

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

                                  [UNEXPECTED]Error while runPendingConfigClone sub-routine is called

                                    [EVENT]     [START 2018/02/06 07:19:26] Check and Stop patch FS Admin Server

                   

                   

                  You are running adadminsrvctl.sh version 120.10.12020000.9

                   

                   

                   

                   

                  The AdminServer is already shutdown

                   

                   

                  adadminsrvctl.sh: exiting with status 2

                   

                   

                  adadminsrvctl.sh: check the logfile /u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/logs/appl/admin/log/adadminsrvctl.txt for more information ...

                   

                   

                                    [EVENT]     [END   2018/02/06 07:19:29] Check and Stop patch FS Admin Server

                                    [EVENT]     [START 2018/02/06 07:19:29] Check and Stop patch Node Manager

                   

                   

                  You are running adnodemgrctl.sh version 120.11.12020000.11

                   

                   

                   

                   

                  The Node Manager is already shutdown

                   

                   

                  adnodemgrctl.sh: exiting with status 2

                   

                   

                  adnodemgrctl.sh: check the logfile /u02/oracle/VISMA/fs1/inst/apps/VISMA_hydaswini/logs/appl/admin/log/adnodemgrctl.txt for more information ...

                   

                   

                                    [EVENT]     [END   2018/02/06 07:19:34] Check and Stop patch Node Manager

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

                                  Log file: /u02/oracle/VISMA/fs_ne/EBSapps/log/adop/15/adop_20180206_071511.log

                   

                   

                   

                   

                  [STATEMENT] Please run adopscanlog utility, using the command

                   

                   

                  "adopscanlog -latest=yes"

                   

                   

                  to get the list of the log files along with snippet of the error message corresponding to each log file.

                   

                   

                   

                   

                  adop exiting with status = 1 (Fail)

                   

                   

                  real    4m24.467s

                  user    3m32.509s

                  sys     0m19.723s

                  • 7. Re: ADOP PHASE=PREPRE FAILED
                    Ramaraju

                    Below is the previous ADOP session which is completed successfully.

                    $ cat status_20170116_143349/adzdshowstatus.out

                    Current Patching Session ID: 10

                    Node Name       Node Type       Phase           Status          Started                        Finished                       Elapsed

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

                    hydaswini       master          PREPARE         COMPLETED       14-JAN-17 06:27:37 -05:00      14-JAN-17 23:46:07 -05:00      17:18:30

                                                    APPLY           COMPLETED       16-JAN-17 04:08:19 -05:00      16-JAN-17 12:23:05 -05:00      8:14:46

                                                    FINALIZE        COMPLETED       16-JAN-17 12:27:09 -05:00      16-JAN-17 12:27:38 -05:00      0:00:29

                                                    CUTOVER         COMPLETED       16-JAN-17 12:29:46 -05:00      16-JAN-17 12:47:00 -05:00      0:17:14

                                                    CLEANUP         COMPLETED       16-JAN-17 12:48:50 -05:00      16-JAN-17 13:45:26 -05:00      0:56:36

                    File System Synchronization Used in this Patching Cycle: Full

                     

                     

                     

                     

                    Below is the previous ADOP fs_clone session which is completed successfully.

                    $ cat status_20170116_193801/adzdshowstatus.out

                    Current Patching Session ID: 11

                    Node Name       Node Type       Phase           Status          Started                        Finished                       Elapsed

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

                    hydaswini       master          FS_CLONE        COMPLETED       16-JAN-17 03:03:13 -05:00      16-JAN-17 06:11:34 -05:00      3:08:21

                                                    PREPARE         NOT APPLICABLE

                                                    APPLY           NOT APPLICABLE

                                                    CUTOVER         NOT APPLICABLE

                                                    CLEANUP         NOT APPLICABLE

                    File System Synchronization Used in this Patching Cycle: Full

                     

                     

                     

                     

                    Below is the present ADOP session.

                    $ cat status_20180206_072035/adzdshowstatus.out

                    Current Patching Session ID: 15

                    Node Name       Node Type       Phase           Status          Started                        Finished                       Elapsed

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

                    hydaswini       master          PREPARE         FAILED          05-FEB-18 20:06:17 -05:00      06-FEB-18 07:19:34 -05:00      11:13:17

                                                    APPLY           NOT STARTED

                                                    FINALIZE        NOT STARTED

                                                    CUTOVER         NOT STARTED

                                                    CLEANUP         NOT STARTED

                    File System Synchronization Used in this Patching Cycle: None

                     

                     

                    Thanks,

                    Ramaraju

                    • 8. Re: ADOP PHASE=PREPRE FAILED
                      Magnanimous

                      Hello Rama,

                       

                      1. Checks if Apps/System/Weblogic Passwords are correct.
 Checks if Context File is Valid
Checks if RUN and PATCH edition file system has READ/WRITE permission.
 Checks if environment variable RUN and PATCH edition are correct.
Checks if 25GB free space is available on the PATCH edition file system. 


                      2. Shut down the application and database, if you see any process please kill. - If this is test instance and possible to take down.


                      3. Abort the session


                      4. Try to start the prepare phase.


                      
 

                      Please share the result.

                      • 9. Re: ADOP PHASE=PREPRE FAILED
                        Ramaraju

                        1. Checks if Apps/System/Weblogic Passwords are correct.
 Checks if Context File is Valid
Checks if RUN and PATCH edition file system has READ/WRITE permission.
 Checks if environment variable RUN and PATCH edition are correct.
Checks if 25GB free space is available on the PATCH edition file system. 


                        ---> All passwords are correct, if wrong we can get error like invalid credentials

                        ---> We have permissions

                        ---> RUN & PATCH editions are correct

                        ---> We have 80 GB of free space

                         

                        2. Shut down the application and database, if you see any process please kill. - If this is test instance and possible to take down.


                        ---> Done the same thing

                         

                        3. Abort the session


                        ---> Yes

                         

                        4. Try to start the prepare phase

                        ---> Still facing same issue.

                         

                        I have ran autoconfig on DB & Apps tiers, still facing same issue.

                         

                        Thanks,

                        Ramaraju

                        • 10. Re: ADOP PHASE=PREPRE FAILED
                          Magnanimous

                          Ok, Please upload the clone log ?

                          • 11. Re: ADOP PHASE=PREPRE FAILED
                            Magnanimous

                            Have you tried to run fs_clone before prepare ? If not can you do that ?

                            • 12. Re: ADOP PHASE=PREPRE FAILED
                              Ramaraju

                              Yes, I have tried.

                               

                              Thanks,

                              Ramaraju

                              • 13. Re: ADOP PHASE=PREPRE FAILED
                                Ramaraju

                                Hi,

                                Please find the attached document here

                                https://ufile.io/ufv44

                                • 14. Re: ADOP PHASE=PREPRE FAILED
                                  Magnanimous

                                  Ok, Checking logs.

                                  1 2 3 上一个 下一个