cancel
Showing results for 
Search instead for 
Did you mean: 

Dump DDIC_TYPE_INCONSISTENCY

former_member209959
Participant
0 Kudos

Hi everybody,

We have installed a SAP Netweaver Mobile 7.1 and then we have imported the support packages until 14. The import was fine but when we tried tx SM21 we got the dump DDIC_TYPE_INCONSISTENCY in structure SXMS_MO_ATTR. In service.sap there are no notes relationated with it and we don't have the license yet, so SAP can't connect with our system.

The log in ST22 is:

Runtime Errors DDIC_TYPE_INCONSISTENCY
Date and Time 10.10.2012 16:01:00
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Short text |
| Inconsistency in the dictionary for the structure "SXMS_MO_ATTR". |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|What happened? |
| Error in the SAP kernel |
| |
| The current ABAP program "SAPLSLO2_ALV" had to be terminated because the |
| ABAP processor detected an internal system error. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|What can you do? |
| Please make a note of the actions and input which caused the error. |
| - |
| |
| To resolve the problem, contact your |
| SAP system administrator. |
| |
| Using transaction ST22 for ABAP dump analysis you can see and |
| administrate termination messages and retain them for longer periods. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Error analysis |
| There is an internal system error. |
| eliminated with ABAP/4. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|How to correct the error |
| It is probably not possible to eliminate the system error |
| with ABAP alone. |
| |
| There may already be a solution in the SAP Notes system. If you have |
| access to the SAP Notes system then check there first using the |
| following keywords: |
| "DDIC_TYPE_INCONSISTENCY" " " |
| "SAPLSLO2_ALV" or "IF_XMS_PROP===================IU" |
| " " |
| You may able to find an interim solution to the problem |
| in the SAP note system. If you have access to the note system yourself, |
| please use the following search criteria: |
| |
| "DDIC_TYPE_INCONSISTENCY" " " |
| "SAPLSLO2_ALV" bzw. "IF_XMS_PROP===================IU" |
| " " |
| If you cannot solve the problem yourself, please send the |
| following documents to SAP: |
| |
| 1. A hard copy print describing the problem (short dump). |
| To obtain this, select "System->List->Save->Local File (unconverted)" |
| on the current screen. |
| |
| 2. A suitable hardcopy printout of the system log. |
| To obtain this, call the system log with Transaction SM21 |
| and set the time interval to 10 minutes before and 5 minutes after |
| the short dump. In the display choose "System->List->Save-> |
| Local File (unconverted)" |
| |
| 3. If the programs are your own programs or modified SAP programs, |
| supply the source code. |
| To do this, choose "More Utilities->Upload/Download->Download" in the |
| Editor. |
| |
| 4. Details regarding the conditions under which the error occurred |
| or which actions and input led to the error. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|System environment |
| SAP-Release 710 |
| |
| Application server... "xxxx" |
| Network address...... "xxx.xxx.x.xx" |
| Operating system..... "SunOS" |
| Release.............. "5.10" |
| Hardware type........ "i86pc" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 4 |
| Shortdump setting.... "full" |
| |
| Database server... "hierro" |
| Database type..... "ORACLE" |
| Database name..... "MBD" |
| Database user ID.. "SAPSR3" |
| |
| Terminal.......... "srv-saprmt" |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 710 |
| created (date)... "Jul 22 2012 21:34:26" |
| create on........ "SunOS 5.10 Generic_118844-27 i86pc" |
| Database version. "OCI_102, 10.2.0.2.0 " |
| |
| Patch level. 279 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 710 |
| Operating system..... "SunOS 5.10, SunOS 5.11" |
| |
| Memory consumption |
| Roll.... 16192 |
| EM...... 125694960 |
| Heap.... 0 |
| Page.... 0 |
| MM Used. 49743736 |
| MM Free. 67563544 |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|User and Transaction |
| Client.............. 000 |
| User................ "ADMIN" |
| Language key........ "E" |
| Transaction......... " " |
| Transaction ID...... "5074B12C4ECF5368E1000000C0A8042C" |
| |
| Program............. "SAPLSLO2_ALV" |
| Screen.............. " " |
| Screen line......... " " |
| Debugger Active..... "none" |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Information on where terminated |
| The termination occurred during generation of the ABAP/4 program |
| "SAPLSLO2_ALV". |
| - |
| |
| The termination occurred in line 49 |
| of the source code of program "IF_XMS_PROP===================IU" (when calling |
| the editor 490). |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Source Code Extract |
----------------------------------------------------------------------------------------------------
|Line |SourceCde |
----------------------------------------------------------------------------------------------------
| 19| raising |
| 20| CX_XMS_SYSTEM_ERROR . |
| 21| methods WRITETOXMLSTRING |
| 22| importing |
| 23| !NSCONTEXT type ref to IF_XMS_NSCONTEXT optional |
| 24| !EXTERNAL type SXMSFLAG default '1' |
| 25| !PARSING_METHOD type CHAR1 default CL_XMS_PARSER=>CO_PARSING_METHOD_UNDEF |
| 26| returning |
| 27| value(VALUE) type STRING |
| 28| raising |
| 29| CX_XMS_SYSTEM_ERROR . |
| 30| methods GETMUSTUNDERSTAND |
| 31| returning |
| 32| value(RETURN) type SXMSFLAG . |
| 33| methods SETMUSTUNDERSTAND |
| 34| importing |
| 35| !MUSTUNDERSTAND type SXMSFLAG . |
| 36| methods ISEXTERNAL |
| 37| returning |
| 38| value(RE_EXTERNAL) type SXMSFLAG . |
| 39| methods SETNAMESPACEURI |
| 40| importing |
| 41| !IM_NSURI type STRING . |
| 42| methods SETLOCALNAME |
| 43| importing |
| 44| !IM_LCNAME type STRING . |
| 45| methods GET_ATTRIBUTES |
| 46| exporting |
| 47| !INDEX type I |
| 48| changing |
|>>>>>| !MO_ATTR type SXMS_MO_ATTR . |
| 50| methods SET_ATTRIBUTES |
| 51| importing |
| 52| !MO_ATTR type SXMS_MO_ATTR |
| 53| !INDEX type I . |
| 54|endinterface. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Internal notes |
| The termination was triggered in function "ab_RxDdicTypeError" |
| of the SAP kernel, in line 1088 of the module |
| "//bas/710_REL/src/krn/runt/abucutil.c#6". |
| The internal operation just processed is " ". |
| Internal mode was started at 20121010160051. |
| There is an inconsistency in the DDIC structure "SXMS_MO_ATTR", the |
| corresponding |
| dictionary runtime object (NAMETAB) is incorrect. |
| |
| The number of components of the structure (NAMETAB component "fldcnt") |
| is specified using 153. If you dismantle all the substructures and |
| calculate the actual total number of all the components recursively |
| then the result is a different value. |
| |
| The error was caused because structure "SXMS_MO_ATTR" or one of its |
| substructures |
| was changed and an error occurred in the subsequent activation. Please |
| check the runtime object of the structure "SXMS_MO_ATTR" in the dictionary to |
| analysis the exact error cause. |
| |
| If the program RSDDCHECK is available on your system, you can also use |
| it to check structure "SXMS_MO_ATTR". |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Active Calls in SAP Kernel |
----------------------------------------------------------------------------------------------------
|Lines of C Stack in Kernel (Structure Differs on Each Platform) |
----------------------------------------------------------------------------------------------------
|[0] DoStack2, at 0xb2c894 |
|[1] CTrcStack2, at 0xb2c543 |
|[2] CTrcStack, at 0xb2c4ec |
|[3] __1cQrabax_CStackSave6F_v_, at 0xd779de |
|[4] ab_rabax, at 0xd6bbd3 |
|[5] __1cSab_RxDdicTypeError6FpkHI_v_, at 0x101c596 |
|[6] __1cCUcKtypeToTree6MpnJUC_BUFFER_IpnHsc_type_pnHUC_NODE_pnRUC_CUST_INCL_INFO_pnSUC_UNSIGNED_TR|
|[7] __1cCUcOtypeToFragView6MppnMUC_FRAG_VIEW_pnRUC_CUST_INCL_INFO_pnHsc_type__v_, at 0x15fa405 |
|[8] __1cCUcDrun6MpnHsc_type__pnMUC_FRAG_VIEW__, at 0x15fa066 |
|[9] __1cRsc_tparUcFragView6FpnHsc_type__pv_, at 0x15f9f75 |
|[10] __1cLsc_loadflds6FpnHsc_type__v_, at 0x1624a56 |
|[11] __1cLsc_ddictype6FpkHnHHD_BOOL_pnHSC_INFO__nMCHECK_RESULT__, at 0x15a542d |
|[12] __1cSglobalTypeFindDdic6FpkHnJNEED_KIND_pnHSC_INFO__nMCHECK_RESULT__, at 0x162d558 |
|[13] __1cQscGlobalTypeFind6FpkHnJNEED_KIND_nHHD_BOOL_3pnHSC_INFO__3_, at 0x162d3f0 |
|[14] __1cSsimple_type_find_16FpkHnJTYPE_MODE_ppnDENV_pnHSC_INFO__nHHD_BOOL__, at 0x162d1bd |
|[15] __1cUsc_complex_type_find6FpkHnJTYPE_MODE_pnHSC_INFO__nHHD_BOOL__, at 0x162c0b9 |
|[16] __1cMsc_ctypid_do6FpkHnJTYPE_MODE_IpnHSC_INFO__nHHD_BOOL__, at 0x162ac3f |
|[17] __1cJsc_ctypid6FpkHnJTYPE_MODE_InHHD_BOOL_pnHSC_INFO__3_, at 0x162a9e3 |
|[18] __1cJsymb_type6FpkHC1ipnHSC_INFO__nHHD_BOOL__, at 0x1517d45 |
|[19] __1cOlist_patt_look6FpnIPATTHEAD_pnELIST_ipnKVAR_BUFFER_ipnHMSG_POS_pii_i_, at 0x152481a |
|[20] __1cJlist_patt6FpppkHpipnIPATTHEAD_pnKVAR_BUFFER_ipnHMSG_POS_4_i_, at 0x1523e92 |
|[21] __1cJpatt_look6FpnIPATTHEAD_pii_i_, at 0x15231de |
|[22] sc_patte, at 0x1522aaf |
|[23] rs_oper_abap3444, at 0x19314e9 |
|[24] rs_expan_abap, at 0x17f7247 |
|[25] __1cIsc_expan6FI_i_, at 0x14e1587 |
|[26] __1cFparse6FpnFLEVEL__i_, at 0x14d3f16 |
|[27] sc_check, at 0x14d15aa |
|[28] sc_inclu, at 0x14c8ad8 |
|[29] rs_oper_abap3090, at 0x1925e60 |
|[30] rs_expan_abap, at 0x17d5d6e |
|[31] __1cIsc_expan6FI_i_, at 0x14e1587 |
|[32] __1cFparse6FpnFLEVEL__i_, at 0x14d3f16 |
|[33] sc_check, at 0x14d15aa |
|[34] __1cLProcessText6FI_i_, at 0x14d0e7e |
|[35] sc_check, at 0x14d15ed |
|[36] sc_inclu, at 0x14c8ad8 |
|[37] rs_oper_abap3090, at 0x1925e60 |
|[38] rs_expan_abap, at 0x17d5d6e |
|[39] __1cIsc_expan6FI_i_, at 0x14e1587 |
|[40] __1cFparse6FpnFLEVEL__i_, at 0x14d3f16 |
|[41] sc_check, at 0x14d15aa |
|[42] __1cLProcessText6FI_i_, at 0x14d0e7e |
|[43] sc_check, at 0x14d15ed |
|[44] sc_inclu, at 0x14c8ad8 |
|[45] rs_oper_abap3090, at 0x1925e60 |
|[46] rs_expan_abap, at 0x17d5d6e |
|[47] __1cIsc_expan6FI_i_, at 0x14e1587 |
|[48] __1cFparse6FpnFLEVEL__i_, at 0x14d3f16 |
|[49] sc_check, at 0x14d15aa |
|[50] __1cLProcessText6FI_i_, at 0x14d0e7e |
|[51] sc_check, at 0x14d15ed |
|[52] sc_inclu, at 0x14c8ad8 |
|[53] rs_oper_abap3090, at 0x1925e60 |
|[54] rs_expan_abap, at 0x17d5d6e |
|[55] __1cIsc_expan6FI_i_, at 0x14e1587 |
|[56] __1cFparse6FpnFLEVEL__i_, at 0x14d3f16 |
|[57] sc_check, at 0x14d15aa |
|[58] __1cLProcessText6FI_i_, at 0x14d0e7e |
|[59] sc_check, at 0x14d15ed |
|[60] sc_inclu, at 0x14c8ad8 |
|[61] rs_oper_abap3090, at 0x1925e60 |
|[62] rs_expan_abap, at 0x17d5d6e |
|[63] __1cIsc_expan6FI_i_, at 0x14e1587 |
|[64] __1cFparse6FpnFLEVEL__i_, at 0x14d3f16 |
|[65] sc_check, at 0x14d15aa |
|[66] __1cLProcessText6FI_i_, at 0x14d0e7e |
|[67] sc_check, at 0x14d15ed |
|[68] sc_inclu, at 0x14c8ad8 |
|[69] rs_oper_abap3090, at 0x1925e60 |
|[70] rs_expan_abap, at 0x17d5d6e |
|[71] __1cIsc_expan6FI_i_, at 0x14e1587 |
|[72] __1cFparse6FpnFLEVEL__i_, at 0x14d3f16 |
|[73] sc_check, at 0x14d15aa |
|[74] __1cLProcessText6FI_i_, at 0x14d0e7e |
|[75] sc_check, at 0x14d15ed |
|[76] sc_inclu, at 0x14c8ad8 |
|[77] rs_oper_abap3090, at 0x1925e60 |
|[78] rs_expan_abap, at 0x17d5d6e |
|[79] __1cIsc_expan6FI_i_, at 0x14e1587 |
|[80] __1cFparse6FpnFLEVEL__i_, at 0x14d3f16 |
|[81] sc_check, at 0x14d15aa |
|[82] __1cLProcessText6FI_i_, at 0x14d0e7e |
|[83] sc_check, at 0x14d15ed |
|[84] sc_inclu, at 0x14c8ad8 |
|[85] rs_oper_abap3090, at 0x1925e60 |
|[86] rs_expan_abap, at 0x17d5d6e |
|[87] __1cIsc_expan6FI_i_, at 0x14e1587 |
|[88] __1cFparse6FpnFLEVEL__i_, at 0x14d3f16 |
|[89] sc_check, at 0x14d15aa |
|[90] __1cLProcessText6FI_i_, at 0x14d0e7e |
|[91] sc_check, at 0x14d15ed |
|[92] sc_inclu, at 0x14c8ad8 |
|[93] rs_oper_abap3090, at 0x1925e60 |
|[94] rs_expan_abap, at 0x17d5d6e |
|[95] __1cIsc_expan6FI_i_, at 0x14e1587 |
|[96] __1cFparse6FpnFLEVEL__i_, at 0x14d3f16 |
|[97] sc_check, at 0x14d15aa |
|[98] sc_inclu, at 0x14c8ad8 |
|[99] rs_oper_abap3090, at 0x1925e60 |
|[100] rs_expan_abap, at 0x17d5d6e |
|[101] __1cIsc_expan6FI_i_, at 0x14e1587 |
|[102] __1cFparse6FpnFLEVEL__i_, at 0x14d3f16 |
|[103] sc_check, at 0x14d15aa |
|[104] sc_checkStart, at 0x14d0d8c |
|[105] cg_generate, at 0x14b3425 |
|[106] ab_gabap, at 0xd3c556 |
|[107] dy_gen_abap, at 0xb545e0 |
|[108] ab_genprog, at 0xd3b3cc |
|[109] __1cHnewload6FpkHpnNTmpSubpoolDir_IpI_i_, at 0x10208c2 |
|[110] __1cRab_LoadProgOrTrfo6FpkHIpI_i_, at 0x1020558 |
|[111] __1cLab_LoadProg6FpkHI_i_, at 0x1020361 |
|[112] ab_link, at 0x101fbe4 |
|[113] __1cIab_jfunc6F_v_, at 0xd232c6 |
|[114] __1cIab_extri6F_i_, at 0xcf73ff |
|[115] __1cJab_xevent6FpkH_i_, at 0xd894da |
|[116] ab_dstep, at 0xcecaeb |
|[117] dynpmcal, at 0xb4bff5 |
|[118] dynppbo0, at 0xb48ab8 |
|[119] dynprctl, at 0xb482e7 |
|[120] dynpen00, at 0xb44b60 |
|[121] Thdynpen00, at 0x969257 |
|[122] TskhLoop, at 0x965db9 |
|[123] ThStart, at 0x95e64a |
|[124] DpMain, at 0x8ba6c9 |
|[125] nlsui_main, at 0x8b89d9 |
|[126] main, at 0x8b89c0 |
----------------------------------------------------------------------------------------------------

Any ideas?

Best Regards.

Accepted Solutions (1)

Accepted Solutions (1)

JPReyes
Active Contributor
0 Kudos

Run the checks on SAP Note 1167784 - Runtime error DDIC_TYPE_INCONSISTENCY

Regards

Juan

former_member209959
Participant
0 Kudos

Hi Juan,

I had checked the report RSNTABCONSISTENCY from Note 1167784 and I found:

Objects with Inconsistent Runtime Object

TABL SXMS_MO_ATTR

NT header................: No. fields(FLDCNT)..... Act: 00F4...... Exp: 00F7......
NT header................: Tab.length(TABLEN)..... Act: 00001A70.. Exp: 00001CA8..
EOIO_VIOL_ACTIONRO Field not in active nametab
EOIO_VIOL_IDRO Field not in active nametab
IS_URLRO Field not in active nametab

The report itself allowed activate the fields and now the dump has disappeared.

Thanks Juan

Answers (0)