DDIC_TYPE_INCONSISTENCY

Question

Hello,
A lot of dumps(around 500) "DDIC_TYPE_INCONSISTENCY" occuring in ECC 6.0 after a kernel upgrade.
The kernel info is :
Application Server pkgp410d_P41_00
SAP Kernel Information
SAP Kernel :  720_REL
Database Client Library : OCI_102, 11.2.0.2.0, V1, default
created in  :  Linux GNU SLES-9 x86_64 cc4.1.2
created on  :  Sep 14 2013 05:05:10
Support Level  :  0
Kernel Patch number : 500
Source ID  :  0.500
DBSL Patch No. : 425
ICU Version : 3.4 Unicode Version 4.1
Supported Environment
What can be the causes for this?
I heard there are GO LIVE transports that shud run in the system.Can that be the reason for the dumps..If so,plaese explain why?
MANY THANKS!
UDAY.

Answer 1

Hello,
Short Text
    Inconsistency in the Dictionary for the structure "KOMPAZ".
What happened?
    Error in the SAP kernel.
    The current ABAP "SAPLME02" 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.
How to correct the error
    The internal system error cannot be fixed by ABAP means only.
    You may be able to find a solution in the SAP note system. If you have
    access to the SAP note system, try searching for the following terms:
     "DDIC_TYPE_INCONSISTENCY" " "
"SAPLME02" or "%_CMMPUR"
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DDIC_TYPE_INCONSISTENCY" " "
"SAPLME02" or "%_CMMPUR"
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.
SAP-Release 700
Application server...
Network address.....
Operating system..... "Linux"
Release.............. "3.0.93-0.8-default"
Hardware type........ "x86_64"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 5
Shortdump setting.... "full"
Database server... "     "
Database type..... "ORACLE"
Database name..... "..."
Database user ID.. "SAPSR3"
Terminal................. " "
Char.set.... "de_DE.ISO-8859-1"
SAP kernel....... 720
created (date)... "Sep 14 2013 05:05:10"
create on........ "Linux GNU SLES-9 x86_64 cc4.1.2 "
Database version. "OCI_102, 11.2.0.2.0, V1, default"
Patch level. 500
Patch text.. " "
Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
SAP database version. 720
Operating system..... "Linux 2.6, Linux 3"
Memory consumption
Roll.... 0
EM...... 6278160
Heap.... 0
Page.... 0