Runtime Error DBIF_RSQL_SQL_ERROR

Former Member — Thu, 10 Jan 2008 05:58:42 GMT

Hi Gurus !

i m getting this dump .

Exception CX_SY_OPEN_SQL_DB

Occurred on 09.01.2008 at 10:59:31

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

"OPNSELDATA"

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

To prevent the exception, note the following:

Database error text........: "ORA-01555: snapshot too old: rollback segment

number 13 with name "PRS_11" too small"

Internal call code.........: "[RSQL/FTCH/VBAK ]"

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

"ZVR04_PEND_SALES " or "ZVR04_PEND_SALES "

"OPNSELDATA"

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

and select the "Print" function to print out the relevant

part.

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

System environment

SAP Release.............. "620"

Information on where terminated

The termination occurred in the ABAP program "ZVR04_PEND_SALES " in

"OPNSELDATA".

The main program was "ZVR04_PEND_SALES ".

The termination occurred in line 661 of the source code of the (Include)

program "ZVR04_PEND_SALES "

of the source code of program "ZVR04_PEND_SALES " (when calling the editor

6610).

The program "ZVR04_PEND_SALES " was started as a background job.

Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in

the

procedure "OPNSELDATA" "(FORM)" but was not handled locally, not declared in

the

RAISING clause of the procedure.

The procedure is in the program "ZVR04_PEND_SALES ". Its source code starts in

line 659

of the (Include) program "ZVR04_PEND_SALES ".

Source code extract

006310 IT_ITAB-BQTY = IT_ITAB-KWMENG - IT_ITAB-OLFIMG - IT_ITAB-DTLFIMG.

006320 ENDIF.

006330

006340 IF IT_ITAB-VKORG = 'IC00'.

006350 IF IT_ITAB-VBELN NE ' '.

006360 IF IT_ITAB-OLFIMG GT 0 OR IT_ITAB-BQTY GT 5 .

006370 APPEND IT_ITAB.

006380 CLEAR IT_ITAB.

006390 ENDIF.

006400 ENDIF.

006410 ELSE.

006420 IF IT_ITAB-VBELN NE ' '.

006430 IF IT_ITAB-OLFIMG GT 0 OR IT_ITAB-BQTY GT 0 .

006440 APPEND IT_ITAB.

006450 CLEAR IT_ITAB.

006460 ENDIF.

006470 ENDIF.

006480 ENDIF.

006490

006500 ENDSELECT.

006510 SORT IT_ITAB BY VBELN.

006520 ENDFORM. "BLKSELDATA

006530

006540 *& *

006550 *& Form OPNSELDATA

006560 *& *

006570 * text

006580 * *

006590 FORM OPNSELDATA.

006600

> SELECT A_{VBELN A}ERDAT A_{AUART A}KNUMV A_{VKORG B}MATNR B_{KWMENG B}UMZI

006620 INTO (IT_ITAB-VBELN, IT_ITAB-ERDAT, IT_ITAB-AUART, IT_ITAB-KNUMV,

006630 IT_ITAB-VKORG, IT_ITAB-MATNR, IT_ITAB-KWMENG, IT_ITAB-UMZIZ, IT_

006640 FROM ( VBAK AS A INNER JOIN VBAP AS B

006650 ON A_{VBELN = B}VBELN INNER JOIN VBUK AS C

006660 ON C_{VBELN = B}VBELN )

006670 WHERE A~VKORG IN SO_VKORG

006680 AND A~VKBUR IN SO_VKBUR

006690 AND A~KUNNR IN SO_KUNNR

006700 AND A~ERDAT IN SO_ERDAT

006710 AND A~AUART IN SO_AUART

006720 AND A~VTWEG IN SO_VTWEG

006730 AND B~WERKS IN SO_WERKS

006740 AND B~MATNR IN SO_MATNR

006750 AND B~ABGRU = ' '

006760 AND C~FSSTK = ' '

006770 AND C~LSSTK = ' '

006780 AND C~SPSTG = ' '

006790 AND A~AUART <> 'ZDSO'

006800 AND A~AUART <> 'ZTSO'

Re: Runtime Error DBIF_RSQL_SQL_ERROR

Former Member — Thu, 10 Jan 2008 06:01:21 GMT

Hi,

Hope you got this error during Debugging. It Occurs during debugging when there is a commit work statement in 4.6c Version. Please let me know the scenario.

Regards,

Sai

Re: Runtime Error DBIF_RSQL_SQL_ERROR

Former Member — Thu, 10 Jan 2008 06:07:06 GMT

no , this dumb occurs when it is run in background as it takes more than 10 hrs.

Re: Runtime Error DBIF_RSQL_SQL_ERROR

Former Member — Thu, 10 Jan 2008 06:23:21 GMT

Is your Backend MaxDB. Please let me know because If you use MaxDB 7.6.00 or 7.6.01, deactivate the shared SQL. You can

also deactivate the shared SQL online as follows:

dbmcli -d <database name> -u <dbm user>,<dbm-password>

param_put -running -permanent SHAREDSQL NO

The setting is only valid for newly opened database sessions. Sessions

that already exist continue to work with shared SQL.

SELECTs with UNION can result in the "AK Catalog information not found"

error with MaxDB 7.6.00 and 7.6.01 if shared SQL is activated.

Please let me know if this works.

Regards,

Sai

Re: Runtime Error DBIF_RSQL_SQL_ERROR

former_member386202 — Thu, 10 Jan 2008 06:26:16 GMT

Hi,

Its a BASIS problem, basis guys has to increase roll area memory. Tell them to do that.

Regards,

PRashant

topic Re: Runtime Error DBIF_RSQL_SQL_ERROR in Application Development and Automation Discussions

Runtime Error DBIF_RSQL_SQL_ERROR

Re: Runtime Error DBIF_RSQL_SQL_ERROR

Re: Runtime Error DBIF_RSQL_SQL_ERROR

Re: Runtime Error DBIF_RSQL_SQL_ERROR

Re: Runtime Error DBIF_RSQL_SQL_ERROR