/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
A dump like this is observed in ABAP via ST22 tcode on a Netweaver client :
Category ABAP programming error
Runtime Errors RAISE_SHORTDUMP
Except. CX_SADL_DUMP_DATABASE_FAILURE
Development Object < >
Application Component < >
Date and Time 2022/09/26 14:36:01 (JAPAN)
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short Text |
| The current application has intentionally triggered a termination with |
| a short dump. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? |
| The current application program has recognised an error that it could |
| not handle adequately. To reverse any database changes made and to save |
| information for further analysis, the application program has |
| intentionally triggered a short dump using the language elements RAISE |
| SHORTDUMP or THROW SHORTDUMP. |
| For more information follow the link: ABAP Keyword Documentation. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What can you do? |
| Note which actions and entries caused the error to occur. |
| |
| Consult your SAP administrator. |
| |
| Using transaction ST22 for ABAP dump analysis, you can view, manage, |
| and retain termination messages for longer periods. |
| Note which actions and entries caused the error to occur. |
| |
| Consult your SAP administrator. |
| |
| Using transaction ST22 for ABAP dump analysis, you can view, manage, |
| and retain termination messages for longer periods. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Error analysis |
| The application has indicated exception "CX_SADL_DUMP_DATABASE_FAILURE" as the |
| reason for the |
| termination: |
| An unrecoverable error has occurred: See previous in exception chain. |
| |
| The exception is related to the previous exception |
| "CX_SADL_GW_V2_FATAL_REQUEST" that occurred in |
| program "SAPMHTTP", in line 0 of include "???". The reason for this exception |
| was: |
| Fatal error in SADL OData v2 request processing (mapping provider |
| 'MPE_ACTION_LOG') |
| |
| The exception is related to the previous exception "CX_SADL_SQL_EXECUTION" |
| that occurred in |
| program "CL_SADL_SQL_EXECUTOR_EXC_HNDLRCP", in line 2 of include |
| "CL_SADL_SQL_EXECUTOR_EXC_HNDLRCM001". The reason for this exception |
| was: |
| Execution of a SADL-assembled SQL query failed, see previous exception |
| |
| The exception is related to the previous exception "CX_SY_OPEN_SQL_DB" that |
| occurred in |
| program "CL_SADL_SQL_EXECUTOR==========CP", in line 71 of include |
| "CL_SADL_SQL_EXECUTOR==========CM00A". The reason for this exception |
| was: |
| The database registered an internal error. SQL code 4. The error text is: |
| cannot allocate enough memory: please check traces for further information. |
| |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Chain of Exception Objects |
----------------------------------------------------------------------------------------------------
|Level Class |
|Attrib. Name Value |
----------------------------------------------------------------------------------------------------
|1 CX_SADL_DUMP_DATABASE_FAILURE |
|(Program) CL_SADL_SHORTDUMP=============CP |
|(Include) CL_SADL_SHORTDUMP=============CM009 |
|(Row) 2 |
|(Short Text) An unrecoverable error has occurred: See previous in exception |
| chain. |
|T100_MSGID SADL_DIAGNOSTIC |
|T100_MSGNO 000 |
|T100_MSGV1 See previous in exception chain. |
|CLASSIFICATION DATABASE_ISSUE |
|IS_RESUMABLE |
|KERNEL_ERRID |
|ORIGIN_DEVELOPMENT_OBJECT_NAME MPE_ACTION_LOG |
|ORIGIN_DEVELOPMENT_OBJECT_TYPE IWPR |
|REASON See previous in exception chain. |
----------------------------------------------------------------------------------------------------
|2 CX_SADL_GW_V2_FATAL_REQUEST |
|(Program) SAPMHTTP |
|(Include) ??? |
|(Row) 0 |
|(Short Text) Fatal error in SADL OData v2 request processing (mapping provider |
| 'MPE_ACTION_LOG') |
|T100_MSGID SADL_GW |
|T100_MSGNO 040 |
|T100_MSGV1 MPE_ACTION_LOG |
|IS_RESUMABLE |
|KERNEL_ERRID |
|MAPPING_PROVIDER_UUID MPE_ACTION_LOG |
----------------------------------------------------------------------------------------------------
|3 CX_SADL_SQL_EXECUTION |
|(Program) CL_SADL_SQL_EXECUTOR_EXC_HNDLRCP |
|(Include) CL_SADL_SQL_EXECUTOR_EXC_HNDLRCM001 |
|(Row) 2 |
|(Short Text) Execution of a SADL-assembled SQL query failed, see previous |
| exception |
|T100_MSGID SADL_SQL |
|T100_MSGNO 000 |
|IS_RESUMABLE |
|KERNEL_ERRID |
|SERIALIZED_RAW_QUERY SADLSQL:V1:LOAD(22150):[6648]eyJEWU5BTUlDX1NRTF9DTEFVU0VTIjp7IlNFTE|
| VDVCI6IkNfTUZHRVhFQ0VWRU5USElTVE9SWX5BU1NFTUJMRURCQVRDSCBBUyBBU1NFT|
| UJMRURCQVRDSCwgQ19NRkdFWEVDRVZFTlRISVNUT1JZfkFTU0VNQkxFRFNFUklBTE5V|
| TUJFUiBBUyBBU1NFTUJMRURTRVJJQU... |
|_00_COUNT_ONLY |
|_01_SELECT C_MFGEXECEVENTHISTORY~ASSEMBLEDBATCH AS ASSEMBLEDBATCH, C_MFGEXECEV|
| ENTHISTORY~ASSEMBLEDSERIALNUMBER AS ASSEMBLEDSERIALNUMBER, C_MFGEXE|
| CEVENTHISTORY~BUSINESSPROCESSCONFIRMEDQTY AS BUSINESSPROCESSCONFIRM|
| EDQTY, C_MFGEXECEVENTHISTORY~CHANGEDOCDA... |
|_02_FROM C_MFGEXECEVENTHISTORY AS C_MFGEXECEVENTHISTORY |
|_03_WHERE |
|_04_GROUP_BY |
|_05_HAVING |
|_06_ORDER_BY C_MFGEXECEVENTHISTORY~MANUFACTURINGORDER ASCENDING, C_MFGEXECEVENTH|
| ISTORY~EVENTDATETIME ASCENDING, C_MFGEXECEVENTHISTORY~SORTFIELD ASC|
| ENDING, C_MFGEXECEVENTHISTORY~MFGEXECDOCUMENTCATEGORY ASCENDING, C_|
| MFGEXECEVENTHISTORY~MANUFACTURINGEXECU... |
|_07_LIMIT 20 |
|_08_OFFSET 200 |
|_09_HINTS &SUPPORTS_FDA_PROT 0& |
|_10_LOCALE %_native( 'WITH PARAMETERS( ''LOCALE'' = ''EN'' )' ) |
----------------------------------------------------------------------------------------------------
|4 CX_SY_OPEN_SQL_DB |
|(Program) CL_SADL_SQL_EXECUTOR==========CP |
|(Include) CL_SADL_SQL_EXECUTOR==========CM00A |
|(Row) 71 |
|(Short Text) The database registered an internal error. SQL code 4. The error |
| text is: cannot allocate enough memory: please check traces for |
| further information. |
|IS_RESUMABLE |
|KERNEL_ERRID |
|SQLCODE 4 |
|SQLMSG cannot allocate enough memory: please check traces for further info|
| rmation |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Information on where terminated |
| The termination occurred in ABAP program or include |
| "CL_SADL_SHORTDUMP=============CP", in "TRIGGER_DATABASE_FAILURE_DUMP". The |
| main program was "SAPMHTTP". |
| |
| In the source code, the termination point is in line 2 of include |
| "CL_SADL_SHORTDUMP=============CM009". |
| include "CL_SADL_SHORTDUMP=============CM009". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Source Code Extract |
----------------------------------------------------------------------------------------------------
|Line |Code |
----------------------------------------------------------------------------------------------------
| 1| METHOD trigger_database_failure_dump. |
|>>>>>| DATA(_) = COND i( WHEN mv_aunit_exc_instead_of_dump <> abap_true THEN |
| 3| THROW SHORTDUMP cx_sadl_dump_database_failure( io_error ) |
| 4|"######################################################################################## |
| 5|"# !!! ATTENTION !!! # |
| 6|"# Before opening a ticket, check if you can resolve the issue yourself: # |
| 7|"# Refer to the "Chain of Exception Objects" section of this dump ("Long text" tab in # |
| 8|"# ADT or if viewed in SAP GUI (transaction ST22) in "ABAP Developer View"). # |
| 9|"# Therein a human-readable representation of the executed SQL and the error which it # |
| 10|"# caused may indicate issues with the service modeling and/or implementation. # |
| 11|"# # |
| 12|"# If you believe the application modeling to be correct after this evaluation please # |
| 13|"# create an incident for the appropriate component (either the database or SADL) and # |
| 14|"# attach a full export of this dump and a description of your scenario. Thank you! # |
| 15|"######################################################################################## |
| 16| ELSE THROW RESUMABLE cx_sadl_dump_database_failure( io_error ) ). "<- for unit tests on|
| 17| ENDMETHOD. |
----------------------------------------------------------------------------------------------------
Read more...
Product
Keywords
KBA , HAN-DB , SAP HANA Database , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)