Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

DBIF_RSQL_INVALID_RSQL The maximum size of an SQL statement was exceeded

Dear,

I would appreciate a helping hand

I have a problem with a dump I could not find any note that I can help solve the problem.

A dump is appearing at various consultants which indicates the following.

>>> SELECT * FROM KNA1 "client specified

559 APPENDING TABLE IKNA1

560 UP TO RSEUMOD-TBMAXSEL ROWS BYPASSING BUFFER

ST22

What happened?

Error in the ABAP Application Program

The current ABAP program "/1BCDWB/DBKNA1" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

and

therefore caused a runtime error.

The reason for the exception is:

The SQL statement generated from the SAP Open SQL statement violates a

restriction imposed by the underlying database system of the ABAP

system.

Possible error causes:

o The maximum size of an SQL statement was exceeded.

o The statement contains too many input variables.

o The input data requires more space than is available.

o ...

You can generally find details in the system log (SM21) and in the

developer trace of the relevant work process (ST11).

In the case of an error, current restrictions are frequently displayed

in the developer trace.

SQL sentence

550 if not %_l_lines is initial.

551 %_TAB2[] = %_tab2_field[].

552 endif.

553 endif.

554 ENDIF.

555 CASE ACTION.

556 WHEN 'ANZE'.

557 try.

>>> SELECT * FROM KNA1 "client specified

559 APPENDING TABLE IKNA1

560 UP TO RSEUMOD-TBMAXSEL ROWS BYPASSING BUFFER

561 WHERE KUNNR IN I1

562 AND NAME1 IN I2

563 AND ANRED IN I3

564 AND ERDAT IN I4

565 AND ERNAM IN I5

566 AND KTOKD IN I6

567 AND STCD1 IN I7

568 AND VBUND IN I8

569 AND J_3GETYP IN I9

570 AND J_3GAGDUMI IN I10

571 AND KOKRS IN I11.

572

573 CATCH CX_SY_DYNAMIC_OSQL_SEMANTICS INTO xref.

574 IF xref->kernel_errid = 'SAPSQL_ESCAPE_WITH_POOLTABLE'.

575 message i412(mo).

576 exit.

577 ELSE.

wp trace:

D *** ERROR => dySaveDataBindingValue: Abap-Field= >TEXT-SYS< not found [dypbdatab.c 510]

D *** ERROR => dySaveDataBindingEntry: dySaveDataBindingValue() Rc=-1 Reference= >TEXT-SYS< [dypbdatab.c 430]

D *** ERROR => dySaveDataBinding: dySaveDataBindingEntry() Rc= -1 Reference=>TEXT-SYS< [dypbdatab.c 137]

Y *** ERROR => dyPbSaveDataBindingForField: dySaveDataBinding() Rc= 1 [dypropbag.c 641]

Y *** ERROR => ... Dynpro-Field= >DISPLAY_SY_SUBRC_TEXT< [dypropbag.c 642]

Y *** ERROR => ... Dynpro= >SAPLSTPDA_CARRIER< >0700< [dypropbag.c 643]

D *** ERROR => dySaveDataBindingValue: Abap-Field= >TEXT-SYS< not found [dypbdatab.c 510]

D *** ERROR => dySaveDataBindingEntry: dySaveDataBindingValue() Rc=-1 Reference= >TEXT-SYS< [dypbdatab.c 430]

D *** ERROR => dySaveDataBinding: dySaveDataBindingEntry() Rc= -1 Reference=>TEXT-SYS< [dypbdatab.c 137]

Y *** ERROR => dyPbSaveDataBindingForField: dySaveDataBinding() Rc= 1 [dypropbag.c 641]

Y *** ERROR => ... Dynpro-Field= >DISPLAY_FREE_VAR_TEXT< [dypropbag.c 642]

Y *** ERROR => ... Dynpro= >SAPLSTPDA_CARRIER< >0700< [dypropbag.c 643]

I thank you in advance

If you require other information please request

Former Member
Not what you were looking for? View more on this topic or Ask a question