Error saying "Error in the module RSQL accessing the database interface"

[Former Member]

Hi,

there is a standard program available for retrieving the assets for the given cost centres on the selection screen.

Our requirement is instead of cost centre we have to retrieve the assets for the given cost centre group.

We have to find all the cost centres available on the given cost centre group and its child nodes.

For all these cost centres we will be retriving the asset history data.

So we copied the standard program into another Y program and made the changes to it.

What's happening is if we give the top most Cose centre group node there are 16000 cost centres available . while retriving the asset history data for all these cost centres an runtime error occurs in a standard program saying

"Error in the module RSQL accessing the database interface, " DBIF_RSQL_INVALID_RSQL ".

The error occurs while executing the statement Fetch Next cursor in a standard Include program.

<b>This happens only if we give huge range of data. If we give small range of data it

works fine</b>.

Can anyone help me in this by saying why it occurs and what will be the solution for this.

Thanks.

[Former Member]

Hi,

one of the Select statment is taking long time than the normal time, then only we get this type of DUMP, so ask your basis people to increase the time .. or give the Smal amount of data or do the performance tuning

Regards

Sudheer

[Former Member]

This generally happens when the tablespace (usually PSAPBTABD) is filled up. Ask your basis team to increase the space in it. It could also be the index problem with PSAPBTABI. Again your basis can increase the index.

- Cheers

[Former Member]

What happens is that SAP passes the query as a string from R3 to the database interface, if this is too large you get a dump along the lines of "Statement is too long or too complex". The interface runs out of memory and is unable to convert it into a SQL query on the database platform.

Whilst your BASIS/DBA team can increase this parameter, you've essentially got a SQL statement with at least 16,000 lines of where statement, so you'll need to rewrite the statement to do it slightly differently.

[Former Member]

In addition to DBIF_RSQL_INVALID_RSQL, there should be a specific error message and/or code issued by the database. Would you post that as well please?

Rob

[Clemenss]

Hi camila,

The huge range is part of the query string passed to the database.

While an MP3 music gadget easily stores a gigabyte of data, ORACLE was able to increase the maxium size of a query string from 16 k to 32 k bytes in the last 5 years.

<b>Unbelievable but true!</b>

Just multiply the number of entries in the range with the field length and see where go go...

Regards,

Clemens