on 06-23-2013 4:26 AM
Hi Experts ,
DDIC_TYPE_INCONSISTENCY with most FI transctions occurring after Switch activation. Data Dictionary inconsistencies post-activation caused many transactions with FI/CO area to short dump as below ( also attached ) , please help
Category Internal Kernel Error
Runtime Errors DDIC_TYPE_INCONSISTENCY
Application Component BC-ABA-LA
Date and Time 06/21/2013 19:18:09
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short text |
| Inconsistency in the dictionary for the structure "AFVC". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? |
| Error in the SAP kernel. |
| |
| The current ABAP "%_CCO" program had to be terminated because the |
| ABAP processor detected an internal system error. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What can you do? |
| Note which actions and input led to the error. |
| |
| For further help in handling the problem, contact your SAP administrator |
| . |
| |
| You can use the ABAP dump analysis transaction ST22 to view and manage |
| termination messages, in particular for long term reference. |
| |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Error analysis |
| There is an internal system error. |
| eliminated with ABAP/4. |
| |
| There is an inconsisteny for the DDIC structure "AFVC", the corresponding |
| Dictionary runtime object (NAMETAB) is incorrect. |
| |
| The number of components of the structure (NAMETAB component "fldcnt") |
| is specified as 179. 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 "AFVC" or one of its substructures and an error occurred |
| afterwards at activation. Check the runtime object of the structure "AFVC" |
| 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 "AFVC" 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 |
| (Unconverted)". |
| |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error. |
| |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|System environment |
| SAP Release..... 731 |
| SAP Basis Level. 0005 |
| |
| Application server... "sapk1lci" |
| Network address...... "10.54.172.67" |
| Operating system..... "AIX" |
| Release.............. "6.1" |
| Hardware type........ "00F76DD84C00" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 7 |
| Shortdump setting.... "full" |
| |
| Database server... "sapk1ldb" |
| Database type..... "ORACLE" |
| Database name..... "K1L" |
| Database user ID.. "SAPSR3" |
| |
| Terminal.......... " " |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 720 |
| created (date)... "Dec 16 2012 19:50:53" |
| create on........ "AIX 1 6 00C7B8024C00" |
| Database version. "OCI_112, 11.2.0.3.0, V1, default" |
| |
| Patch level. 400 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 720 |
| Operating system..... "AIX 1 6, AIX 1 7" |
| |
| Memory consumption |
| Roll.... 0 |
| EM...... 4189792 |
| Heap.... 0 |
| Page.... 0 |
| MM Used. 3016112 |
| MM Free. 1171008 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|User and Transaction |
| Client.............. 000 |
| User................ "SAPSYS" |
| Language key........ "E" |
| Transaction......... " " |
| Transaction ID...... "51C31B5ED8634540E10080000A36AC43" |
| |
| EPP Whole Context ID.... " " |
| EPP Connection ID....... " " |
| EPP Caller Counter...... 0 |
| |
| Program............. "%_CCO" |
| Screen.............. " " |
| Screen Line......... " " |
| Debugger Active..... "none" |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Information on where terminated |
| The termination occurred during generation of the ABAP/4 program "%_CCO". |
| - |
| |
| The termination occurred in line 13 |
| of the source code of program "%_CCO" (when calling the editor 130). |
| The program "%_CCO" was started as a background job. |
| Job Name....... " " |
| Job Initiator.. " " |
| Job Number..... " " |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Source Code Extract |
----------------------------------------------------------------------------------------------------
|Line |SourceCde |
----------------------------------------------------------------------------------------------------
| 1|TYPE-POOL co . |
| 2|* Type für Auftragskopie erstellen |
| 3|TYPES: BEGIN OF co_ord_idx, |
| 4| aufnr_old LIKE aufk-aufnr, |
| 5| index_new LIKE sy-tabix, |
| 6| flg_append TYPE c, |
| 7| rsnum_old LIKE afko-rsnum, |
| 8| stsma_old LIKE jsto-stsma, |
| 9| END OF co_ord_idx. |
| 10|TYPES: co_ord_tab LIKE typ_ord_idx OCCURS 0. |
| 11| |
| 12|TYPES: BEGIN OF co_opr_idx, |
|>>>>>| aufpl_old LIKE afvc-aufpl, |
| 14| aplzl_old LIKE afvc-aplzl, |
| 15| index_new LIKE sy-tabix, |
| 16| END OF co_opr_idx. |
| 17|TYPES: co_opr_tab TYPE co_opr_idx OCCURS 0. |
| 18| |
| 19|TYPES: BEGIN OF co_cmp_idx, |
| 20| rsnum_old LIKE resb-rsnum, |
| 21| rspos_old LIKE resb-rspos, |
| 22| rsart_old LIKE resb-rsart, |
| 23| index_new LIKE sy-tabix, |
| 24| END OF co_cmp_idx. |
| 25|TYPES: co_cmp_tab TYPE co_cmp_idx OCCURS 0. |
| 26| |
| 27|TYPES: co_affhd_tab LIKE STANDARD TABLE OF affhd WITH DEFAULT KEY, |
| 28| co_affld_tab LIKE STANDARD TABLE OF affld WITH DEFAULT KEY, |
| 29| co_afpod_tab LIKE STANDARD TABLE OF afpod WITH DEFAULT KEY, |
| 30| co_afvgd_tab LIKE STANDARD TABLE OF afvgd WITH DEFAULT KEY, |
| 31| co_caufvd_tab LIKE STANDARD TABLE OF caufvd WITH DEFAULT KEY, |
| 32| co_resbd_tab LIKE STANDARD TABLE OF resbd WITH DEFAULT KEY. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Internal notes |
| The termination was triggered in function "ab_RxDdicTypeError" |
| of the SAP kernel, in line 1069 of the module |
| "//bas/720_REL/src/krn/runt/abucutil.c#4". |
| The internal operation just processed is " ". |
| Internal mode was started at 20130621191809. |
| There is an inconsistency in the DDIC structure "AFVC", the corresponding |
| dictionary runtime object (NAMETAB) is incorrect. |
| |
| The number of components of the structure (NAMETAB component "fldcnt") |
| is specified using 179. 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 "AFVC" or one of its substructures |
| was changed and an error occurred in the subsequent activation. Please |
| check the runtime object of the structure "AFVC" 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 "AFVC". |
| |
| |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Active Calls in SAP Kernel |
----------------------------------------------------------------------------------------------------
|Lines of C Stack in Kernel (Structure Differs on Each Platform) |
----------------------------------------------------------------------------------------------------
|=> 64 bit R/3 Kernel |
|=> 64 bit AIX Kernel |
|=> Heap limit = unlimited |
|=> Stack limit = 33554432 |
|=> Core limit = unlimited |
|=> File size limit = unlimited |
|=> Heap address = 0x11d086bc0 |
|=> Stack address = 0xffffffffffe3ed0 |
|=> Stack low = 0xffffffffffe3ed0 |
|=> Stack high = 0xfffffffffffedc0 |
|=> Stack Trace: |
| AixStack() at 0x10015cda4 |
| CTrcStack2() at 0x10015cc98 |
| rabax_CStackSave__Fv@AF172_21() at 0x1002f50e8 |
| ab_rabax() at 0x1002e2f90 |
| ab_RxDdicTypeError__FPCUsUi() at 0x100a9df10 |
| firstLevelChildCnt__2UcFP7sc_type() at 0x100850e18 |
| typeToTree__2UcFP9UC_BUFFERUiP7sc_typeP7UC_NODEP17UC_CUST_INCL_INFOP18UC_UNSIGNED_TRIPLEP13UC_ALI|
| typeToFragView__2UcFPP12UC_FRAG_VIEWP17UC_CUST_INCL_INFOP7sc_type() at 0x1008500a4 |
| runUc__2UcFP7sc_type() at 0x10084fe54 |
| sc_tparUcFragView__FP7sc_type() at 0x10084fd38 |
| sc_loadflds__FP7sc_type() at 0x10049ed34 |
| simple_type_find_1__FPCUs9TYPE_MODEPP3ENVP7SC_INFO() at 0x1004a42ec |
| sc_complex_type_find__FPCUs9TYPE_MODEP7SC_INFO() at 0x1004a2ca4 |
| sc_data_type_find_1__FPCUs7HD_BOOLP6SC_LOCP7SC_INFO() at 0x1008733b0 |
| sc_data_type_find__FPCUs7HD_BOOLP6SC_LOCP7SC_INFO() at 0x100872be8 |
| sc_ctypid_do__FPCUs9TYPE_MODEUiP7SC_INFO() at 0x1004a0e28 |
| sc_ctypid__FPCUs9TYPE_MODEUi7HD_BOOLP7SC_INFO() at 0x1004a0520 |
| sc_typid() at 0x101d07b90 |
| rs_oper_abap5971() at 0x1021773a4 |
| Unknown at 0x101ff1d14 |
| sc_expan__FUi() at 0x101d1a26c |
| parse__FP5LEVEL() at 0x101d571b4 |
| checkStatement__FiPP4STMTP5LEVELPP3ENVN41() at 0x101d4fb6c |
| sc_check() at 0x101d4cdf8 |
| sc_checkStart() at 0x101d4c908 |
| cg_generate() at 0x1004adef4 |
| ab_gabap() at 0x100467e4c |
| dy_gen_abap() at 0x101436dc4 |
| generateProgram__FPCUsUc() at 0x10273d7ac |
| ab_APGWorker() at 0x10273ce14 |
| ThSchedCallDelayed() at 0x1012c4cdc |
| TskhLoop() at 0x100264e3c |
| ThStart() at 0x10025f9b4 |
| DpMain() at 0x100024fb4 |
| nlsui_main() at 0x100000934 |
----------------------------------------------------------------------------------------------------
Hello
Call Tx SE38 and execute the program RSNTABCONSISTENCY or RSDDCHECK for a consistency check.
Select "Individual Objects". Enter AFVC and execute.
Try to activate the structure AFVC from Tx SE11.
If it throws an error then call Tx SE37 and execute the function module DD_NAMETAB_DELETE against the structure AFVC.
Once done activate the structure AFVC from Tx SE11.
Good Luck
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Kindly check below SAP Notes and also run the SGEN
Note 1854531 - Individual DDIC_TYPE_INCONSISTENCY Rabax during upgrade
Note 1686842 - Missing authorization check in ABAP Dump Collector
Thanks
Ram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abu,
You can check the runtime object consistency .
Se11->utilities->runtime object->Check.
Post this you may go to SE14 and activate the structure once again to correct the inconsistencies.
Hope this helps.
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.