cancel
Showing results for 
Search instead for 
Did you mean: 

LO Extraction Setup job OLI7BW fails woth SQL error

Former Member
0 Kudos

I am setting up the setup tables in my QA-R/3. We are doing this after the R/3 QA is recently refreshed with PROD data. Any help is appreciated.

Here is my short dump.

ABAP runtime errors DBIF_RSQL_INVALID_REQUEST

Invalid database interface call in the statement where table "KONV " is

The current ABAP/4 program terminated due to

an internal error in the database interface.

An invalid request was made to the internal SAP database interface

when accessing table "KONV ".

Information on where termination occurred

The termination occurred in the ABAP/4 program "RMCVNEAV2 " in

"READ_PACKAGE_OF_DOCUMENTS".

The main program was "RMCVNEAV2 ".

The termination occurred in line 334

of the source code of program "RMCVNEAV2 " (when calling the editor 3340).

The program "RMCVNEAV2 " was started as a background job.

003280

003290 * read KONV

003300 IF cnt_knumv > 0.

003310 SELECT * INTO TABLE gt_konvn

003320 FROM konv

003330 WHERE knumv IN l_knumv

> ORDER BY PRIMARY KEY.

003350 ENDIF.

<u>SM21 has the following messages</u>

BY0 > cluster: KOCLU key: 220*0001019484

BZW Error EOSDE during compression/decompression (COM c2_co)

R68Performrollback

AB0 Run-time error "DBIF_RSQL_INVALID_REQUEST" occurred

AB1 > Short dump "060426 005604 ftlqsapq C_GOPIE " generated

D01 Transaction termination 00 671 ( DBIF_RSQL_INVALID_REQUEST 20060426005604 00:56:06 BTC 02 R68 Perform

rollback

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

what is the message in the short dump? It might be an issue with your range tab i_knumv. It might contain too many entries. If this is the case, you will see something like 'statement too large' in the short dump.

Please let us know more details.

regards

Siggi

Former Member
0 Kudos

ABAP runtime errors DBIF_RSQL_INVALID_REQUEST

Occurred on 04/26/2006 at 00:56:04

>> Short dump has not been completely stored. It is too big.

Invalid database interface call in the statement where table "KONV " is

What happened?

The current ABAP/4 program terminated due to

an internal error in the database interface.

Former Member
0 Kudos

Hi,

well I guess you need to check that issue with a basis or database person.

Siggi