After the upgrade from Solution Manager 7.1 to Solution Manager 7.2 one is facing unexpected ASSERTION_FAILED dumps.
In the header of the dump the following information can be found:
Category ABAP Programming Error
Runtime Errors ASSERTION_FAILED
ABAP Program CL_SMSY_TRACER================CP
Application Component SV-SMG-SYS
A closer look at the dump shows the application termiated at the following code:
| 45| " SolMan 7.2 SP0: Trigger Dump also without checkpoint activation |
| 46| |
|>>>>>| assert fields lv_no_smsy_usage |
| 48| iv_msg |
| 49| iv_char_param_1 |
| 50| iv_char_param_2 |
| 51| iv_char_param_3
In the active calls of the dump for example the following calls can be observed:
28 METHOD CL_SMSY_TRACER================CP CL_SMSY_TRACER================CM00L 47
27 METHOD CL_SMSY_TRACER================CP CL_SMSY_TRACER================CM004 83
26 FUNCTION SAPLSMSY_GET_DATA LSMSY_GET_DATAU05 24
25 FUNCTION SAPLZ_OLD_SMSY LZ_OLD_SMSYU03 49
In this example above one can observe that the function SMSY_GET_SYSTEM_INFO is called out of customer related Z-Coding.
Solution Manager 7.2
ASSERTION_FAILED, CL_SMSY_TRACER, TRIGGER_DUMP, ST22, Customer Coding, Landscape API for Diagnostics, LMDB, lv_no_smsy_usage, CL_DIAGLS_FACTORY. , KBA , SV-SMG-SYS , Solution Manager System Landscape , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.