DBIF_RSQL_INVALID_RSQL error

[Former Member]

Hi Experts,

Yesterday we were facing run time errors on one of the application server " DBIF_RSQL_INVALID_RSQL error". When we saw some process were running in SM50 which was taking almost 90% CPU and 50% RAM. We have some Z-development which is running on that server. But we are using that Z-development from last 1 Years. We didn't face this kind of issue still now.

After restarting the Application server the run time error has stopped coming as it has given almost 380 run time errors within 2 hours.

I would like to know the reason the run time has occurred. how to avoid this kind of runtime errors in future.

Regards,

Amit

[markus_doehr2]

> Yesterday we were facing run time errors on one of the application server " DBIF_RSQL_INVALID_RSQL error".

Please post the first two pages of the dump here, otherwise we can just "guess".

Markus

[Former Member]

Hi Markus,

After we updated latest kernal we have started this error.

Runtime Errors DBIF_RSQL_INVALID_RSQL

Exception CX_SY_OPEN_SQL_DB

Date and Time 26.04.2010 17:14:21

Short text

Error in module RSQL of the database interface.

What happened?

Error in the ABAP Application Program

The current ABAP program "RADBTDDF" had to be terminated because it has

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 "SE_DD02L_TABNAME_TABNAME" "(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"

"RADBTDDF" or "RADBTDDF"

"SE_DD02L_TABNAME_TABNAME"

The exception must either be prevented, caught within proedure

"SE_DD02L_TABNAME_TABNAME" "(FORM)", or its possible occurrence must be

declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

System environment

SAP-Release 700

Application server... "pagedq"

Network address...... "132.147.160.247"

Operating system..... "Linux"

Release.............. "2.6.16.60-0.21-defau"

Hardware type........ "ia64"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 4

Shortdump setting.... "full"

Database server... "pagep1"

Database type..... "ORACLE"

Database name..... "PIP"

Database user ID.. "SAPSR3"

Terminal................. "BOM-Barcode2"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Dec 14 2009 20:23:20"

create on........ "Linux GNU SLES-9 ia64 cc3.3.3"

Database version. "OCI_102 (10.2.0.1.0) "

[markus_doehr2]

> 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.

The reason is, that the generated statement is too big.

Check the tracefile dev_w4 for the statement.

Markus

[Former Member]

Hi Amit

Can you check your tablespaces, this can happen when one of your table spaces is full, you will have to extend them. Also check if you still have space on your Oracle partiton, otherwise you will have to free some space.

i hope this helps.

Regards

Partson

[Former Member]

There could be multiple reasons for occurring this error.. Check the sap system log, database log, dev_ traces in work directory.

Kind regards,

Mark

[Former Member]

Hi Amit,

If you search sap notes with keyword "DBIF_RSQL_INVALID_RSQL", you will get several hits.

You can then read the notes which are relevant to your problem and try to get the clue.

Mainly this error comes when invalid parameter is passed to the database.

Regards.

Rajesh Narkhede