Online Tutorials & Training Materials | STechies.com
Register Login

LOAD_PROGRAM_CLASS_MISMATCH due to incorr. PUBLIC time stamp

|| || 2

LOAD_PROGRAM_CLASS_MISMATCH due to incorr. PUBLIC time stamp
Stechies

Hello Experts,

What common symptoms can be seen in case of an error ‘LOAD_PROGRAM_CLASS_MISMATCH due to incorr. PUBLIC time stamp’?
How can I get this issue fixed?

Kindly explain with example.

Thanks in advance.


Comments

  • 16 May 2016 3:00 pm

    The following symptoms can be noticed by the user:

    • Even if the class has not been changed for an ABAP class, the short dump LOAD_PROGRAM_CLASS_MISMATCH continues to occur recurrently 
    • The PUBLIC interface of the class has changed according to the "Description of the error situation" section of the short dump.
    • An older version of the PUBLIC interface is used by the class itself than the user of the class.

    For instance:

    Description of the error situation
    During program flow, the section "PUBLIC" of the interface of the class "CL_ST_CRYPTO_SCT13" was changed. Due to this certain inconsistencies were caused at runtime.
    The program "CL_ST_CRYPTO_SCT13============CP" uses the interface version 20110212090738.
    The program "CL_WS_SECURITY_PROTOCOL=======CP" uses the interface version 20110212090739.
    At 20110226094403 the internal session was started.    

  • 16 May 2016 3:09 pm

    To resolve this:

    In kernel release 7.20, this issue can be fixed. However, in older releases, the kernel change necessary for this is not compatible. Due to this, the error cannot be fixed in older releases.
    The report TOUCHSRC can be executed as a workaround for the following programs which includes:

    • The interface has been changed for the PUBLIC include of the class, for instance, CL_ST_CRYPTO_SCT13============CU
    • The interface has been changed for the class, for instance, CL_ST_CRYPTO_SCT13============CP
    • the user of the class, for instance, CL_WS_SECURITY_PROTOCOL=======CP

Related Articles

0.0152 seconds.