2078286 - Dump DBSQL_STMNT_TOO_LARGE, Number of DBSL marker exceeded

Dump DBSQL_STMNT_TOO_LARGE occurs while accessing tables (especially large tables with huge number of entries, such as BSEG) using transaction SE16, for example:

In section "Error analysis" of the dump, the following (or similar) can be found:

| Number of DBSL marker exceeded |
| Current = 45687 |
| "Maximum = 32767"

In the devlopper traces the following can be found  :

C *** ERROR => too many input values (<...>) - maximum is 32767
B ***LOG BYK=> current SQL statement exceeds a database limit

Important! The solution in this document is for dump DBSQL_STMNT_TOO_LARGE with error 'Number of DBSL marker exceeded', however it can also be used for the other type of errors when the dump name is DBIF_RSQL_INVALID_RSQL or DBIF_RSQL_INVALID_REQUEST. Since all these dumps mean that the SQL statement came across a restriction of the database system.

SAP NetWeaver release independent.

statement too big, no. of entries, SE16, DBIF_RSQL_INVALID_RSQL, DBIF_RSQL_INVALID_REQUEST, DBSQL_STMNT_TOO_LARGE, /1BCDWB/, marker ,Open SQL command is too big , KBA , BC-DB-DBI , DB Independent Database Interface , BC-DWB-UTL-BRD , Data Browser , Problem