5 Replies Latest reply on Nov 24, 2019 5:04 PM by Mohammed Ali A. Syed

    EBS 12.2.9 - How to abort failed patching cycle?

    Beauty_and_dBest

      Hi ALL,

       

      I have started and ADOP patching cycle, and it failed on APPLY phase.

      I tried to abort it but even the abort phase failed as well.

       

      $ adop phase=abort

       

      Enter the APPS password:

      Enter the SYSTEM password:

      Enter the WLSADMIN password:

       

      Validating credentials.

       

      Initializing.

          Run Edition context  : /u02/apptest1/TEST1/fs1/inst/apps/TEST1_lcctest2/appl        /admin/TEST1_lcctest2.xml

          Patch edition context: /u02/apptest1/TEST1/fs2/inst/apps/TEST1_lcctest2/appl        /admin/TEST1_lcctest2.xml

          Patch file system free space: 91.85 GB

       

      Validating system setup.

          Node registry is valid.

          [WARNING]   MTCC has not been run. Apply Patch 17537119 and run checkMTpatch.sh.

       

      Checking for existing adop sessions.

          Continuing with existing session [Session ID: 11].

              Session Id            :   11

              Prepare phase status  :   COMPLETED

              Apply phase status    :   ATLEAST ONE PATCH IS ALREADY APPLIED

              Cutover  phase status :   NOT COMPLETED

              Abort phase status    :   RUNNING

              Session status        :   FAILED

      The above session will be aborted. Do you want to continue [Y/N]? Y

       

       

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

      ADOP (C.Delta.11)

      Session ID: 11

      Node: lcctest2

      Phase: abort

      Log: /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191122_090434/adop.log

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

       

      Running abort phase DDL in DDL handler table.

          Log: /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191122_090434/abort/lcctest2/log/abort.log

       

       

      The table FND_INSTALL_PROCESSES created by AD Administration already exists.

      You should check the file

      /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191122_090434/abort/lcctest2/log/abort.log

       

      for errors.

       

          [UNEXPECTED]Error occurred in ABORT.

       

          [UNEXPECTED]Abort phase has failed.

       

      [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

       

       

      $ adopscanlog -latest=yes

       

      Scanning /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/ directory ...

      /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191122_090434/adop.log:

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

      Lines #(103-109):

          [EVENT]     Log: /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191122_090434/abort/lcctest2/log/abort.log

          [PROCEDURE] Running: adpatch options=hotpatch,nocompiledb interactive=no console=no workers=4 restart=no abandon=yes defaultsfile=/u02/apptest1/TEST1/fs1/EBSapps/appl/admin/TEST1/adalldefaults.txt patchtop=/u02/apptest1/TEST1/fs1/EBSapps/appl/ad/12.0.0/patch/115/driver logfile=abort.log driver=uabort.drv acp=yes

          [UNEXPECTED]Error occurred in ABORT.

       

          [UNEXPECTED]Abort phase has failed.

          [PROCEDURE] [START 2019/11/22 09:06:55] Updating session timestamps

          [STATEMENT] ABORT Phase END TIME: 22-11-2019 09:06:56

       

       

       

      Please help how to  resolve this issue.

       

      Kind regards,

      jc

        • 1. Re: EBS 12.2.9 - How to abort failed patching cycle?
          mdtaylor

          Hi jc,

           

          Please use adadmin to see if you can drop this table then.

           

          ERP on DB: adpatch: Drop FND_INSTALL_PROCESSES table [No] ?

           

          Regards,

          Michael

          • 2. Re: EBS 12.2.9 - How to abort failed patching cycle?
            Maaz Khan

            Hello Jc,

             

            Can you please review below log and let us know -

             

            /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191122_090434/abort/lcctest2/log/abort.log

             

             

             

             

            • 3. Re: EBS 12.2.9 - How to abort failed patching cycle?
              Beauty_and_dBest

              Hi Maaz and Michael,

               

              If I run adadmin, there is no option to drop the table, but I just exit right away with the error:

               

              $ adop -status

              Enter the APPS password:
              Connected.
              ==============================================================
              ADOP (C.Delta.11)
              Session Id: 11
              Command: status
              Output: /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191124_052516/adzdshowstatus.out
              ===============================================================
              Node Name       Node Type  Phase           Status          Started             Finished      Elapsed
              --------------- ---------- --------------- --------------- -------------------- -------------------- ------------
              lcctest2        master     PREPARE         COMPLETED       2019/11/22 06:07:09 2019/11/22 06:31:06  0:23:57
                                         APPLY           FAILED          2019/11/22 06:56:36 2019/11/22 06:57:03  0:00:27
                                         FINALIZE        NOT STARTED
                                         CUTOVER         NOT STARTED
                                         CLEANUP         NOT STARTED

              File System Synchronization Type: Full

              adop exiting with status = 0 (Success)

               

              $ adop phase=abort

              Enter the APPS password:
              Enter the SYSTEM password:
              Enter the WLSADMIN password:

              Validating credentials.

              Initializing.
                  Run Edition context  : /u02/apptest1/TEST1/fs1/inst/apps/TEST1_lcctest2/appl/admin/TEST1_lcctest2.xml
                  Patch edition context: /u02/apptest1/TEST1/fs2/inst/apps/TEST1_lcctest2/appl/admin/TEST1_lcctest2.xml
                  Patch file system free space: 91.74 GB

              Validating system setup.
                  Node registry is valid.
                  [WARNING]   MTCC has not been run. Apply Patch 17537119 and run checkMTpatch.sh.

              Checking for existing adop sessions.
                  Continuing with existing session [Session ID: 11].
                      Session Id            :   11
                      Prepare phase status  :   COMPLETED
                      Apply phase status    :   ATLEAST ONE PATCH IS ALREADY APPLIED
                      Cutover  phase status :   NOT COMPLETED
                      Abort phase status    :   RUNNING
                      Session status        :   FAILED
              The above session will be aborted. Do you want to continue [Y/N]? Y

              ===========================================================================
              ADOP (C.Delta.11)
              Session ID: 11
              Node: lcctest2
              Phase: abort
              Log: /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191124_052534/adop.log
              ===========================================================================

              Running abort phase DDL in DDL handler table.
                  Log: /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191124_052534/abort/lcctest2/log/abort.log

              The table FND_INSTALL_PROCESSES created by AD Administration already exists.
              You should check the file
              /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191124_052534/abort/lcctest2/log/abort.log

              for errors.

                  [UNEXPECTED]Error occurred in ABORT.

                  [UNEXPECTED]Abort phase has failed.


              [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)

               


              The table FND_INSTALL_PROCESSES created by AD Administration already exists.
              You should check the file
              /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191122_090434/abort/lcctest2/log/abort.log

              for errors.
              reating FND_INSTALL_PROCESSES table...

              Running adtasktim.sql ..

              Connected.
              Connected.

              PL/SQL procedure successfully completed.


              Commit complete.


              The table FND_INSTALL_PROCESSES created by AD Administration already exists.
              You should check the file
              /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191122_090434/abort/lcctest2/log/abort.log

              for errors.

               

               

              I also check  log > /u02/apptest1/TEST1/fs_ne/EBSapps/log/adop/11/20191122_090434/abort/lcctest2/log/abort.log

              But it has the same contents as the above file.

               

               

              Please help...

               

              Kind regards,

              • 4. Re: EBS 12.2.9 - How to abort failed patching cycle?
                aspardhya

                Bounce the Admin Server and re-run abort, and see if it helps.

                • 5. Re: EBS 12.2.9 - How to abort failed patching cycle?
                  Mohammed Ali A. Syed

                  Hi,

                  $ adop phase=abort

                  Enter the APPS password:
                  Enter the SYSTEM password:
                  Enter the WLSADMIN password:

                  Validating credentials.

                  Initializing.
                      Run Edition context  : /u02/apptest1/TEST1/fs1/inst/apps/TEST1_lcctest2/appl/admin/TEST1_lcctest2.xml
                      Patch edition context: /u02/apptest1/TEST1/fs2/inst/apps/TEST1_lcctest2/appl/admin/TEST1_lcctest2.xml
                      Patch file system free space: 91.74 GB

                  Validating system setup.
                      Node registry is valid.
                      [WARNING]   MTCC has not been run. Apply Patch 17537119 and run checkMTpatch.sh.

                  Checking for existing adop sessions.
                      Continuing with existing session [Session ID: 11].
                          Session Id            :   11
                          Prepare phase status  :   COMPLETED
                          Apply phase status    :   ATLEAST ONE PATCH IS ALREADY APPLIED
                          Cutover  phase status :   NOT COMPLETED
                          Abort phase status    :   RUNNING
                          Session status        :   FAILED

                  The above session will be aborted. Do you want to continue [Y/N]? Y

                  The above session will be aborted. Do you want to continue [Y/N]? Y

                   

                   

                  You answered yes, so it will continue the last failed apply phase.

                   

                  You should answer N to this, then it will drop the table FND_INSTALL_PROCESSES and will run the abort phase.

                   

                  Thanks