Runtime errors DBIF_RSQL_SQL_ERROR

[Former Member]

Hello Friends,

Please Help me solve this solve this issue.

Runtime errors DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

<<dump error message removed by moderator>>

Moderator Message: Instead of copy-pasting the entire dump message, tell us when and for what you got this dump.

Thanking You,

Rahul Asthana.

Edited by: kishan P on Aug 5, 2011 10:55 AM

[Former Member]

Hi,

A SQL operation on this table can not be performed is a generic conclusion.

You may also want to try running it again, also check with your Basis team which definitely helps.

Lastly, did you check if a record already exists in the table with the current entries?

Rgds,

Narendra.

[Former Member]

Hi Narendra,

I had already check all the fields in the table they all are existing in the table, and I am tiring to catch the exception also in the class "CX_SY_OPEN_SQL_DB" which I am not getting in program. Kindly Help me to solve this issue.

Thanking You,

Rahul Asthana

[Former Member]

Hello Krishan,

I am trying to update my table and the fields which i am using in updation are not a key but still it not updating and I am tring to catch the exception also in the class "CX_SY_OPEN_SQL_DB" which i am not getting in program, due to this reasons i mention the whole dump while posting my problem. kindly help me solve this issue.

Thanking You,

Rahul Asthana

[Former Member]

Hi Rahul,

Check whether a record already exists in the table with the current entries / check whether you are trying to update entries which are not yet available int he table.

Thanks

[Former Member]

Hi Friend,

I had already checked all the fields in the table they all are existing in the table, and I am tiring to catch the exception also in the class "CX_SY_OPEN_SQL_DB" which I am not getting in program. Kindly Help me to solve this issue.

Thanking You,

Rahul Asthana

[Former Member]

Hi,

The reason could be the workarea / itab being used in the UPDATE statement being processed did not match the line style of the DB table being updated.

Pl. Check & let me know, it's still not working

Regards,

S.Senthilkumar

[deepak_dhamat]

Hi Rahul Asthana

,

Please show us the structure of table you are updating

and also the update command

regards

Deepak.

[Former Member]

Hi,

I am sending you the whole error description with, update command.

One More thing i like to share with you that i am trying to search which exception is use while updating ibut i am not getting it. The name of the Class"CX_SY_OPEN_SQL_DB" .

KINLY HELP ME TO SOLVE THIS ISSUE.

Runtime errors DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

An SQL error occurred when accessing a table.

Error analysis

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

"PROCESS_RECORDS" "(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:

The database system recognized that your last operation on the database

would have led to a deadlock.

Therefore, your transaction was rolled back

to avoid this.

ORACLE always terminates any transaction that would result in deadlock.

The other transactions involved in this potential deadlock

are not affected by the termination.

Information on where terminated

The termination occurred in the ABAP program "ZNRD_SABRE_RECON" in

"PROCESS_RECORDS".

The main program was "ZNRD_SABRE_RECON ".

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

program "ZNRD_SABRE_RECON"

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

1990).

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

Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in

the

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

in the

RAISING clause of the procedure.

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

line 160

of the (Include) program "ZNRD_SABRE_RECON ".

Source code extract

001690 concatenate 'Message from' sy-sysid ' - SABRE RECON - Check It'

001700 into l_obj_hd-objdes

001710 separated by Space.

001720 * End of changes

001730 * *

001740 l_obj_hd-objsns = '0'.

001750

001760 DATA: order_complete(1) TYPE c.

001770

001780 SORT rect03 BY r03_ordnum.

001790

001800 LOOP AT rect03.

001810 CONCATENATE '000' rect03-r03_ordnum INTO poforselect.

001820 SELECT SINGLE * FROM znrd_order WHERE ebeln = poforselect.

001830 IF sy-subrc = 0.

001840 SELECT SINGLE * FROM znrd_orddetail WHERE ebeln = poforselect AND

001850 fwdmatnr = rect03-r03_ordpart.

001860 * Update ZNRD_ORDDETAIL irrespective of Progress Qty.

001870

001880 IF sy-subrc = 0.

001890 * *

001900 * Commented by Vinod on 15/03/2004 for SR: 109234

001910 ** Addition By Atul Gupta 13.01.2004

001920 * PERFORM lock.

001930 ** End of Addition by Atul 13.01.2004

001940 * *

001950 znrd_orddetail-allocqty = rect03-r03_alcqty.

001960 znrd_orddetail-duesoqty = rect03-r03_dueqty.

001970 znrd_orddetail-username = sy-uname.

001980 znrd_orddetail-userdate = sy-datum.

-

---

> UPDATE znrd_orddetail.

002000

002010 * *

002020 * Commented by Vinod on 15/03/2004 for SR: 109234

002030 ** Addition By Atul Gupta 13.01.2004

002040 * PERFORM unlock.

002050 ** End of Addition by Atul 13.01.2004

002060 * *

002070 ELSE.

002080 CONCATENATE 'PO, NOT PRESENT IN ZNRD-ORDER' ':' poforselect ':'

002090 'MATERIAL' ':' rect03-r03_ordpart

002100 INTO l_obj-line.

002110 APPEND l_obj.

002120 CLEAR l_obj.

002130 ENDIF.

002140

002150 ELSE. "DOESN'T EXIST IN ZNRD_ORDER

002160

002170 CONCATENATE 'PO, NOT PRESENT IN ZNRD-ORDER' ':' poforselect

002180 INTO l_obj-line.