DBIF_RSQL_INVALID_RSQL

[Former Member]

Dear all,

AIX , Oracle 10.2.0.4 , Ecc6.0

We are facing error ABAP Dump as DBIF_RSQL_INVALID_RSQL . Kindly check the below logs .

Runtime Errors DBIF_RSQL_INVALID_RSQL

Exception CX_SY_OPEN_SQL_DB

Date and Time 13.09.2010 12:52:01

Short text

Error in module RSQL of the database interface.

What happened?

Error in the ABAP Application Program

The current ABAP program "ZSD_SALES_REPORT" had to be terminated because it ha

come across a statement that unfortunately cannot be executed.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

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

in

procedure "POPULATE_TABLE" "(FORM)", nor was it propagated by a RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

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.

How to correct the error

The SAP Open SQL statement concerned must be divided into several

smaller units.

If the problem occurred due to the use of an excessively large table

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.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DBIF_RSQL_INVALID_RSQL" "CX_SY_OPEN_SQL_DB"

"ZSD_SALES_REPORT" or "ZSD_SALES_REPORT"

"POPULATE_TABLE"

The exception must either be prevented, caught within proedure

"POPULATE_TABLE" "(FORM)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

Kindly suggest

[Former Member]

HI Satheesh,

As suggested by Eric could you please modify your select query where the termination occurs.

[Former Member]

Dear Satheesh,

The issue seems to be with the custom program ZSD_SALES_REPORT. For this type of issues I'd check with the ABAP developer who can debug the program.

Regards,

Varadharajan M

[former_member204746]

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.

It looks like the generated SQL request is too long.

This can be caused by too many selections by the user, or, by poor programming. in Both Cases, this is not really a BASIS issue.

ask your programmer to check this out.