Hello Everyone,
In our Solution Manager Development system we can see that the job "LANDSCAPE FETCH" is getting cancelled everyday since 1st February.
From the Job Log I got the below information.
Internal session terminated with a runtime error (see ST22)
And the ST22 Log is as follows.
========================================================
Category ABAP Programming Error
Runtime Errors ASSERTION_FAILED
ABAP Program CL_LMDB_API_SYSTEM_INSTALL_NR=CP
Application Component SV-SMG-LDB
Date and Time 12.02.2016 05:04:07
========================================================
Short text
The ASSERT condition was violated.
========================================================
What happened?
==================================================================================
In the running application program, the ASSERT statement recognized a situation that should not have occurred.
The runtime error was triggered for one of these reasons:
- For the checkpoint group specified with the ASSERT statement, the
activation mode is set to "abort".
- Via a system variant, the activation mode is globally set to "abort"
for checkpoint groups in this system.
- The activation mode is set to "abort" on program level.
- The ASSERT statement is not assigned to any checkpoint group.
===================================================================================
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
===================================================================================
Error analysis
The following checkpoint group was used: "No checkpoint group specified"
If in the ASSERT statement the addition FIELDS was used, you can find
the content of the first 8 specified fields in the following overview:
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
====================================================================================
How to correct the error
Probably the only way to eliminate the error is to correct the program.
-
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:
"ASSERTION_FAILED" " "
"CL_LMDB_API_SYSTEM_INSTALL_NR=CP" or "CL_LMDB_API_SYSTEM_INSTALL_NR=CM003"
"GET_ASSOCIATED_ESID_INSTANCE"
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.
======================================================================================
===================================================================
User and Transaction
Client.............. 100
User................ "SOLMAN_BTC"
Language key........ "E"
Transaction......... " "
Transaction ID...... "3677D1E5BF79F1138442005056992732"
EPP Whole Context ID.... "0050569927321EE3B488220060D62B41"
EPP Connection ID....... "0050569927321EE3B488220F93F88B41"
EPP Caller Counter...... 1
Program............. "CL_LMDB_API_SYSTEM_INSTALL_NR=CP"
Screen.............. "SAPMSSY0 1000"
Screen Line......... 6
Debugger Active..... "none"
====================================================================
Information on where terminated
Termination occurred in the ABAP program "CL_LMDB_API_SYSTEM_INSTALL_NR=CP" -
in "GET_ASSOCIATED_ESID_INSTANCE".
The main program was "RSGET_SMSY ".
In the source code you have the termination point in line 14
of the (Include) program "CL_LMDB_API_SYSTEM_INSTALL_NR=CM003".
The program "CL_LMDB_API_SYSTEM_INSTALL_NR=CP" was started as a background job.
Job Name....... "LANDSCAPE FETCH"
Job Initiator.. "RAVPAN"
Job Number..... 04560500
===========================================================================================
I have done the following checks from Solution Manager Development System end and the result looks ok to us.
1. SLDCHECK
2. SLDAPICUST
Can anybody kindly suggest what might be wrong or if we need to check any extra configuration checks needs to be done?
I cannot see our newly built ECC system under Maintenance Planner. We are suspecting this issue as the cause.
Thanks and Regards
Anurag