SAP Knowledge Base Article - Preview

2913707 - Dump DBSQL_STMNT_TOO_LARGE is generated

Symptom

The following ST22 dump is generated daily in the Solution Manager system:

Category ABAP Programming Error
Runtime Errors DBSQL_STMNT_TOO_LARGE
Except. CX_SY_OPEN_SQL_DB
ABAP Program CL_0SMD_HK====================CP
Application Component SV-SMG-DIA

Short Text
   Der Open SQL command is too big.

What happened?
   Error in the ABAP Application Program

   The current ABAP program "CL_0SMD_HK====================CP" had to be
   terminated because it has
   come across a statement that unfortunately cannot be executed.

Error analysis
   An exception has occurred which is explained in more detail below. The
   exception is assigned to class 'CX_SY_OPEN_SQL_DB' and was not caught in
   procedure
   "GET_LASTPART" "(METHOD)", nor was it propagated by a RAISING clause.
   Since the caller of the procedure could not have anticipated this
   exception, the current program was terminated.

Source Code
   16 ENDLOOP.
   17
   18 * SELECT sid FROM /bi0/srequid APPENDING TABLE lt_sid WHERE requid IN lt_request_range. "#E
>>>>> SELECT sid FROM (p_tab) APPENDING TABLE lt_sid WHERE requid IN lt_request_range. "#EC CI_S
   20
   21 SORT lt_sid DESCENDING.

Active Calls/Events
   5 METHOD CL_0SMD_HK====================CP CL_0SMD_HK====================CM006 19
   CL_0SMD_HK=>GET_LASTPAR


Read more...

Environment

Solution Manager 7.2

Product

SAP Solution Manager 7.2

Keywords

 CCM, SQL, DBSQL_STMNT_TOO_LARGE, 2881175 , KBA , SV-SMG-CCM , Custom Code Management , 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.