1 2 Previous Next 22 Replies Latest reply on Apr 6, 2016 1:35 AM by Beauty_and_dBest

    Patch says complete but status is still active

    Beauty_and_dBest

      Hi ALL,

       

      EBS R12.2.4

      OL6

      11gR2

       

       

      I am running adop patch=prepare, but it failed because there is pending active apply phase

      How do I abort,cancel, or abandon this pending apply?

       

      Thanks a lot,

      jc

       

      Current Patching Session ID: 25

       

      Node Name       Node Type       Phase           Status          Started                        Finished                       Elapsed

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

      prodapp         master          PREPARE         NOT APPLICABLE

                                      APPLY           ACTIVE          15-JAN-16 02:58:20 +08:00      15-JAN-16 03:14:09 +08:00      0:15:49

                                      FINALIZE        NOT APPLICABLE

                                      CUTOVER         NOT APPLICABLE

                                      CLEANUP         NOT STARTED

       

      File System Synchronization Used in this Patching Cycle: None

       

       

      File System Information:

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

      File System: SINGLE NODE INSTANCE

       

      Custom File System Synchronization script:  /EBSapps/appl/ad/custom/adop_sync.drv

       

      Patch Stage Top:  /EBSapps/patch

       

      Online Patching Log base:  /EBSapps/log/adop/25

       

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

      =             Patches Applied in the Current Patching Cycle

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

       

      Node Name    Node Type Patch         Status         Run ID File System Patch Base    File System Applied Base  Adpatch Parameters   Session Type

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

      prodapp      master    21068635      Y               31354                           /home/appprod/PROD/fs1    hotpatch             HOTPATCH

       

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

      =             ADADMIN actions in the Current Patching Cycle

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

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

      = There is no Online Patching Cycle in progress at this time.

      = Report sections dependent upon Patch Edition will have no output.

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

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

      =                 Summary of the Last 10 ADOP Cycles

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

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

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

              25 prodapp    master    15-JAN-16  0:00:00          0:00:00          0:00:00          0:14:06         COMPLETE     21068635             HOTPATCH

              24 apps       master    15-OCT-14  0:22:35          0:19:22          12:42:53         0:00:00         COMPLETE     --                   --

              23 apps       master    14-OCT-14  0:35:28          0:28:54          0:01:42          0:05:47         COMPLETE     19445058             ONLINE

                            master                                                                  0:13:09         COMPLETE     19581770             ONLINE

                            master                                                                  0:22:07         COMPLETE     CONFIG_CLONE      CONFIG_CLONE

                            master                                                                  0:13:09         COMPLETE     19581770             ONLINE

                            master                                                                  0:22:07         COMPLETE     CONFIG_CLONE      CONFIG_CLONE

                            slave                0:00:00          0:00:00          0:00:00          0:00:00         COMPLETE     CONFIG_CLONE      CONFIG_CLONE

              21 apps       master    09-SEP-14  0:11:46          0:22:55          0:01:51          0:00:00         COMPLETE     --                   --

              20 apps       master    09-SEP-14  0:14:20          1:16:06          0:02:55          0:00:00         COMPLETE     --                   --

              19 apps       master    05-SEP-14  3:01:14          0:20:26          0:02:50          0:00:00         COMPLETE     --                   --

              18 apps       master    04-SEP-14  0:23:30          0:26:14          1:49:58          0:12:40         COMPLETE     CONFIG_CLONE      CONFIG_CLONE

                            master                                                                  4:32:49         COMPLETE     18122014             ONLINE

                            slave                0:00:00          0:00:00          0:00:00          0:00:00         COMPLETE     CONFIG_CLONE      CONFIG_CLONE

              17 apps       master    03-SEP-14  0:28:29          1:56:09          0:06:05          0:18:20         COMPLETE     CONFIG_CLONE      CONFIG_CLONE

                            slave                0:00:00          0:00:00          0:00:00          0:00:00         COMPLETE     CONFIG_CLONE      CONFIG_CLONE

              16 apps       master    02-SEP-14  6:45:26          0:28:03          0:01:26          0:00:00         COMPLETE     --                   --

       

       

      ~

        • 1. Re: Patch says complete but status is still active
          Bashar.

          Hi,

           

          You have applied a patch in hotpatch mode.

          You must run fs_clone before you can start a new patching cycle. This has been mentioned before in separate discussions, right?

           

          Regards,

          Bashar

          1 person found this helpful
          • 2. Re: Patch says complete but status is still active
            Beauty_and_dBest

            Thanks bashar, you are really and angel

             

            I thought adop=prepare will take care of everything

            • 3. Re: Patch says complete but status is still active
              Beauty_and_dBest

              Hi Bashar,

               

              I run > adop phase=fs_clone , then run prepare  but I still got error

               

              [appprod@uat PATCH]$ adop phase=prepare

               

              Enter the APPS password:

              Enter the SYSTEM password:

              Enter the WLSADMIN password:

               

              Please wait. Validating credentials...

               

              RUN file system context file: /u01/appprod/PROD/fs1/inst/apps/PROD_uat/appl/admin/PROD_uat.xml

              PATCH file system context file: /u01/appprod/PROD/fs2/inst/apps/PROD_uat/appl/admin/PROD_uat.xml

              Execute SYSTEM command : df /u01/appprod/PROD/fs2

               

              Worker count determination...

               

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

              [EVENT]     [START 2016/04/03 21:46:31] Performing database sanity checks

              [EVENT]     [END   2016/04/03 21:46:33] Finished performing database sanity checks

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

                      Session Id            :   27

                      Prepare phase status  :   NOT COMPLETED

                      Apply phase status    :   NOT COMPLETED

                      Cutover  phase status :   NOT COMPLETED

                      Abort phase status    :   NOT COMPLETED

                      Session status        :   FAILED

                Will continue with previous session

                [START 2016/04/03 21:46:35] adzdoptl.pl run

                  ADOP Session ID: 27

                  Phase: prepare

                  Log file: /u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/adop_20160403_214600.log

                  [EVENT]     [START 2016/04/03 21:46:37] Calling task: "Executing txkADOPValidation script on uat"; script: "/u01/appprod/PROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl"; args: " -contextfile=/u01/appprod/PROD/fs1/inst/apps/PROD_uat/appl/admin/PROD_uat.xml -patchctxfile=/u01/appprod/PROD/fs2/inst/apps/PROD_uat/appl/admin/PROD_uat.xml -phase=prepare -logloc=/u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/prepare_20160403_214600/PROD_uat -promptmsg=hide"

                    [EVENT]     [START 2016/04/03 21:46:37] Executing txkADOPValidation script on uat

                      [EVENT]     Calling: /u01/appprod/PROD/fs1/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: /u01/appprod/PROD/fs1/FMW_Home/webtier/perl/bin/perl /u01/appprod/PROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkValidateSetup.pl -contextfile=/u01/appprod/PROD/fs1/inst/apps/PROD_uat/appl/admin/PROD_uat.xml -patchctxfile=/u01/appprod/PROD/fs2/inst/apps/PROD_uat/appl/admin/PROD_uat.xml -logloc=/u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/prepare_20160403_214600/PROD_uat -phase=prepare -promptmsg=hide

               

              Program : txkValidateSetup.pl started @ Sun Apr  3 21:46:41 2016

               

              *** Log File = /u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/prepare_20160403_214600/PROD_uat/ADOPValidations_Sun_Apr_3_21_46_41_2016.log

               

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

                      [UNEXPECTED]Error occurred while executing "perl /u01/appprod/PROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl  -contextfile=/u01/appprod/PROD/fs1/inst/apps/PROD_uat/appl/admin/PROD_uat.xml -patchctxfile=/u01/appprod/PROD/fs2/inst/apps/PROD_uat/appl/admin/PROD_uat.xml -phase=prepare -logloc=/u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/prepare_20160403_214600/PROD_uat -promptmsg=hide"

                      [UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script on uat

                      Log file: /u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/adop_20160403_214600.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)

               

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

              Current Patching Session ID: 27

               

              Node Name       Node Type       Phase           Status          Started                        Finished                    Elapsed

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

              uat             master          PREPARE         NOT STARTED

                                              APPLY           NOT STARTED

                                              FINALIZE        NOT STARTED

                                              CUTOVER         NOT STARTED

                                              CLEANUP         NOT STARTED

               

              File System Synchronization Used in this Patching Cycle: Full

               

              INFORMATION: Patching cycle aborted, so fs_clone will run automatically on uat node in prepare phase of next patching cycle.

               

              File System Information:

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

              File System: SINGLE NODE INSTANCE

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

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

              uat         master      /u01/appprod/PROD/fs1          /u01/appprod/PROD/fs2          /u01/appprod/PROD/fs_ne        /u01/appprod/PROD/fs1/

                                                                                                                                    inst/apps/PROD_uat

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

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

              Online Patching Log base: /u01/appprod/PROD/fs_ne/EBSapps/log/adop/27

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

              =             Patches Applied in the Current Patching Cycle

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

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

              =             ADADMIN actions in the Current Patching Cycle

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

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

              = There is no Online Patching Cycle in progress at this time.

              = Report sections dependent upon Patch Edition will have no output.

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

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

              =                 Summary of the Last 10 ADOP Cycles

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

               

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

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

                      27 uat        master               0:00:00          0:00:00          0:00:00          0:00:00         FAILED       --                   --

                      26 uat        master    03-APR-16  0:00:00          0:00:00          0:00:00          0:00:00         NOT-STARTED  CLONE                CLONE

                      25 prodapp    master    15-JAN-16  0:00:00          0:00:00          0:00:00          0:14:06         COMPLETE     21068635             HOTPATCH

                      24 apps       master    15-OCT-14  0:22:35          0:19:22          12:42:53         0:00:00         COMPLETE     --                   --

                      23 apps       master    14-OCT-14  0:35:28          0:28:54          0:01:42          0:05:47         COMPLETE     19445058             ONLINE

                                    master                                                                  0:13:09         COMPLETE     19581770             ONLINE

                                    master                                                                  0:22:07         COMPLETE     CONFIG_CLONE      CONFIG_CLONE

                                    slave                0:00:00          0:00:00          0:00:00          0:00:00         COMPLETE     CONFIG_CLONE      CONFIG_CLONE

                      21 apps       master    09-SEP-14  0:11:46          0:22:55          0:01:51          0:00:00         COMPLETE     --                   --

                      20 apps       master    09-SEP-14  0:14:20          1:16:06          0:02:55          0:00:00         COMPLETE     --                   --

                      19 apps       master    05-SEP-14  3:01:14          0:20:26          0:02:50          0:00:00         COMPLETE     --                   --

                      18 apps       master    04-SEP-14  0:23:30          0:26:14          1:49:58          0:12:40         COMPLETE     CONFIG_CLONE      CONFIG_CLONE

                                    master                                                                  4:32:49         COMPLETE     18122014             ONLINE

                                    slave                0:00:00          0:00:00          0:00:00          0:00:00         COMPLETE     CONFIG_CLONE      CONFIG_CLONE

              • 4. Re: Patch says complete but status is still active
                Bashar.

                Did the fs_clone complete successfully?

                Did you source the run file system environment before you started?

                 

                Regards,

                Bashar

                1 person found this helpful
                • 5. Re: Patch says complete but status is still active
                  Beauty_and_dBest

                  Yes my default env is run fs.

                   

                  But the fs_clone did not complete successfully. It abort and  messaged like it will be done during prepare.

                  • 6. Re: Patch says complete but status is still active
                    Bashar.

                    Please run fs_clone again and post the errors/messages you encounter.

                     

                    Regards,

                    Bashar

                    • 7. Re: Patch says complete but status is still active
                      Beauty_and_dBest

                      Hi bashar,

                       

                      Below is the error:

                       

                      [appprod@uat PATCH]$ adop phase=fs_clone

                       

                      Enter the APPS password:

                      Enter the SYSTEM password:

                      Enter the WLSADMIN password:

                       

                      Please wait. Validating credentials...

                       

                      RUN file system context file: /u01/appprod/PROD/fs1/inst/apps/PROD_uat/appl/admin/PROD_uat.xml

                       

                      PATCH file system context file: /u01/appprod/PROD/fs2/inst/apps/PROD_uat/appl/admin/PROD_uat.xml

                      Execute SYSTEM command : df /u01/appprod/PROD/fs2

                       

                      Worker count determination...

                       

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

                      [EVENT]     [START 2016/04/03 23:44:10] Performing database sanity checks

                      [EVENT]     [END   2016/04/03 23:44:20] Finished performing database sanity checks

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

                              Session Id            :   27

                              Prepare phase status  :   NOT COMPLETED

                              Apply phase status    :   NOT COMPLETED

                              Cutover  phase status :   NOT COMPLETED

                              Abort phase status    :   NOT COMPLETED

                              Session status        :   FAILED

                        Will continue with previous session

                        [UNEXPECTED]FS clone cannot be called while a patching cycle is active

                       

                      [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 = 2 (Fail)

                      [appprod@uat PATCH]$ adopscanlog -latest=yes

                       

                      Scanning /u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/ directory ...

                       

                      /u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/adop_20160403_214600.log:

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

                       

                      Lines #(102-106):

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

                              [STATEMENT] Output directory: /u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/prepare_20160403_214600/PROD_uat

                              [UNEXPECTED]Error occurred while executing "perl /u01/appprod/PROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl  -contextfile=/u01/appprod/PROD/fs1/inst/apps/PROD_uat/appl/admin/PROD_uat.xml -patchctxfile=/u01/appprod/PROD/fs2/inst/apps/PROD_uat/appl/admin/PROD_uat.xml -phase=prepare -logloc=/u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/prepare_20160403_214600/PROD_uat -promptmsg=hide"

                              [UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script on uat

                              [PROCEDURE] [START 2016/04/03 21:46:56] Unlocking sessions table

                       

                      Lines #(103-107):

                              [STATEMENT] Output directory: /u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/prepare_20160403_214600/PROD_uat

                              [UNEXPECTED]Error occurred while executing "perl /u01/appprod/PROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl  -contextfile=/u01/appprod/PROD/fs1/inst/apps/PROD_uat/appl/admin/PROD_uat.xml -patchctxfile=/u01/appprod/PROD/fs2/inst/apps/PROD_uat/appl/admin/PROD_uat.xml -phase=prepare -logloc=/u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/prepare_20160403_214600/PROD_uat -promptmsg=hide"

                              [UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script on uat

                              [PROCEDURE] [START 2016/04/03 21:46:56] Unlocking sessions table

                                [STATEMENT] Unlocking ad_adop_sessions table for uat with wait interval of 60 seconds and number of tries 2

                       

                      /u01/appprod/PROD/fs_ne/EBSapps/log/adop/27/prepare_20160403_214600/PROD_uat/ADOPValidations_Sun_Apr_3_21_46_41_2016.log:

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

                       

                      Lines #(75-79):

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

                       

                      ERROR:

                      Nodes with context files in the FND_OAM_CONTEXT_FILES table on both run and patch file systems: NONE

                      Nodes without context files in the FND_OAM_CONTEXT_FILES table on either/or run and patch file systems: uat

                      • 8. Re: Patch says complete but status is still active
                        Bashar.

                        Please post the contents of the FND_OAM_CONTEXT_FILES table.

                         

                        Regards,

                        Bashar

                        1 person found this helpful
                        • 9. Re: Patch says complete but status is still active
                          Beauty_and_dBest

                          Hi Bashar and ALL,

                           

                          Capture.PNG

                          Capture2.PNG

                          Capture3.PNG

                           

                          Kind regards,

                          • 10. Re: Patch says complete but status is still active
                            Bashar.

                            Your patch context file information is missing. Please do the following:

                             

                            1. Abort the current patching cycle.
                            2. Source the patch file system environment.
                            3. Run the command "sh $AD_TOP/bin/adconfig.sh contextfile=/u01/appprod/PROD/fs2/inst/apps/PROD_uat/appl/admin/PROD_uat.xml -syncctx" to run AutoConfig and synchronize the file system with the database.
                            4. Query the table again and make sure that there are new records for fs2.
                            5. Source the run file system environment.
                            6. Perform fs_clone.

                             

                            Regards,

                            Bashar

                            1 person found this helpful
                            • 11. Re: Patch says complete but status is still active
                              Beauty_and_dBest

                              Thanks bashar , it seems cloning now, running for a longer time.

                              • 12. Re: Patch says complete but status is still active
                                Beauty_and_dBest

                                Hi bashar and ALL,

                                 

                                I completed the adop=prepare.

                                Then I run the next 4 commands as:

                                 

                                adop phase=apply,finalize,cutover,cleanup patches=20221271 patchtop=/home/PATCH

                                 

                                But I got error again

                                 

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

                                 

                                RUN file system context file: /u01/appprod/PROD/fs1/inst/apps/PROD_uat/appl/admin/PROD_uat.xml

                                PATCH file system context file: /u01/appprod/PROD/fs2/inst/apps/PROD_uat/appl/admin/PROD_uat.xml

                                Execute SYSTEM command : df /u01/appprod/PROD/fs2

                                Worker count determination...

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

                                [EVENT]     [START 2016/04/05 05:39:49] Performing database sanity checks

                                [EVENT]     [END   2016/04/05 05:39:52] Finished performing database sanity checks

                                  Using ADOP Session ID from currently incomplete patching cycle

                                [START 2016/04/05 05:39:54] adzdoptl.pl run

                                  ADOP Session ID: 29

                                  Phase: apply,finalize,cutover,cleanup

                                  Log file: /u01/appprod/PROD/fs_ne/EBSapps/log/adop/29/adop_20160405_053929.log

                                  [START 2016/04/05 05:39:56] apply phase

                                      Calling: adpatch  abandon=yes restart=no workers=3      console=no interactive=no  defaultsfile=/u01/appprod/PROD/fs2/EBSapps/appl/admin/PROD_patch/adalldefaults.txt patchtop=/home/PATCH/20221271 driver=u20221271.drv logfile=u20221271.log

                                      ADPATCH Log directory: /u01/appprod/PROD/fs_ne/EBSapps/log/adop/29/apply_20160405_053929/PROD_uat/20221271/log

                                ***

                                Continue as if it were successful :

                                ***

                                AutoPatch could not find a response to the above prompt

                                in the defaults file.

                                The patch has FAILED,

                                Please check the adpatch logs for more details.

                                You should check the file

                                /u01/appprod/PROD/fs_ne/EBSapps/log/adop/29/apply_20160405_053929/PROD_uat/20221271/log/u20221271.log

                                for errors.

                                      [UNEXPECTED]Error occurred while executing "adpatch  abandon=yes restart=no workers=3      console=no interactive=no  defaultsfile=/u01/appprod/PROD/fs2/EBSapps/appl/admin/PROD_patch/adalldefaults.txt patchtop=/home/PATCH/20221271 driver=u20221271.drv logfile=u20221271.log"

                                      [UNEXPECTED]Please check the adpatch log files.

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

                                      Log file: /u01/appprod/PROD/fs_ne/EBSapps/log/adop/29/adop_20160405_053929.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)

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

                                 

                                      ADPATCH Log directory: /u01/appprod/PROD/fs_ne/EBSapps/log/adop/29/apply_20160405_053929/PROD_uat/20221271/log

                                      [PROCEDURE] Running: adpatch  abandon=yes restart=no workers=3      console=no interactive=no  defaultsfile=/u01/appprod/PROD/fs2/EBSapps/appl/admin/PROD_patch/adalldefaults.txt patchtop=/home/PATCH/20221271 driver=u20221271.drv logfile=u20221271.log acp=yes

                                      [UNEXPECTED]Error occurred while executing "adpatch  abandon=yes restart=no workers=3      console=no interactive=no  defaultsfile=/u01/appprod/PROD/fs2/EBSapps/appl/admin/PROD_patch/adalldefaults.txt patchtop=/home/PATCH/20221271 driver=u20221271.drv logfile=u20221271.log"

                                      [UNEXPECTED]Please check the adpatch log files.

                                      [STATEMENT] sql stmt : <     update ad_adop_session_patches set  status='F'

                                     where adop_session_id=29

                                     and status='R'

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

                                      [STATEMENT] SQL statement : "  update ad_adop_sessions

                                  set status='F'

                                   where adop_session_id = 29 and appltop_id = 197 and node_name='uat'

                                      [STATEMENT] APPLY Phase END TIME: 05-04-2016 05:45:05

                                      [PROCEDURE] [START 2016/04/05 05:45:05] Unlocking sessions table

                                        [STATEMENT] Unlocking ad_adop_sessions table for uat with wait interval of 60 seconds and number of tries 2

                                      [PROCEDURE] [END   2016/04/05 05:45:05] Unlocking sessions table

                                      [STATEMENT] SQL statement : "  update ad_adop_sessions

                                  set status='F'

                                   where adop_session_id = 29 and appltop_id = 197 and node_name='uat'

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

                                 

                                FND_INSTALL_PROCESSES table dropped.

                                Dropping AD_DEFERRED_JOBS table...

                                DROP TABLE AD_DEFERRED_JOBS PURGE

                                AD_DEFERRED_JOBS table dropped.

                                The following Oracle Forms objects did not generate successfully:

                                 

                                ap      forms/US        APXINWKB.fmx

                                ap      forms/US        APXPMTCH.fmx

                                ap      forms/US        APXRMTCH.fmx

                                 

                                An error occurred while generating Oracle Forms files.

                                ***

                                Continue as if it were successful :

                                ***

                                AutoPatch could not find a response to the above prompt

                                in the defaults file.

                                The patch has FAILED,

                                Please check the adpatch logs for more details.

                                You should check the file

                                /u01/appprod/PROD/fs_ne/EBSapps/log/adop/29/apply_20160405_053929/PROD_uat/20221271/log/u20221271.log

                                for errors.

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

                                 

                                      [UNEXPECTED]Error occurred while executing "adpatch  abandon=yes restart=no workers=3      console=no interactive=no  defaultsfile=/u01/appprod/PROD/fs2/EBSapps/appl/admin/PROD_patch/adalldefaults.txt patchtop=/home/PATCH/20221271 driver=u20221271.drv logfile=u20221271.log"

                                      [UNEXPECTED]Please check the adpatch log files.

                                      [STATEMENT] sql stmt : <     update ad_adop_session_patches set  status='F'

                                Lines #(88-92):

                                      [PROCEDURE] Running: adpatch  abandon=yes restart=no workers=3      console=no interactive=no  defaultsfile=/u01/appprod/PROD/fs2/EBSapps/appl/admin/PROD_patch/adalldefaults.txt patchtop=/home/PATCH/20221271 driver=u20221271.drv logfile=u20221271.log acp=yes

                                      [UNEXPECTED]Error occurred while executing "adpatch  abandon=yes restart=no workers=3      console=no interactive=no  defaultsfile=/u01/appprod/PROD/fs2/EBSapps/appl/admin/PROD_patch/adalldefaults.txt patchtop=/home/PATCH/20221271 driver=u20221271.drv logfile=u20221271.log"

                                      [UNEXPECTED]Please check the adpatch log files.

                                      [STATEMENT] sql stmt : <     update ad_adop_session_patches set  status='F'

                                     where adop_session_id=29

                                Lines #(94-98):

                                >

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

                                      [STATEMENT] SQL statement : "  update ad_adop_sessions

                                  set status='F'

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

                                 

                                Current Patching Session ID: 29

                                Node Name       Node Type       Phase           Status          Started                        Finished                       Elapsed

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

                                uat             master          PREPARE         COMPLETED       05-APR-16 01:25:56 +08:00      05-APR-16 02:32:16 +08:00      1:06:20

                                                                APPLY           FAILED          05-APR-16 05:39:56 +08:00      05-APR-16 05:45:05 +08:00      0:05:09

                                                                FINALIZE        NOT STARTED

                                                                CUTOVER         NOT STARTED

                                                                CLEANUP         NOT STARTE

                                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

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

                                uat         master      /u01/appprod/PROD/fs1          /u01/appprod/PROD/fs2          /u01/appprod/PROD/fs_ne        /u01/appprod/PROD/fs1/inst/app

                                                                                                                                                     s/PROD_uat

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

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

                                Online Patching Log base: /u01/appprod/PROD/fs_ne/EBSapps/log/adop/29

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

                                =             Patches Applied in the Current Patching Cycle

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

                                Node Name    Node Type Patch         Status         Run ID File System Patch Base    File System Applied Base  Adpatch Parameters   Session Type

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

                                uat          master    20221271      F                  -1                           /u01/appprod/PROD/fs2                          ONLINE

                                 

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

                                =             ADADMIN actions in the Current Patching Cycle

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

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

                                =                 Summary of the Last 10 ADOP Cycles

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

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

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

                                        29 uat        master    05-APR-16  1:06:20          0:00:00          0:00:00          0:00:01         FAILED       20221271       ONLINE

                                        28 uat        master    05-APR-16  0:00:00          0:00:00          0:00:00          0:00:00         COMPLETE     CLONE           CLONE

                                • 13. Re: Patch says complete but status is still active
                                  Bashar.

                                  There are three forms that failed during generation.

                                  Check the workers logs to find the errors encountered and post them here.

                                   

                                  Regards,

                                  Bashar

                                  1 person found this helpful
                                  • 14. Re: Patch says complete but status is still active
                                    Beauty_and_dBest

                                    Thanks bashar,

                                     

                                    I already forgot how to find the corresponding worker logs

                                     

                                    Is adadmin still applicable in 12.2?

                                    Are these folders correct?

                                     

                                    Log files file Online patching (adop)

                                    The adop log files are located on the non-editioned file system (fs_ne), under:

                                    $NE_BASE/EBSapps/log/adop/<adop_session_id>/<phase>_<date>_<time>/<context_name>/log

                                    This log directory will contain patch logs, patch worker logs and other patch related log files created for specific purposes
                                    Also, some patch tasks may create separate log files in the same directory.

                                     

                                     

                                    Kind regards,

                                    1 2 Previous Next