• 15. Re: R12.2 Patching- adop CLONE phase is struck
      Magnanimous

      After setting up the JVM can you paste the output ?

       

      echo $CONFIG_JVM_ARGS

      • 16. Re: R12.2 Patching- adop CLONE phase is struck
        3592655

        Magnanimous

        No, this is not a new server. this clone is part of the patching process.

        The patch we applied is #31044218.

         

        Thank you.

        • 17. Re: R12.2 Patching- adop CLONE phase is struck
          Magnanimous

          Hello Rajesh,

          I had an same issue back in 2015, when i checked my notes and i applied the following MOS -

          ADOP Fails with OutOfMemoryError: Java Heap Space Error (Doc ID 1679761.1)

           

           

           

          You might already have opened the SR if not please do asap.

           

          Prashant Umap

          • 18. Re: R12.2 Patching- adop CLONE phase is struck
            Magnanimous

            Send me all logs from the clone directory.

             

            Prashant

            • 19. Re: R12.2 Patching- adop CLONE phase is struck
              3592655

              Logs from the Clone directory: https://outgoing.more4apps.com/temporary/clone.zip

               

              Thank you.

              • 20. Re: R12.2 Patching- adop CLONE phase is struck
                Magnanimous

                What the mount point free size on clone node ?

                • 21. Re: R12.2 Patching- adop CLONE phase is struck
                  3592655

                  Magnanimous Yes verified we do have enough space in all the filesystem.

                   

                  Thank you.

                  • 22. Re: R12.2 Patching- adop CLONE phase is struck
                    Magnanimous

                    Ok thanks for the update. As it looks like vision instance you might not have the SR created?

                    Prashant Umap

                    • 23. Re: R12.2 Patching- adop CLONE phase is struck
                      3592655

                      Magnanimous : Yes that's right.

                      • 24. Re: R12.2 Patching- adop CLONE phase is struck
                        Magnanimous

                        Can you paste the following query output?

                        show parameter parallel_max_servers;

                        If its more, try to give less workers and retry adop.

                        • 25. Re: R12.2 Patching- adop CLONE phase is struck
                          Magnanimous

                          Also one more thing by checking all the attached logs not able to find on what level its failing. Do you know what level ?

                          Is it at - OHS Level ? If yes please do let me know.

                          We might need to update the conf files?

                          • 26. Re: R12.2 Patching- adop CLONE phase is struck
                            3592655

                            Magnanimous

                            SQL> show parameter parallel_max_servers;

                            NAME                                 TYPE        VALUE

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

                            parallel_max_servers                 integer     8

                            • 27. Re: R12.2 Patching- adop CLONE phase is struck
                              3592655

                              Magnanimous

                              Below is the log information when i force the adop clone to fail

                               

                              ============================ LOG  ============================

                              run> adopscanlog -latest=yes

                               

                               

                              Scanning /oramid/VIS9/fs_ne/EBSapps/log/adop/135/ directory ...

                               

                               

                              /oramid/VIS9/fs_ne/EBSapps/log/adop/135/20200702_092135/fs_clone/<instance>/TXK_SYNC_create/txkADOPPreparePhaseSynchronize.log:

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

                               

                               

                              Lines #(414-416):

                              TIME    : Mon Jul  6 09:17:17 2020

                              FUNCTION: main::runFSCloneApply [ Level 1 ]

                              ERRORMSG: /oramid/VIS9/fs1/EBSapps/comn/adopclone_<instance>/bin/adclone.pl did not go through successfully.

                               

                               

                              /oramid/VIS9/fs_ne/EBSapps/log/adop/135/20200702_092135/adop.log:

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

                               

                               

                              Lines #(143-148):

                                  [PROCEDURE] Calling: /oramid/VIS9/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl

                                  [EVENT]     Log: /oramid/VIS9/fs_ne/EBSapps/log/adop/135/20200702_092135/fs_clone/<instance>

                                  [UNEXPECTED]Error occurred running "perl /oramid/VIS9/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/oramid/VIS9/fs1/inst/apps/VIS9_<instance>/appl/admin/VIS9_<instance>.xml -patchcontextfile=/oramid/VIS9/fs2/inst/apps/VIS9_<instance>/appl/admin/VIS9_<instance>.xml -promptmsg=hide -console=off -mode=create -sync_mode=copy -sessionid=135 -timestamp=20200702_092135 -outdir=/oramid/VIS9/fs_ne/EBSapps/log/adop/135/20200702_092135/fs_clone/<instance>"

                                  [UNEXPECTED]occurred during CLONE Patch File System from Run File System, running command: "perl /oramid/VIS9/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/oramid/VIS9/fs1/inst/apps/VIS9_<instance>/appl/admin/VIS9_<instance>.xml -patchcontextfile=/oramid/VIS9/fs2/inst/apps/VIS9_<instance>/appl/admin/VIS9_<instance>.xml -promptmsg=hide -console=off -mode=create -sync_mode=copy -sessionid=135 -timestamp=20200702_092135 -outdir=/oramid/VIS9/fs_ne/EBSapps/log/adop/135/20200702_092135/fs_clone/<instance>".

                                  [EVENT]     Releasing managed server ports.

                                      [PROCEDURE] [START 2020/07/06 09:17:17] Releasing ports

                               

                               

                              Lines #(164-169):

                                          [PROCEDURE] [START 2020/07/06 09:17:19] Check and stop patch Admin Server

                                          [PROCEDURE] [START 2020/07/06 09:17:20] Check and Stop patch FS Admin Server

                                          [UNEXPECTED]Error occurred running "sh /oramid/VIS9/fs2/inst/apps/VIS9_<instance>/admin/scripts/adadminsrvctl.sh  stop -nopromptmsg"

                                          [UNEXPECTED]Error running adadminsrvctl command

                                      [PROCEDURE] [START 2020/07/06 09:17:20] Unlocking sessions table

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

                               

                              Thank you.

                              • 28. Re: R12.2 Patching- adop CLONE phase is struck
                                Magnanimous

                                Please try the following -

                                Solution 1 -

                                1. Shutdown application on all the node.
                                2. Kill if any process running
                                3. Startup the application – stop the internal manager
                                4. All managers will be in Actual and Target shld be 0
                                5. Again shutdown the application on all the node.
                                6. Startup the application.
                                7. Please see if any Patching Application req in running status if any cancel that.
                                8. And run prepare again.

                                Solution 2

                                phase=abort

                                phase=cleanup cleanup_mode=full

                                phase=fs_clone

                                If still abort phase is failing, please check all the locks and kill if any.

                                 

                                Please check and revert back.

                                • 29. Re: R12.2 Patching- adop CLONE phase is struck
                                  3592655

                                  Magnanimous : Sure will check and let you know.

                                   

                                  Thank you.

                                  1 2 上一个 下一个