cancel
Showing results for 
Search instead for 
Did you mean: 

DBIF_RSQL_INVALID_RSQL - RSQL error 13

Former Member
0 Kudos

Hello,

We are getting ABAP DUMP - DBIF_RSQL_INVALID_RSQL in our system.. We

have migrated from informix to oracle on Test server...

Kindly see error and suggest:

RSQL error 13 when accessing table "PA0001 ".

What happened?

The current ABAP/4 program "ZTIME_MUSTER " had to be terminated becaus

one of the statements could not be executed.

This is probably due to an error in the ABAP/4 program.

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your

SAP system administrator.

You can print this message by choosing "Print".

Transaction ST22 allows you to display and manage short dumps. It

is especially useful if you want to keep a particular message.

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.

-

If the error occurred in a non-modified SAP program, you may be

able to find a solution in the SAP note system.

If you have access to the note system yourself, use the following

search criteria:

"DBIF_RSQL_INVALID_RSQL"

"ZTIME_MUSTER " bzw. "ZTIME_MUSTER "

"DATA_EXTRACT"

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

-

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

-


Thanks,

RaHuL...

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

> RSQL error 13 when accessing table "PA0001 ".

>

>

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

What most likely happened is, that some used a multi-selection with too many single values. The generated SQL statement is exceeding the maximum size and thus you get the error.

This error can only be worked around by using less single selections.

Markus

Former Member
0 Kudos

Hello,

Thanks for the replies...

Markus,

As i mentioned we have migrated from Informix to Oracle... The problem i am referring to is in one of the many programs that we have run in informix environment... If we go by what you suggest all the Programs or may be quite a few [not all are tested] in which we get error will have to be changed... Is there anything we can check?

Shaji,

Thanks for the suggestion.. I will check the parameter, increase it if its less ,restart SAP and then get back again with the STATUS...

Thanks,

RaHuL...

former_member185954
Active Contributor
0 Kudos

Rahul,

there might be some hard coded EXEC SQL statements which may work on Informix , but not on Oracle.

You need to check if the SQL query that throws error has valid syntax in Oracle.

Regards,

Siddhesh

0 Kudos

Hello,

Most is already indicated.

Unfortunatelly, to know the exact error you should check not only the short dump.

Full information is on the developer trace.

From the short dump you know the server and time

From the system log you will know the workprocess.

If you check the developer trace (dev_w<number>) for the workproces then you will find the statement and the exact error.

This will tell you the "limit" that has been exceeded.

The limits are different in each database, so it is possible that limit is smaller in oracle than in informix.

Knowing the exact error and the query, then you will have to adapt the source (perhaps a smaller in list or ... )

Note with all the details and perhaps a better explanation is 13607

There are also some cases where the error is on the kernel, not on the rogram. You should also check SAP notes, like 1044523, 876328 ...

Answers (3)

Answers (3)

Former Member
0 Kudos

If you search SAPNOTES for DBIF_RSQL_INVALID_RSQL you will find several notes added last week.

One of those notes may help you?

Former Member
0 Kudos

What is the SM21 log reporting ?

What is the size of abap/buffersize, try increasing it and restart SAP

former_member185954
Active Contributor
0 Kudos

Hello Rahul,

Can you post the actual SQL statement that you are executing ?

Regards,

Siddhesh