Skip to Content
avatar image
Former Member

ABAP/4 processor: DBIF_RSQL_SQL_ERROR

Hi All,

I have scheduled a job in background.The job is taking a very long time than usual to process.After processing for around 5000 sec's the job is getting cancelled.Upon checking the job log it is found that the job is cancelled with the following error "ABAP/4 processor: DBIF_RSQL_SQL_ERROR " .

The bottleneck of the code is found at a select query retrieving all the records from a std.table.

Is there any way to solve this problem without changing the program now? Does this happen when the server is busy ?

SELECT BVBELN BPOSNR AFKART AKUNAG AKUNRG AERDAT B~MATNR

BPMATN BPRSDT BARKTX BFKIMG BMEINS BNETWR B~MWSBP

BABRBG BFBUDA BPRODH BAUBEL B~AUPOS

INTO TABLE I_VBRP

FROM VBRK AS A

INNER JOIN VBRP AS B

ON AVBELN = BVBELN

FOR ALL ENTRIES IN I_FINAL

WHERE ( B~AUBEL = I_FINAL-VBELN AND

B~AUPOS = I_FINAL-POSNR ) AND

A~ERDAT >= '20070101'.

IF SY-SUBRC EQ 0.

SORT I_VBRP BY VBELN POSNR ERDAT..

Kindly Advise.

Thanks.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Oct 28, 2008 at 01:23 PM

    DBIF_RSQL_SQL_ERROR can have many causes. What does the dump say in section "error analysis"? Any database-specific error code mentioned? E.g. ORA-xxxxx

    Thomas

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Thomas Zloch

      Hi Thomas,

      I am getting same error when archieving IDOCs,error is coming in the FM "ARCHIVE_GET_NEXT_OBJECT" while updating ADMI_STATS table.

      Please find the error analysis below.

      An exception occurred. This exception is dealt with in more detail below

      . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was

      neither

      caught nor passed along using a RAISING clause, in the procedure

      "UPDATE_ADMI_STATS" "(FORM)"

      .

      Since the caller of the procedure could not have expected this exception

      to occur, the running program was terminated.

      The reason for the exception is:

      How to correct the error

      The exception must either be prevented, caught within the procedure

      "UPDATE_ADMI_STATS"

      "(FORM)", or declared in the procedure's RAISING clause.

      To prevent the exception, note the following:

      Database error text........: "[8115] Arithmetic overflow error converting

      expression to data type int.#[3621] The statement has been terminated."

      Internal call code.........: "[RSQL/UPDT/ADMI_STATS ]"

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

      You may able to find an interim solution to the problem

      in the SAP note system. If you have access to the note system yourself,

      use the following search criteria:

      -


      "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC

      "SAPLARCH" or "LARCHF06"

      "UPDATE_ADMI_STATS"

      -


      Could you please thorugh some light how to correct error..

  • avatar image
    Former Member
    Oct 28, 2008 at 01:35 PM

    It appears to be a memory issue. Try reducing the a mount of data being processed.

    Rob

    Add comment
    10|10000 characters needed characters exceeded