Symptom
The dump DBSQL_STMNT_TOO_LARGE occurs. Detail logs can be found in the transaction ST22:
Category | ABAP Programming Error |
Runtime Errors | DBSQL_STMNT_TOO_LARGE |
Except. | CX_SY_OPEN_SQL_DB |
ABAP Program | SAPF111S |
Application Component | FI-BL-PT-AP |
In session "short text" of the dump, the following (or similar) can be found:
Der Open SQL command is too big.
More information: Table = PAYRQ Number of DBSL tokens exceeded
Current = 70415
"Maximum = 65535"
In the developers trace, below error occurs:
B DbSqlDbslStmtDesc::getDbslStmt(): Number of DBSL tokens 70415 exceeds maximal number 65535
B Dumping token list ...
Important! The solution in this document is for dump DBSQL_STMNT_TOO_LARGE with error 'Number of DBSL tokens exceeded', however it can also be used for the other type of errors when the dump name is DBSQL_STMNT_TOO_LARGE, DBIF_RSQL_INVALID_REQUEST or DBIF_RSQL_INVALID_RSQL or SAPSQL_STMNT_TOO_LARGE. Since all these dumps mean that the SQL statement came across a restriction of the database system.
Read more...
Environment
SAP NetWeaver Release independent.
Product
Keywords
DBIF_RSQL_INVALID_RSQL, DBIF_RSQL_INVALID_REQUEST, DBSQL_STMNT_TOO_LARGE, Dump, Der Open SQL Command is too big, PAYRQ, Tokens, DBSL, ST22, Dump Analysis, CX_SY_OPEN_SQL_DB , KBA , BC-DB-DBI , DB Independent Database Interface , 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.