Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

About DUMP: DBIF_RSQL_SQL_ERROR

Hii Expert ,

I am facing  below issue while trying to export client.   SQL Error Dump : DBIF_RSQL_SQL_ERROR

Exception              CX_SY_OPEN_SQL_DB


Short text

    SQL error in the database when accessing a table.

What can you do?

    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.

How to correct the error

    Database error text........: "[601] Could not continue scan with NOLOCK due to

     data movement."

    Internal call code.........: "[RSQL/COUN/AFFH ]"

    Please check the entries in the system log (Transaction SM21).

    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_SQL_ERROR" "CX_SY_OPEN_SQL_DB"

    "RSSPACECHECK" or "RSSPACECHECK"

    "GET_TABLE_SIZE"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

   To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

   Display the system log by calling transaction SM21.

   Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

   In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

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

RAISING clause of the procedure.

To prevent the exception, note the following:

Regards

Dhananjay patil

Former Member
Not what you were looking for? View more on this topic or Ask a question