1 2 Previous Next 18 Replies Latest reply on May 29, 2017 1:47 AM by #MVivek

    error while applying adop patch

    #MVivek

      Here, is the log given below -

       

      bash-3.2$ adop phase=prepare

       

       

      Enter the APPS password:

      Enter the SYSTEM password:

      Enter the WLSADMIN password:

       

       

      Validating credentials...

       

       

      Initializing...

          Run Edition context  : /orabin/oracle/UAT9/fs1/inst/apps/UAT9_egluatfidb02/appl/admin/UAT9_egluatfidb02.xml

          Patch edition context: /orabin/oracle/UAT9/fs2/inst/apps/UAT9_egluatfidb02/appl/admin/UAT9_egluatfidb02.xml

          Patch file system freespace: 94.70 GB

       

       

      Validating system setup...

          Node registry is valid.

      Logfile location /orabin/oracle/UAT9/fs1/inst/apps/UAT9_egluatfidb02/logs/appl/rgf/TXK/verifyssh.log

      xml output = /orabin/oracle/UAT9/fs1/inst/apps/UAT9_egluatfidb02/logs/appl/rgf/TXK/out.xml

          ssh is not enabled for the following nodes

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

          egluatweb

          [UNEXPECTED]ssh is not enabled.

          [UNEXPECTED]Hint: These are some available options:

          [UNEXPECTED]- If you would like to enable ssh, execute the following command:

           perl /orabin/oracle/UAT9/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkRunSSHSetup.pl enablessh \

                -contextfile=/orabin/oracle/UAT9/fs1/inst/apps/UAT9_egluatfidb02/appl/admin/UAT9_egluatfidb02.xml \

                -hosts=egluatfidb02,egluatweb

        Then, try the adop command again.

          [UNEXPECTED]- Otherwise, with ssh disabled you would need to execute adop on each node separately:

           adop phase=<desired phase> allnodes=no action=db     // on admin node

           adop phase=<desired phase> allndoes=no action=nodb   // on non-admin nodes

          [UNEXPECTED]Error while verifying ssh for all nodes.

       

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

        • 1. Re: error while applying adop patch
          #MVivek

          bash-3.2$ adop -status

           

          Enter the APPS password:

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

          ADOP (C.Delta.6)

          Session Id: 51

          Command: status

          Output: /orabin/oracle/UAT9/fs_ne/EBSapps/log/status_20170429_180344/adzdshowstatus.out

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

           

          Node Name       Node Type  Phase           Status          Started              Finished             Elapsed

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

          egluatfidb02    master     FS_CLONE        COMPLETED       2017/02/22 12:44:45  2017/02/22 03:53:18  3:08:33

           

          egluatweb       slave      FS_CLONE        COMPLETED       2017/02/22 12:44:46  2017/02/22 08:53:40  8:08:54

           

          File System Synchronization Type: Full

           

          adop exiting with status = 0 (Success)

          bash-3.2$

          • 2. Re: error while applying adop patch
            mdtaylor

            Are you using shared appl_top or separate installations?  Have you always had ssh disabled?

            • 3. Re: error while applying adop patch
              #MVivek

              Micheal,

               

              Actually, EBS was running in two server before. But one server (web server) is crashed. So, now EBS is running in one server only.

               

              Web server is not exists now.

               

              Thanks

              Vivek

              • 4. Re: error while applying adop patch
                mdtaylor

                Hi Vivek,

                 

                Please review the Deleting an Application Tier Node section of the Cloning 12.2 document, especially Case 2.

                 

                Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)

                 

                Regards,

                Michael

                1 person found this helpful
                • 5. Re: error while applying adop patch
                  #MVivek

                  Still Getting error.

                  • 6. Re: error while applying adop patch
                    mdtaylor

                    Hi Vivek,

                     

                    Do you still see the crashed node in fnd_nodes and ad_appl_tops?  You may need to shutdown the applications, execute fnd_conc_clone.setup_clean as apps which will wipe out all node and tns information, then execute autoconfig on the dbTier, patch appTier, then run appTier.  Then restart the applications and adop should be successful.

                     

                    Regards,

                    Michael

                    • 7. Re: error while applying adop patch
                      #MVivek

                      Michael,

                       

                      Now getting different error.

                       

                      Error:

                      +++++++++++++++++++++++++
                      configProperty id = Server6
                      Count for NodeIterator nextNode = 3
                      ERROR: Managed Server's are not in sync between file system context and DB context
                      ERROR: Update Moveplan Fail

                       

                      START: Inside exitClone....
                      Updating status INCOMPLETE for ApplywlsTechStack

                       

                      START: Updating status INCOMPLETE for action ApplywlsTechStack

                       

                      END: Updated status INCOMPLETE for action ApplywlsTechStack

                       

                      Thanks

                      Vivek

                      • 8. Re: error while applying adop patch
                        #MVivek

                        bash-3.2$ adopscanlog -latest=yes

                         

                         

                        Scanning /orabin/oracle/UAT9/fs_ne/EBSapps/log/adop/57/ directory ...

                         

                         

                        /orabin/oracle/UAT9/fs_ne/EBSapps/log/adop/57/adop_20170501_034652.log:

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

                         

                         

                        Lines #(100-104):

                            [PROCEDURE] Calling: /orabin/oracle/UAT9/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl

                            [EVENT]     Log: /orabin/oracle/UAT9/fs_ne/EBSapps/log/adop/57/fs_clone_20170501_034652/UAT9_egluatfidb02

                            [UNEXPECTED]Error occurred while executing "perl /orabin/oracle/UAT9/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/orabin/oracle/UAT9/fs1/inst/apps/UAT9_egluatfidb02/appl/admin/UAT9_egluatfidb02.xml -patchcontextfile=/orabin/oracle/UAT9/fs2/inst/apps/UAT9_egluatfidb02/appl/admin/UAT9_egluatfidb02.xml -promptmsg=hide -console=off -mode=create -sessionid=57 -timestamp=20170501_034652 -outdir=/orabin/oracle/UAT9/fs_ne/EBSapps/log/adop/57/fs_clone_20170501_034652/UAT9_egluatfidb02"

                            [UNEXPECTED]Error occurred while CLONE Patch File System from Run File System using command: "perl /orabin/oracle/UAT9/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/orabin/oracle/UAT9/fs1/inst/apps/UAT9_egluatfidb02/appl/admin/UAT9_egluatfidb02.xml -patchcontextfile=/orabin/oracle/UAT9/fs2/inst/apps/UAT9_egluatfidb02/appl/admin/UAT9_egluatfidb02.xml -promptmsg=hide -console=off -mode=create -sessionid=57 -timestamp=20170501_034652 -outdir=/orabin/oracle/UAT9/fs_ne/EBSapps/log/adop/57/fs_clone_20170501_034652/UAT9_egluatfidb02".

                            [EVENT]     Releasing the managed servers ports...

                         

                         

                        Lines #(101-105):

                            [EVENT]     Log: /orabin/oracle/UAT9/fs_ne/EBSapps/log/adop/57/fs_clone_20170501_034652/UAT9_egluatfidb02

                            [UNEXPECTED]Error occurred while executing "perl /orabin/oracle/UAT9/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/orabin/oracle/UAT9/fs1/inst/apps/UAT9_egluatfidb02/appl/admin/UAT9_egluatfidb02.xml -patchcontextfile=/orabin/oracle/UAT9/fs2/inst/apps/UAT9_egluatfidb02/appl/admin/UAT9_egluatfidb02.xml -promptmsg=hide -console=off -mode=create -sessionid=57 -timestamp=20170501_034652 -outdir=/orabin/oracle/UAT9/fs_ne/EBSapps/log/adop/57/fs_clone_20170501_034652/UAT9_egluatfidb02"

                            [UNEXPECTED]Error occurred while CLONE Patch File System from Run File System using command: "perl /orabin/oracle/UAT9/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/orabin/oracle/UAT9/fs1/inst/apps/UAT9_egluatfidb02/appl/admin/UAT9_egluatfidb02.xml -patchcontextfile=/orabin/oracle/UAT9/fs2/inst/apps/UAT9_egluatfidb02/appl/admin/UAT9_egluatfidb02.xml -promptmsg=hide -console=off -mode=create -sessionid=57 -timestamp=20170501_034652 -outdir=/orabin/oracle/UAT9/fs_ne/EBSapps/log/adop/57/fs_clone_20170501_034652/UAT9_egluatfidb02".

                            [EVENT]     Releasing the managed servers ports...

                                [PROCEDURE] [START 2017/05/01 04:50:15] Releasing the ports

                         

                         

                        Lines #(128-132):

                                    [PROCEDURE] [END   2017/05/01 04:51:10] Check and Stop patch Node Manager

                                    [PROCEDURE] [END   2017/05/01 04:51:10] Check and Stop patch Node Manager

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

                            [PROCEDURE] [START 2017/05/01 04:51:11] Unlocking sessions table

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

                         

                         

                        /orabin/oracle/UAT9/fs_ne/EBSapps/log/adop/57/fs_clone_20170501_034652/UAT9_egluatfidb02/TXK_SYNC_create/fsclone_stage/FSCloneStageAppsTier_05010356.log:

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

                         

                         

                        Lines #(23-27):

                         

                         

                        patchMSList size: 5

                        ERROR: Number of servers are not in sync between Run and Patch Context.

                        ERROR: Managed Servers would be in-sync at apply phase

                         

                         

                         

                         

                        Lines #(24-28):

                        patchMSList size: 5

                        ERROR: Number of servers are not in sync between Run and Patch Context.

                        ERROR: Managed Servers would be in-sync at apply phase

                         

                         

                         

                         

                         

                         

                        /orabin/oracle/UAT9/fs_ne/EBSapps/log/adop/57/fs_clone_20170501_034652/UAT9_egluatfidb02/TXK_SYNC_create/txkADOPPreparePhaseSynchronize.log:

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

                         

                         

                        Lines #(478-480):

                        TIME    : Mon May  1 04:50:15 2017

                        FUNCTION: main::runFSCloneApply [ Level 1 ]

                        ERRORMSG: /orabin/oracle/UAT9/fs1/EBSapps/comn/adopclone_egluatfidb02/bin/adclone.pl did not go through successfully.

                         

                         

                        /orabin/oracle/UAT9/fs_ne/EBSapps/log/adop/57/fs_clone_20170501_034652/UAT9_egluatfidb02/TXK_SYNC_create/fsclone_apply/FSCloneApplyAppsTier_05010430.log:

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

                         

                         

                        Lines #(4476-4480):

                        configProperty id = Server6

                        Count for NodeIterator nextNode = 3

                        ERROR: Managed Server's are not in sync between file system context and DB context

                        ERROR: Update Moveplan Fail

                         

                         

                         

                         

                        Lines #(4477-4481):

                        Count for NodeIterator nextNode = 3

                        ERROR: Managed Server's are not in sync between file system context and DB context

                        ERROR: Update Moveplan Fail

                         

                         

                        START: Inside exitClone....

                        bash-3.2$

                        bash-3.2$

                        1 person found this helpful
                        • 9. Re: error while applying adop patch
                          #MVivek

                          Raised SR as well.

                           

                          Thanks

                          Vivek

                          • 10. Re: error while applying adop patch
                            mdtaylor

                            You may have to remove the patch fs and clone it again. They also may have you abandon this adop session and start a new one since you are stuck in prepare phase anyway.

                            • 11. Re: error while applying adop patch
                              #MVivek

                              Hi Michael,

                               

                              Thanks for you support and all effort.

                              Waiting for Oracle Support, update..

                               

                              Once resolved or any update got from Oracle support, let you know.

                               

                              Thanks

                              Vivek

                              • 12. Re: error while applying adop patch
                                #MVivek

                                Hi mdtaylor

                                Your Suggestion:

                                 

                                You may have to remove the patch fs and clone it again. They also may have you abandon this adop session and start a new one since you are stuck in prepare phase anyway.

                                 

                                 

                                Can you please provide steps, it will be very helpful.

                                 

                                 

                                Thanks

                                Vivek

                                • 13. Re: error while applying adop patch
                                  mdtaylor

                                  Vivek,

                                   

                                  First recommendation is to abort the adop session which is stuck trying to ssh to a dead node.

                                   

                                  adop --help

                                  Applications DBA Online Patching Tool (adop)

                                   

                                  Usage: adop [phase=<phase,phase,...>] [patches=<patch#,patch#,...>]

                                              [<parameter>=<value> ...] [input_file=<filename>]

                                         adop -help

                                         adop -examples

                                         adop -status [<session_id>]

                                         adop -validate

                                   

                                  See Oracle E-Business Suite Maintenance Guide for a full description of

                                  adop features, operation, and usage.

                                   

                                  The phase parameter specifies the parts (phases) of the online

                                  patching cycle to be executed. The five standard phases are executed

                                  in the order shown below.

                                   

                                  Standard phases:

                                    prepare       - Prepare the instance for patch application.

                                    apply         - Apply patches (to the patch edition).

                                    finalize      - Ready the instance for cutover.

                                    cutover       - Make the patch edition the new run edition.

                                    cleanup       - Drop obsolete objects and data from old editions.

                                   

                                  There are also three special phases, for use when needed.

                                   

                                  Special phases:

                                    abort         - Abort the current online patching cycle.

                                    actualize_all - Create actual copies of all code objects in the patch

                                                    edition.

                                    fs_clone      - Copy the run file system to the patch file system.

                                   

                                  So run adop phase=abort, cleanup cleanup_mode=full

                                   

                                  https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm

                                   

                                  Aborting an Online Patching Cycle

                                  If a patching cycle is failing and the issue cannot be resolved quickly, it is possible to abort the patching cycle and return to normal runtime operation. The patch edition will be dropped.

                                  You can abandon a patching cycle (without applying any patches) by running the command:

                                  $ adop phase=abort

                                  Tip: This abort command can only be used before successful completion of the cutover phase. After cutover, the system is running on the new edition, and abort is no longer possible for that patching cycle.

                                  Aborting a patching cycle will drop the patch edition, but you must then run the cleanup and fs_clone phases before starting a new patching cycle. The cleanup must be a full cleanup.

                                  For example:

                                  $ adop phase=prepare $ adop phase=apply patches=123456 [Patch application encounters problems and you want to abort] $ adop phase=abort $ adop phase=cleanup cleanup_mode=full $ adop phase=fs_clone

                                  Optionally, you can combine the abort and cleanup commands as follows:

                                  $ $ adop phase=abort,cleanup cleanup_mode=full

                                  Note: You cannot abort application of a patch applied in hotpatch mode or downtime mode.

                                   

                                  Then try to run adop again.

                                  1 person found this helpful
                                  • 14. Re: error while applying adop patch
                                    #MVivek

                                    Hi mdtaylor,

                                     

                                    I have performed earlier.

                                     

                                    I have tried it by following below steps -

                                     

                                    1. No services or processes are running from the PATCH file system

                                     

                                     

                                    2. Ensured the Weblogic Admin Server and Node Manager are running on the Run File system. You can run the following commands to check the status:

                                    $ adadminsrvctl.sh status

                                    $ adnodemgrctl.sh status

                                     

                                    3. Cleanup

                                    $ adop phase=cleanup cleanup_mode=full

                                     

                                    4. fs_clone

                                    $ adop phase=fs_clone force=yes

                                     

                                    But result is same as, failed.

                                     

                                    N.B.

                                    My ID is locked.. Unable to provide logs. I will provide you all logs, once my account is unlocked.

                                     

                                    Thanks

                                    Vivek

                                    1 2 Previous Next