DBIF_RSQL_INVALID_RSQL statement too big

Question

Hi All,
We are on SAP R/3 4.6C (kernel 46D 64 bit pacth 2113 with last DBLS library, AIX 5.2, DB2 7.1 on z/os 1.4) and for a BW extraction we have the following dump:
"ABAP runtime error DBIF_RSQL_INVALID_RSQL, RSQL error 13 occurred.
The following message also appears in the developer trace:
B *** ERROR => dbtran ERROR (set_input_da_spec): statement too big
B marker count = 1195 > max. marker count = 726."
For the OSS note 655018 the limit of marker count is 2000, but in the trace of work process we read 726.
Many thanks for your help
Bob

Answer 1

Hi Bernhard,
thak you for reply. This is the dump:
============================================================
ABAP runtime errors    DBIF_RSQL_INVALID_RSQL
       Occurred on     16.01.2008 at 10:29:04
RSQL error 13 when accessing table "EKKO ".
What happened?
The current ABAP/4 program "SAPDBERM " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
The SQL statement generated from SAP Open SQL violates a
restriction imposed by the database system used in R/3.
For details, refer to either the system log or the developer trace.
Possible reasons for error:
o Maximum size of an SQL statement exceeded.
o The statement contains too many input variables.
o The input data requires more space than is available.
o ...
You can usually find details in the system log (SM21) and in
the developer trace of the relevant work process (ST11).
In the event of an error, the developer trace often gives the
current restrictions.
How to correct the error
The SAP Open SQL statement concerned must be divided into several
smaller units.
If the problem occurred because an excessively large table was used
in an IN itab construct, you can use FOR ALL ENTRIES instead.
When you use this addition, the statement is split into smaller units
according to the restrictions of the database system used.
System environment
SAP Release.............. "46C"
Application server....... "R3PRD"
Network address.......... "172.24.10.50"
Operating system......... "AIX"
Release.................. "5.2"
Hardware type............ "00C7A3EC4C00"
Database server.......... "r3prddb_gb"
Database type............ "DB2"
Database name............ "PRD"
Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "46D"
Created on............... "Aug 25 2005 20:51:50"
Created in............... "AIX 1 5 00447C4A4C00"
Database version......... " "
Patch level.............. "2113"
Patch text............... " "
Supported environment....
Database................. "DB2 for OS/390 6.1"
SAP database version..... "46D"
Operating system......... "AIX 1 4, AIX 2 4, AIX 3 4, AIX 1 5, AIX 2 5, AIX 3
5, , System build information:, -
, LCHN :
775484"
User, transaction...
Client.............. 300
User................ "ALEREMOTE"
Language key........ "E"
Transaction......... " "
Program............. "SAPDBERM "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPDBERM " in
"PUT_EKKO".
The main program was "AQZZSYSTBWGENER0SY000000000361 ".
The termination occurred in line 333
of the source code of program "SAPDBERM " (when calling the editor 3330).
The program "SAPDBERM " was started as a background job.
Source code extract
003030   ENDFORM.
003040
003050   ----
003060   FORM PUT_EKKO.
003070
003080     CONSTANTS: LC_PACKAGE_SIZE LIKE SY-TFILL VALUE 10.
003090     DATA: BEGIN OF LT_SEKKO OCCURS 0,
003100             EBELN LIKE EKKO-EBELN,
003110           END OF LT_SEKKO.
003120     DATA: BEGIN OF LT_TEKKO OCCURS 0,
003130             EBELN LIKE EKKO-EBELN,
003140           END OF LT_TEKKO.
003150     DATA: L_INDEX_FROM LIKE SY-TABIX,
003160           L_INDEX_TO   LIKE SY-TABIX,
003170           L_EKPO_TABIX LIKE SY-TABIX.
003180     PERFORM KSCHL_SETZEN.
003190     ONEST = P_ONEST.
003200     TEST  = TESTLAUF.
003210     DB_DEL  = ' '.    "VETVG und Komponenten bleiben noch stehen
003220     DETPROT = P_PROT.
003230     ANDAT = ER_ANDAT.
003240     PERFORM AKTIVITAET_SETZEN(SAPFM06D) USING '06'.
003250     SELECT EBELN    FROM  EKKO INTO TABLE LT_SEKKO
003260       WHERE EBELN  IN ER_EBELN
003270         AND EKORG  IN ER_EKORG
003280         AND BSTYP  IN ER_BSTYP
003290         AND BEDAT  IN ER_BEDAT
003300         AND BSART  IN ER_BSART
003310         AND EKGRP  IN ER_EKGRP
003320   *   AND MEMORY NE 'X'
>         ORDER BY EBELN.
003340     L_INDEX_FROM = 1.
003350
003360     DO.
003370       REFRESH LT_TEKKO.
003380       L_INDEX_TO = L_INDEX_FROM + LC_PACKAGE_SIZE - 1.
003390       LOOP AT LT_SEKKO FROM L_INDEX_FROM
003400                        TO   L_INDEX_TO.
003410         APPEND LT_SEKKO TO LT_TEKKO.
003420       ENDLOOP.
003430       IF SY-SUBRC NE 0.
003440         EXIT.
003450       ENDIF.
003460       SELECT        * FROM  EKKO INTO TABLE XEKKO
003470         FOR ALL ENTRIES IN LT_TEKKO
003480              WHERE  EBELN  = LT_TEKKO-EBELN
003490         ORDER BY PRIMARY KEY.
003500       SELECT        * FROM  EKPO INTO TABLE XEKPO
003510         FOR ALL ENTRIES IN LT_TEKKO
003520              WHERE  EBELN  = LT_TEKKO-EBELN
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0                             SY-INDEX 0
SY-TABIX 1                             SY-DBCNT 152
SY-FDPOS 1                             SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1
============================================================
We have also installed the last kernel and the DBSL 2342.
Thank you and regards
Bob