Skip to Content
avatar image
Former Member

EHP7 UPGRADE ERROR IN PHASE MAIN_SHDIMP/SUBMOD_SHD2_RUN/RUN_RSAIMMERGE_UPG_SHD

Currently we are stuck in EHP7 upgrade in phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/RUN_RSAIMMERGE_UPG_SHD

shadow instance background job "RSAIMMERGE_UPG_SHD" is getting fails due to the following error

2EETQ399 Error DDIC_FIELDS_NO_ACCESS occured. P1=ABAP-generation exit error,

I have unlocked the shadow instance and tried to find sm37 logs.. but system is giving dump DDIC_FIELDS_NO_ACCESS

also tried with updated kernel still same result

current kernel version in upgrade directory is 753

and main kernel is 721

Thanks

Rafiquersaimmrgshd.txt

ehp7.png (83.7 kB)
rsaimmrgshd.txt (4.9 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • May 03 at 06:26 AM

    Dear Rafique,

    for SUBST_LIST_SYS_LOGS errors I would say the DIR_PUT parameter doesn't point to the Upgrade directory. But I hardly think that this will do the trick here.
    Can you please check the shadow work process traces if they have some more information?



    Cheers,
    Andreas

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 03 at 12:26 PM

    Dear Andreas,

    DIR_PUT parameter by default pointing to /sapmnt/EH7/SUM/abap

    apart from this i did not find any useful link to fasten my resolution towards the error,and i have raised a high level incident to SAP, SAP has taken more than 30 hrs still no update fro their end.

    attaching some trace files form shadow instance.

    Regards

    Rafique

    Add comment
    10|10000 characters needed characters exceeded

  • May 04 at 06:42 AM

    Dear Rafique,

    the issue is too complex to solve it without remote connection. Looks like something is not okay with table AFPOD.

      Generating ABAP Program CL_GUI_ALV_GRID===============CP        .
    A  Source %_CCO                                    Line 29.
    A  Error Code DDIC_FIELDS_NO_ACCESS.
    A  Module  $Id: //bas/749_STACK/src/krn/abap/gen/scsyddic.c#1 $ SAP.
    A  Function sc_ddicflds Line 498. 

    A P1: AFPOD


    You can call CIC to request a speed-up, but this has to be analyze by a consultant on the system.

    Best regards,
    Andreas

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Dear Andreas,

      You are right in regards to table AFPO & Structure.. SAP Has given reply as follows...

      "The problem is that the report ZRUTDDLSACT activates only DDL sources, but classical objects like table and structures not.

      The problem right now in your shadow instance is that the table AFPO doesn't exist on DB level.
      We from dictionary side can't fix objects in the 2nd shadow instance (*_SHD2_*).
      Our recommendation is to check the main instance fro inconsistent dictionary objects, fix those and start the upgrade from scatch.

      You can check and fix the dictionary objects in your system with the report RUTMSJOB "

      I have executed the report RUTMSJOB and found no errors in main instance.

      do we have any oracle level methods/techniques with which we can successfully export import the table into shadow system from main instance? OR

      if i start the whole procedure from scratch what precautions/steps should i take so that this type of error do not occurs

      Regards

      Rafique



      rutmsjob-eh7.txt (17.7 kB)