6 Replies Latest reply on Feb 23, 2016 8:34 PM by Beauty_and_dBest

    Patching new instance

    Beauty_and_dBest

      Hi ALL,

       

      EBS R12.2.4

      OL 6.5

       

       

      We have a new instance name PRD,

      I am again initiating new adop prepare. But still encountered error.

      Every time I run of adop prepare, it generates different error.

      Capture.PNG

      Capture2.PNG

      Capture3.PNG

       

      Lines #(976-980):

      AutoPatch error:

      Error removing file:

      /u01/PATCH/21027021/backup/PRD/fitr12/pa/patch/115/sql/PAXFBPVDS.pls

       

      Lines #(981-985):

      AutoPatch error:

      Error removing file:

      /u01/PATCH/21027021/backup/PRD/fitr12/pa/patch/115/sql/PAXFFPPB.pls

       

      Lines #(986-990):

      AutoPatch error:

      Error removing file:

      /u01/PATCH/21027021/backup/PRD/fitr12/pa/patch/115/sql/PAXIBILB.pls

       

      /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160223_164104/PRD_fitr12/TXK_SYNC_update_Tue_Feb_23_16_44_51_2016/txkADOPPreparePhaseSynchronize_Tue_Feb_23_16_44_51_2016.log:

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

      Lines #(468-470):

      TIME    : Tue Feb 23 16:45:24 2016

      FUNCTION: main::execADPATCH [ Level 1 ]

      ERRORMSG: Application of patch did not go through successfully.

       

      Script done on Tue 23 Feb 2016 05:06:20 PM PHT

       

       

      Why is it removing lots of program files?

       

      Kind regards,

      jc

        • 1. Re: Patching new instance
          VishnuVinnakota

          As part of prepare, it includes Clone phase to sync the Run and Patch.

           

          As I see, it is trying to apply a patch(Sync) as part of prepare.

           

          What exactly do you mean by a New Instance? Did you clone or Install?

           

          Did you apply any patches on this instance before?

          1 person found this helpful
          • 2. Re: Patching new instance
            Beauty_and_dBest

            Yes, this is a clone from another instance which has patch applied but not in complete cylcle, like a hotpatch not done with fs_clone.

            Why is it has error removing files?

             

            I run adop prepare again at it changing the error?

             

            Thanks,

             

            $ 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/appprd/PRD/fs2/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml

            PATCH file system context file: /u02/appprd/PRD/fs1/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml

            Execute SYSTEM command : df /u02/appprd/PRD/fs1

            Worker count determination...

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

            [EVENT]     [START 2016/02/24 00:34:53] Performing database sanity checks

            [EVENT]     [END   2016/02/24 00:34:55] Finished performing database sanity checks

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

              Session Id            :   29

              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 2016/02/24 00:34:56] adzdoptl.pl run

                ADOP Session ID: 29

                Phase: prepare

                Log file: /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/adop_20160224_003436.log

                [EVENT]     [START 2016/02/24 00:34:57] Calling task: "Executing txkADOPValidation script on fitr12"; script: "/u02/appprd/PRD/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl"; args: " -contextfile=/u02/appprd/PRD/fs2/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml -patchctxfile=/u02/appprd/PRD/fs1/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml -phase=prepare -logloc=/u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12 -promptmsg=hide"

                  [EVENT]     [START 2016/02/24 00:34:57] Executing txkADOPValidation script on fitr12

                    [EVENT]     Calling: /u02/appprd/PRD/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/appprd/PRD/fs2/FMW_Home/webtier/perl/bin/perl /u02/appprd/PRD/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkValidateSetup.pl -contextfile=/u02/appprd/PRD/fs2/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml -patchctxfile=/u02/appprd/PRD/fs1/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml -logloc=/u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12 -phase=prepare -promptmsg=hide

            Program : txkValidateSetup.pl started @ Wed Feb 24 00:35:00 2016

            *** Log File = /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/ADOPValidations_Wed_Feb_24_00_35_00_2016.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: fitr12

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

            [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/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/ADOPValidations_Wed_Feb_24_00_35_00_2016.log

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

                  [EVENT]     [END   2016/02/24 00:36:26] Executing txkADOPValidation script on fitr12

                [EVENT]     [END   2016/02/24 00:36:26] Executing txkADOPValidation script on fitr12

                [START 2016/02/24 00:36:30] prepare phase

                  [EVENT]     [START 2016/02/24 00:36:31] Validating Configuration

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

            Program :  started @ Wed Feb 24 00:36:31 2016

            *** Log File = /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/TXK_SANITY_filesystemcheck_Wed_Feb_24_00_36_31_2016/txkADOPPreparePhaseSanityCheck_Wed_Feb_24_00_36_31_2016.log

            LOG FILE     : /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/TXK_SANITY_filesystemcheck_Wed_Feb_24_00_36_31_2016/txkADOPPreparePhaseSanityCheck_Wed_Feb_24_00_36_31_2016.log

            Program :  completed @ Wed Feb 24 00:36:32 2016

                  [EVENT]     [END   2016/02/24 00:36:32] Validating Configuration

                  [EVENT]     [START 2016/02/24 00:36:32] Detecting config changes in FS

                    [EVENT]     Calling task: "Executing adConfigChangeDetector on fitr12"; script: "/u02/appprd/PRD/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/adConfigChangeDetector.pl"; args: " -detectConfigChanges contextfile=/u02/appprd/PRD/fs2/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml promptmsg=hide log=/u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/adConfigChanges.log hostname=fitr12"

                    [EVENT]     [START 2016/02/24 00:36:33] Executing adConfigChangeDetector on fitr12

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

            The log file is /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/adConfigChanges.log

                    [EVENT]     [END   2016/02/24 00:36:36] Executing adConfigChangeDetector on fitr12

                  [EVENT]     [END   2016/02/24 00:36:36] Detecting config changes in FS

                  [EVENT]     [START 2016/02/24 00:36:36] Performing check to see if pending cleanup actions exist

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

                  [EVENT]     [END   2016/02/24 00:36:36] Performing check to see if pending cleanup actions exist

                  [EVENT]     [START 2016/02/24 00:36:36] Performing DB Sanity checks

                  [EVENT]     [END   2016/02/24 00:36:36] Performing DB Sanity checks

                  [START 2016/02/24 00:36:36] Generating Tablespace Report

                      [EVENT]     Report: /u02/appprd/PRD/fs2/EBSapps/appl/ad/12.0.0/sql/ADZDSHOWTS.sql

                      [EVENT]     Output: /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/adzdshowts.out

                  [END   2016/02/24 00:36:37] Generating Tablespace Report

                  [EVENT]     [START 2016/02/24 00:36:37] Run the ADZDPATCH concurrent program

                    [EVENT]     [START 2016/02/24 00:36:40] Checking status of the ADZDPATCH concurrent program

                      [EVENT]     Status of ADZDPATCH:

                      [EVENT]     This request is waiting to be processed by the Conflict Resolution

            Manager.  This request cannot yet begin execution because other requests

            may conflict with it. The Conflict Resolution Manager will determine when

            this request may begin execution. User SYSADMIN submitted this request on

            24-FEB-2016 00:36:39.  No action required. This is a normal condition.

                    [EVENT]     [END   2016/02/24 00:36:41] Checking status of the ADZDPATCH concurrent program

                    [EVENT]     [START 2016/02/24 00:36:41] Waiting for ADZDPATCH concurrent program to run

                    [EVENT]     [END   2016/02/24 00:37:12] Waiting for ADZDPATCH concurrent program to run

                  [EVENT]     [END   2016/02/24 00:37:12] Run the ADZDPATCH concurrent program

                  [EVENT]     [START 2016/02/24 00:37:12] Generating ad_zd_logs before truncating

                      [EVENT]     Report: /u02/appprd/PRD/fs2/EBSapps/appl/ad/12.0.0/sql/ADZDSHOWLOG.sql

                      [EVENT]     Output: /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/adzdshowlog_cleanup.out

                  [EVENT]     [END   2016/02/24 00:37:13] Generating ad_zd_logs before truncating

                  [EVENT]     [START 2016/02/24 00:37:13] Check and create Patch Edition (if required)

                    [EVENT]     [START 2016/02/24 00:37:13] Checking if Patch Edition already exists

                    [EVENT]     [END   2016/02/24 00:37:13] Check and create Patch Edition (if required)

                    [EVENT]     [START 2016/02/24 00:37:13] Performing steps to synchronise the FS

                        [EVENT]     [START 2016/02/24 00:37:14] Sync FS of RUN and PATCH

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

            Program :  started @ Wed Feb 24 00:37:14 2016

            *** Log File = /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/TXK_SYNC_update_Wed_Feb_24_00_37_14_2016/txkADOPPreparePhaseSynchronize_Wed_Feb_24_00_37_14_2016.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.

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

            SUMMARY OF PATCHES BEING SYNCHRONIZED...

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

            [1] SINGLE PATCH (DRV=u21027021.drv):  21027021

            [2] ADADMIN action :  RELINK

            [3] ADADMIN action :  RELINK

            SYNCHRONIZATION is in progress. This may take a little longer depending on the number and size of patches that are being synchronized.

            Check log file /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/TXK_SYNC_update_Wed_Feb_24_00_37_14_2016/txkADOPPreparePhaseSynchronize_Wed_Feb_24_00_37_14_2016.log for details.

            Oracle E-Business Suite Online Patching

            PATCH edition environment variables have been set.

            LOGPATH is set to /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/TXK_SYNC_update_Wed_Feb_24_00_37_14_2016/log

            AutoPatch error:

            AutoPatch stores backup files under your patch directory.

              Because of this, your patch directory must be writable.

              Please change permissions on your patch directory so that it can be

              written by the user currently running AutoPatch.

            You should check the file

            /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/TXK_SYNC_update_Wed_Feb_24_00_37_14_2016/log/u_21027021.log

            for errors.

             

            Oracle E-Business Suite Online Patching

            RUN edition environment variables have been set.

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

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

            TIME    : Wed Feb 24 00:37:40 2016

            FUNCTION: main::execADPATCH [ Level 1 ]

            ERRORMSG: Application of patch did not go through successfully.

                          [UNEXPECTED]Error occurred while executing "perl /u02/appprd/PRD/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/u02/appprd/PRD/fs2/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml -patchcontextfile=/u02/appprd/PRD/fs1/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml -promptmsg=hide -console=off -patchtop=/u02/appprd/PRD/fs_ne/EBSapps/patch -mode=update -sessionid=29 -timestamp=20160224_003436 -workercount=4 -outdir=/u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12 -autoskip=No"

                          [UNEXPECTED]Error while runSyncFS sub-routine is called

                            [EVENT]     [START 2016/02/24 00:37:40] 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/appprd/PRD/fs1/inst/apps/PRD_fitr12/logs/appl/admin/log/adadminsrvctl.txt for more information ... 

                            [EVENT]     [END   2016/02/24 00:37:46] Check and Stop Patch FS Admin Server

                            [EVENT]     [START 2016/02/24 00:37:46] 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/appprd/PRD/fs1/inst/apps/PRD_fitr12/logs/appl/admin/log/adnodemgrctl.txt for more information ... 

                            [EVENT]     [END   2016/02/24 00:37:52] Check and Stop Patch Node Manager

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

                          Log file: /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/adop_20160224_003436.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)

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

             

             

            $ adopscanlog -latest=yes

            Scanning /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/ directory ...

            /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/adop_20160224_003436.log:

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

            Lines #(187-191):

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

                          [STATEMENT] Output directory: /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12

                          [UNEXPECTED]Error occurred while executing "perl /u02/appprd/PRD/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/u02/appprd/PRD/fs2/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml -patchcontextfile=/u02/appprd/PRD/fs1/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml -promptmsg=hide -console=off -patchtop=/u02/appprd/PRD/fs_ne/EBSapps/patch -mode=update -sessionid=29 -timestamp=20160224_003436 -workercount=4 -outdir=/u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12 -autoskip=No"

                          [UNEXPECTED]Error while runSyncFS sub-routine is called

                          [PROCEDURE] [START 2016/02/24 00:37:40] Check and Stop Patch Admin Server

            Lines #(188-192):

                          [STATEMENT] Output directory: /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12

                          [UNEXPECTED]Error occurred while executing "perl /u02/appprd/PRD/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/u02/appprd/PRD/fs2/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml -patchcontextfile=/u02/appprd/PRD/fs1/inst/apps/PRD_fitr12/appl/admin/PRD_fitr12.xml -promptmsg=hide -console=off -patchtop=/u02/appprd/PRD/fs_ne/EBSapps/patch -mode=update -sessionid=29 -timestamp=20160224_003436 -workercount=4 -outdir=/u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12 -autoskip=No"

                          [UNEXPECTED]Error while runSyncFS sub-routine is called

                          [PROCEDURE] [START 2016/02/24 00:37:40] Check and Stop Patch Admin Server

                            [EVENT]     [START 2016/02/24 00:37:40] Check and Stop Patch FS Admin Server

            Lines #(198-202):

                            [EVENT]     [END   2016/02/24 00:37:52] Check and Stop Patch Node Manager

                          [PROCEDURE] [END   2016/02/24 00:37:52] 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/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/TXK_SYNC_update_Wed_Feb_24_00_37_14_2016/log/u_21027021.log:

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

            Lines #(265-269):

            /u01/PATCH/21027021/test.txt

            AutoPatch error:

            AutoPatch stores backup files under your patch directory.

              Because of this, your patch directory must be writable.

            /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29/prepare_20160224_003436/PRD_fitr12/TXK_SYNC_update_Wed_Feb_24_00_37_14_2016/txkADOPPreparePhaseSynchronize_Wed_Feb_24_00_37_14_2016.log:

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

            Lines #(464-466):

            TIME    : Wed Feb 24 00:37:40 2016

            FUNCTION: main::execADPATCH [ Level 1 ]

            ERRORMSG: Application of patch did not go through successfully.

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

            cat /u02/appprd/PRD/fs_ne/EBSapps/log/status_20160224_004140/adzdshowstatus.out

            Current Patching Session ID: 29

            Node Name       Node Type       Phase           Status          Started                        Finished                       Elapsed

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

            fitr12          master          PREPARE         FAILED          23-FEB-16 04:43:00 +08:00      24-FEB-16 12:37:52 +08:00      7:54:52

                                            APPLY           NOT STARTED

                                            FINALIZE        NOT STARTED

                                            CUTOVER         NOT STARTED

                                            CLEANUP         NOT STARTED

             

            File System Synchronization Used in this Patching Cycle: Light

             

            File System Information:

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

            File System: SINGLE NODE INSTANCE

             

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

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

            fitr12      master      /u02/appprd/PRD/fs2            /u02/appprd/PRD/fs1            /u02/appprd/PRD/fs_ne          /u02/appprd/PRD/fs2/inst/apps/

                                                                                                                                 PRD_fitr12

             

            Custom File System Synchronization script: /u02/appprd/PRD/fs_ne/EBSapps/appl/ad/custom/adop_sync.drv

            Patch Stage Top: /u02/appprd/PRD/fs_ne/EBSapps/patch

            Online Patching Log base: /u02/appprd/PRD/fs_ne/EBSapps/log/adop/29

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

            =             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    Elapsed(Prepare) Elapsed(Cutover) Elapsed(Cleanup) Elapsed(Apply)  Status       Patches Applied      Session Type

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

                    29 fitr12     master    23-FEB-16  7:54:52          0:00:00          0:00:00          0:00:00         FAILED       --                   --

             

             

                    28 fitr12     master    17-FEB-16  0:24:08          0:16:24          0:12:58          0:20:34         COMPLETE     CONFIG_CLONE         CONFIG_CLONE

                                  master                                                                  0:21:43         COMPLETE     21027021             ONLINE

                                  master               0:00:00          0:00:00          0:00:00          0:00:00         COMPLETE     CONFIG_CLONE         CONFIG_CLONE

             

             

                    27 fitr12     master    07-FEB-16  0:10:26          0:13:26          0:11:56          0:00:00         COMPLETE     --                   --

             

             

                    26 fitr12     master    07-FEB-16  1:08:35          0:11:46          0:19:45          0:19:27         COMPLETE     21343684             ONLINE

                                  master                                                                  1:05:15         COMPLETE     CONFIG_CLONE         CONFIG_CLONE

                                  master               0:00:00          0:00:00          0:00:00          0:00:00         COMPLETE     CONFIG_CLONE         CONFIG_CLONE

             

             

                    25 fitr12     master    28-JAN-16  0:00:00          0:00:00          0:00:39          0:01:48         COMPLETE     18955265             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     --                   --

            • 3. Re: Patching new instance
              Narsi M-Oracle

              Hello Jenna,

               

              I don't think issue is due to hotpatch.

              Because, it is trying to remove:

              /u01/PATCH/21027021/backup/PRD/fitr12/pa/patch/115/sql/PAXFBPVDS.pls

              From Patch 21027021 -- This patch was applied in a regular adop cycle as per your output details.

              Can you check if those files exist ?


              Regards,

              Narsi

              1 person found this helpful
              • 4. Re: Patching new instance
                Beauty_and_dBest

                Yes it exist in my central patch directory.

                 

                [ec2-user@fitr12 ~]$ sudo su - root

                [root@fitr12 ~]# ls -l /u01/PATCH/21027021/backup/PRD/fitr12/pa/patch/115/sql/PAXFBPVDS.pls

                -rw-r--r--. 1 appvis dba 1459 Feb 17 11:18 /u01/PATCH/21027021/backup/PRD/fitr12/pa/patch/115/sql/PAXFBPVDS.pls

                 

                Why is the patch removing the source file? I can not able to remove since I already changed its permission.

                This is my repository directory, right now I changed the ownership to appvis since I am also apply this patch to this instance.

                The adop prepare I am running is for "appprd" instance.

                 

                But why is that when a run adop prepare again, it displayed new error? and the deleling of files is gone?

                • 5. Re: Patching new instance
                  Narsi M-Oracle

                  Hello Jenna,

                   

                  Can you try to give 777 permissions recursively  to the "u01/PATCH/21027021/backup/" and check if it helps.

                  This should not affect any of your instances as it is only deleting files from your backup folder.

                   

                  Regards,

                  Narsi

                  1 person found this helpful
                  • 6. Re: Patching new instance
                    Beauty_and_dBest

                    Thanks ALL,

                     

                    It went ok when I change permission the directory.

                    My question is why is it still performing cleanup on adop prepare phase? When I already done adop cleanup phase?

                    Why is it accessing the old patch directory?

                    What if I clone it to another server and the patch directory has new name?

                    How can I completely run a new patching cycle so that it is free from cleaning up previous patches?

                    Do I need to run adop prepare phase as my last steps, then abort it? then clone it and transfer to another server?

                     

                    Kind regards,