1 2 3 Previous Next 30 Replies Latest reply on Oct 8, 2019 5:38 PM by Prashant Umap

    ADOP Cut-over error - EBS R12.2.5

    Beauty_and_dBest

      EBS R12.2.5

      12c

      OL6

       

      Hi ALL,

       

      I am currently applying patch  p26834480_R12.AD.C_R12_LINUX

      I am already on "cutover phase", but I got error below:

       

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

      ADOP (C.Delta.11)

      Session ID: 7

      Node: prodsrvr

      Phase: cutover

      Log: /u01/apptest3/TEST3/fs_ne/EBSapps/log/adop/7/20190926_143829/adop.log

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

       

       

      Validating configuration on node: [prodsrvr].

          Log: /u01/apptest3/TEST3/fs_ne/EBSapps/log/adop/7/20190926_143829/cutover/validate/prodsrvr

      [ERROR]: AD and TXK code levels are NOT in sync.

          [UNEXPECTED]Error occurred running "perl /u01/apptest3/TEST3/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl  -contextfile=/u01/apptest3/TEST3/fs1/inst/apps/TEST3_prodsrvr/appl/admin/TEST3_prodsrvr.xml -patchctxfile=/u01/apptest3/TEST3/fs2/inst/apps/TEST3_prodsrvr/appl/admin/TEST3_prodsrvr.xml -phase=cutover -logloc=/u01/apptest3/TEST3/fs_ne/EBSapps/log/adop/7/20190926_143829/cutover/validate/prodsrvr -promptmsg=hide"

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

       

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

       

       

       

      Please help how to toubleshoot this error.

       

       

      Kind regards,

      jc

        • 1. Re: ADOP Cut-over error - EBS R12.2.5
          mdtaylor

          Hi jc,

           

          Please review the following note:

           

          Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)

           

          It appears AD.C and TXK.C are not at the same Delta levels.  If you are on AD.C.Delta.11, then you must also apply TXK.C.Delta.11 in the same patching cycle.

           

          You may have to abort the adop session and correct this in a new adop session.

           

          Regards,

          Michael

          • 2. Re: ADOP Cut-over error - EBS R12.2.5
            Beauty_and_dBest

            Thanks Michael,

             

            But the note said p26834480_R12.AD.C_R12_LINUX  is a pre-requisite to  TXK.C.Delta.11 

             

            I really do not underatend these AD and TXK patches.

             

            Please help how to apply these two.

             

             

            Kind regards,

            • 3. Re: ADOP Cut-over error - EBS R12.2.5
              Mohammed Ali A. Syed

              Hi,

              Before running cutover phase you need to apply patches 28840822 and 19259764

               

              Thanks

              • 4. Re: ADOP Cut-over error - EBS R12.2.5
                Beauty_and_dBest

                Hi EBSdba,

                 

                How can that be possible? i will apply  a new patching cycle in the middle of a pending hanging AD patch?

                 

                 

                Kind regards,

                • 5. Re: ADOP Cut-over error - EBS R12.2.5
                  Maaz Khan

                  Hi Jc,

                   

                  Step -1

                   

                  We need to check you current AD and TXK code level first -

                  col ABBREVIATION for a10

                  set lines 1000

                  col NAME for a50

                  col CODELEVEL for a20

                  SELECT ABBREVIATION,NAME,codelevel FROM AD_TRACKABLE_ENTITIES WHERE abbreviation in ('txk','ad');

                   

                  Let us know your current code level. You should carefully follow Path B - 3.2 Path B — Existing Release 12.2 customers (below AD-TXK Delta 11 codelevel)  - Doc ID 1617461.1

                   

                  Step- 2

                  Let us know your current status of patching cycle -

                  adop -status

                   

                  Step -3

                  Apply all recommended patches as per etcc -

                  Patch 17537119: EBS Technology Codelevel Checker

                  checkMTpatch.sh on appstier nodes

                  checkDBpatch.sh on dbtier nodes

                   

                   

                  Regards,

                  Maaz

                  • 6. Re: ADOP Cut-over error - EBS R12.2.5
                    Mohammed Ali A. Syed

                    Yes, in one patching cycle you can apply any number of patches.

                     

                    1. Prepare

                    2. Apply pahase -> apply any number of patches

                    3. finalize

                    4. cutover

                    5. cleanup

                    • 7. Re: ADOP Cut-over error - EBS R12.2.5
                      lmu

                      if you run finalize , then realize you have more patches to apply, you can apply them, then run finalize again.

                      • 8. Re: ADOP Cut-over error - EBS R12.2.5
                        Beauty_and_dBest

                        Thanks ALL,

                         

                        Yes, I know that in one patching cycle, I can apply many patches. But not in the middle of a current hanging/pending error patch.

                         

                        I will check first what Maaz have given, detailed process.

                         

                        col ABBREVIATION for a10

                        set lines 1000

                        col NAME for a50

                        col CODELEVEL for a20

                         

                        SELECT ABBREVIATION,NAME,codelevel FROM AD_TRACKABLE_ENTITIES WHERE abbreviation in ('txk','ad');

                         

                        ABBREVIATI NAME                                               CODELEVEL

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

                        ad         Oracle Applications DBA                            C.11

                        txk        Oracle Applications Technology Stack               C.8

                         

                        SQL>

                         

                        [apptest3@prodsrvr ~]$ adop -status

                         

                        Enter the APPS password:

                        Connected.

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

                        ADOP (C.Delta.11)

                        Session Id: 7

                        Command: status

                        Output: /u01/apptest3/TEST3/fs_ne/EBSapps/log/adop/7/20190930_144547/adzdshowstatus.out

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

                        Node Name       Node Type  Phase           Status          Started              Finished             Elapsed

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

                        prodsrvr          master     PREPARE         COMPLETED       2019/09/26 11:49:02  2019/09/26 12:05:51  0:16:49

                                                   APPLY           ACTIVE          2019/09/26 13:33:21  2019/09/26 14:18:11  0:44:50

                                                   FINALIZE        COMPLETED       2019/09/26 14:24:06  2019/09/26 14:25:53  0:01:47

                                                   CUTOVER         NOT STARTED

                                                   CLEANUP         NOT STARTED

                         

                        File System Synchronization Type: None

                         

                        adop exiting with status = 0 (Success)

                         

                         

                        Please help what to do next.

                        I can see above that the patch take effect since the version of AD is now 11?

                        ad         Oracle Applications DBA                            C.11

                         

                         

                         

                        Kind regards,

                        • 9. Re: ADOP Cut-over error - EBS R12.2.5
                          Beauty_and_dBest

                          Hi ALL.

                           

                          I will try below :

                           

                          Before running cutover phase you need to apply patches 28840822 and 19259764

                           

                          So this means I will apply the three patches simultaneously? ad.c.11, 28840822, and 19259764.

                           

                          I already run cutover, but did not succeed, I am still allowed to apply the two patches above?

                           

                           

                          Kind regards,

                          • 10. Re: ADOP Cut-over error - EBS R12.2.5
                            Maaz Khan

                            Hi Jc,

                             

                            As per status, cutover has not been started yet, please apply remaining patches as well and then try to perform a cutover.

                            I normally take complete backup of both apps and db before RUP upgrades.

                             

                            Regards,

                            MAaz

                            • 11. Re: ADOP Cut-over error - EBS R12.2.5
                              Beauty_and_dBest

                              Thanks Maaz and ALL

                               

                              Yes I am applying first in TEST instance.

                               

                              Please confirm. I will apply the three patches p26834480_R12.AD.C_R12_LINUX28840822 and 19259764  in the same patching cycle?

                               

                              In which order do I apply them? Can I apply them in any order?

                               

                               

                               

                              Kind regards,

                              • 12. Re: ADOP Cut-over error - EBS R12.2.5
                                Maaz Khan

                                Hi Jc,

                                 

                                As per outputs you have shared earlier, I can see AD_11 patch -  is already applied. However, you missed to merge and apply additional critical patch - Patch 28280348:R12.AD.C

                                So please follow below approach and let us know-

                                1. Apply additional critical patch - Patch 28280348:R12.AD.C

                                adop phase=apply patches=28280348

                                2. Merge TXK_11(Patch 28840822  (R12.TXK.C.Delta.11)) with other critical TXK patches (Patch 29965377:R12.TXK.C

                                , Patch 29781255:R12.TXK.C)

                                adop phase=apply patches=28840822,29965377,29781255 merge=yes

                                3. Run the Middle Tier EBS Technology Codelevel Checker (MT-ETCC) on the patch file system.

                                4. If all goes well, complete patching cycle.

                                5. Follow remaining steps given in doc id.

                                 

                                 

                                Regards,

                                Maaz

                                • 13. Re: ADOP Cut-over error - EBS R12.2.5
                                  Beauty_and_dBest

                                  Thanks Maaz,

                                   

                                  For that very clear explanation

                                  You know my head aches everytime I read this AD/TXK support note, as is changes a lot of times.

                                  I got phobia when reading this note. I wonder why it is written in a very hard to understand style or manner?

                                  It seems the paragraph's indentation is not good?

                                  I wish you can re-write this notes in your own style in a blog?

                                   

                                  Hi Maaz and ALL,

                                   

                                  What about patches mentioned by EBSDBA? >  Before running cutover phase you need to apply patches 28840822 and 19259764

                                   

                                  Do I need 19259764?

                                   

                                   

                                  Kind regards,

                                  • 14. Re: ADOP Cut-over error - EBS R12.2.5
                                    Beauty_and_dBest

                                    Hi Maaz and ALL,

                                     

                                    I think cutover was partially done, because the listener is down?  but the adop -status did not update correctly

                                    Because when I apply the additional patch, I got error below:

                                     

                                    adop phase=apply patches=28280348 patchtop=/u01/PATCH

                                     

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

                                    Checking for existing adop sessions.

                                        Continuing with existing session [Session ID: 7].

                                        Session Id            :   7

                                        Prepare phase status  :   COMPLETED

                                        Apply phase status    :   COMPLETED

                                        Cutover  phase status :   NOT COMPLETED

                                        Abort phase status    :   NOT COMPLETED

                                        Session status        :   FAILED

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

                                    ADOP (C.Delta.11)

                                    Session ID: 7

                                    Node: castor

                                    Phase: apply

                                    Log: /u01/apptest3/TEST3/fs_ne/EBSapps/log/adop/7/20190930_203035/adop.log

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

                                     

                                    Applying patch 28280348.

                                        Log: /u01/apptest3/TEST3/fs_ne/EBSapps/log/adop/7/20190930_203035/apply/castor/28280348/log/u28280348.log

                                    ...Unable to connect.

                                     

                                    AutoPatch error:

                                    The following ORACLE error:

                                     

                                    CONNECT APPS/*****

                                    Error while getting a new connection to db

                                     

                                    AutoPatch error:

                                    The following ORACLE error:

                                     

                                    AutoPatch error:

                                    Failed running aidinv() in adprim()

                                     

                                    AutoPatch error:

                                    Failed running Invoker's Rights maintanance logic

                                     

                                    You should check the file

                                    /u01/apptest3/TEST3/fs_ne/EBSapps/log/adop/7/20190930_203035/apply/castor/28280348/log/u28280348.log

                                     

                                    for errors.

                                     

                                        [ERROR]     Cannot connect to database

                                        [ERROR]     Error Message: ORA-12516: TNS:listener could not find available handler with matching protocol stack (DBD ERROR: OCIServerAttach)

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Cannot connect to database

                                        [ERROR]     Error Message: ORA-12516: TNS:listener could not find available handler with matching protocol stack (DBD ERROR: OCIServerAttach)

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                        [ERROR]     Error calling ad_zd_log. Refer to log file for details.

                                     

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

                                     

                                    But I check the listener and it is still up?

                                     

                                    $ lsnrctl status TEST3

                                     

                                    LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 30-SEP-2019 20:51:17

                                    Copyright (c) 1991, 2014, Oracle.  All rights reserved.

                                     

                                    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=prodsrvr.oraclecellc.com)(PORT=1561)))

                                    STATUS of the LISTENER

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

                                    Alias                     TEST3

                                    Version                   TNSLSNR for Linux: Version 12.1.0.2.0 - Production

                                    Start Date                26-SEP-2019 11:38:32

                                    Uptime                    4 days 9 hr. 12 min. 44 sec

                                    Trace Level               off

                                    Security                  ON: Local OS Authentication

                                    SNMP                      OFF

                                    Listener Parameter File   /u01/oratest3/TEST3/12.1.0/network/admin/TEST3_prodsrvr/listener.ora

                                    Listener Log File         /u01/oratest3/TEST3/12.1.0/admin/TEST3_prodsrvr/diag/tnslsnr/prodsrvr/test3/alert/log.xml

                                    Listening Endpoints Summary...

                                      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=prodsrvr.oraclecellc.com)(PORT=1561)))

                                    Services Summary...

                                    Service "TEST3" has 2 instance(s).

                                      Instance "TEST3", status UNKNOWN, has 1 handler(s) for this service...

                                      Instance "TEST3", status READY, has 1 handler(s) for this service...

                                    Service "TEST3_ebs_patch" has 1 instance(s).

                                      Instance "TEST3", status READY, has 1 handler(s) for this service...

                                    Service "ebs_patch" has 1 instance(s).

                                      Instance "TEST3", status READY, has 1 handler(s) for this service...

                                    The command completed successfully

                                     

                                     

                                    Do I need to bounce the apps and database?

                                     

                                    Please help....

                                     

                                    Kind regards,

                                    1 2 3 Previous Next