Inconsistency in the dictionary for the structure "CRMD_ORDERADM_I". dump in production?

[former_member198180]

Hi team,

i am facing the problem on production server after releasing few transport requests i am getting dump like as below .please help.

Category               Internal Kernel Error

Runtime Errors         DDIC_TYPE_INCONSISTENCY

Application Component  BC-ABA-LA

Date and Time          11.02.2016 19:52:01

How to correct the error

     The error was probably caused by changes being made to the

     DDIC structure "CRMD_ORDERADM_I" or one of its substructures and an error

      occurred

     afterwards at activation. Check the runtime object of the structure

      "CRMD_ORDERADM_I"

     in the Dictionary to analyze the exact cause of the error.

     If the program RSNTABCONSISTENCY or its predecessor RSDDCHECK exists in

     your system, you can check structure "CRMD_ORDERADM_I" with the help of one of

      these

     programs.

     If you cannot solve the problem yourself and want to send an error

     notification to SAP, include the following information:

     1. The description of the current problem (short dump)

        To save the description, choose "System->List->Save->Local File

     (Unconverted)".

     2. Corresponding system log

        Display the system log by calling transaction SM21.

        Restrict the time interval to 10 minutes before and five minutes

     after the short dump. Then choose "System->List->Save->Local File

Error analysis

    There is an internal system error.

    eliminated with ABAP/4.

    There is an inconsisteny for the DDIC structure "CRMD_ORDERADM_I", the

     corresponding

    Dictionary runtime object (NAMETAB) is incorrect.

    The number of components of the structure (NAMETAB component "fldcnt")

    is specified as 30. If all the substructures are resolved and the

    actual total number of components is calculated recursively, a different

    value is returned.

How to correct the error

    The error was probably caused by changes being made to the

    DDIC structure "CRMD_ORDERADM_I" or one of its substructures and an error

     occurred

    afterwards at activation. Check the runtime object of the structure

     "CRMD_ORDERADM_I"

    in the Dictionary to analyze the exact cause of the error.

    If the program RSNTABCONSISTENCY or its predecessor RSDDCHECK exists in

    your system, you can check structure "CRMD_ORDERADM_I" with the help of one of

     these

Thanks & Reards

Kalpana

[former_member222142]

Hello Kalpana,

your issue is more related to the Basic Data dictionary community than to the CRM Service area.

Did you make this transport during the business hours ?

because it can be that the DB was not able to process the modification when you transported it.

The SAP recommendation to use transports in non-business hours. Is there  any transport logs with error messages ?

Consider  note 1248769  Inconsistency between database and ABAP dictionary

and 1167784 - runtime error DDIC_TYPE_INCONSISTENCY.

Alternative you can think about re-import of the transport that caused this inconsistency.

Further question could be answered by the Data dictionary community.

Best Regards

Gerhard

[former_member198180]

Hi Gerhard,

Thanks for quick reply...we transported this requests in bussines hours only and we copied live production server to test production server.this test production server only we released all the requests.

i dont know why this dump is coming,we willl try to import transport requests again on live test server.

any other idea to resolve this issue. i found one link but here production we dont have se14 access.is it correct way for adjusting data base table?

how to resolve DDIC_TYPE_INCONSISTENCY error - ABAP Development - SCN Wiki

Thanks & Regards

kalpana

[Former Member]

Hi Kalpana,

While following Gerhard's recommendations, also see OSS Note 1854531.

This dump can also be caused if, when the program was generated, the DDIC structure used was not yet completely activated. As a result, the ABAP generation recognized an inconsistent state.

This issue belong to BC-ABA-LA, it is not a CRM Service issue. Therefore, you may not receive the deserved assistance here. Consider transferring this issue to the right channel.

Best of luck!

[former_member222142]

HI Kalpana,

it's usual and responsible  that the configuration transaction like SE14 are locked on the productiv environment, cause usually the productiv environment are modified/changed via the Development system and Quality/Test system. The transport from the development to the productiv system via the Quality system take place in the system Transport management where the transport route is defined.

Only in exceptional situations or emegency situation the system adminstrator could unlock the system for changes/modification. These had to be done with utmost acurateness to avoid the grow apart of  productiv on the one hand and Development & Qualtiy/Test system on other hand.

Possibly you had to maintain the changes in the development  & Quality/Testsystem afterwards to ensure a consistent System landscape.

As already mentioned more information about these topic are in the Basis Data dictonary community.

Best Regards

Gerhard