DBIF_RSQL_SQL_ERROR

[Former Member]

Hi All,

I am facing this runtime error while running one of the custom programs to update status of workorders in SAP. I am totally clueless as why this is happening. Any help pls...

Dump:

Runtime errors DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

The database system detected a deadlock and avoided it by rolling back

your transaction.

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

"STATUS_UPDATE" "(FUNCTION)"

.

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.

How to correct the error

-

---

The exception must either be prevented, caught within the procedure

"STATUS_UPDATE"

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

To prevent the exception, note the following:

Database error text........: "ORA-00060: deadlock detected while waiting for

resource"

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

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

"SAPLBSVU" or "LBSVUU01"

"STATUS_UPDATE"

The termination occurred in the ABAP program "SAPLBSVU" in "STATUS_UPDATE".

The main program was "ZPM_MATAVAIL_CHK ".

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

program "LBSVUU01"

of the source code of program "LBSVUU01" (when calling the editor 1400).

Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in

the

procedure "STATUS_UPDATE" "(FUNCTION)" but was not handled locally, not

declared in the

RAISING clause of the procedure.

The procedure is in the program "SAPLBSVU ". Its source code starts in line 7

of the (Include) program "LBSVU$01 ".

[Former Member]

Or

Refer SAPNote- 84348 - Oracle deadlocks, ORA-00060 if the short dump persist.

[Former Member]

The short dump is generated due to "ZPM_MATAVAIL_CHK ". It is a Z program please sit with your Abap team to resolve it.

[Former Member]

Hi,

The fact that your customer program is generating

Database error text........: "ORA-00060: deadlock detected

when doing updates tends to point to a coding issue.

Not saying that other factors can also contribute to your issue but in my experience

there will be coding deficiencies when updating tables.

Pass this one back to your abapers for analysis.

Mark

[Former Member]

Hi,

I am also facing the same issue, better to know which table you are having problem and debug that program code. You can solve the problem.

[Former Member]

the table is JEST table. It has all the status of the work orders in it.

[sivakumar_kilari3]

Hi,

"The termination occurred in the ABAP program "SAPLBSVU" in "STATUS_UPDATE".

The main program was "ZPM_MATAVAIL_CHK ".

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

program "LBSVUU01"

You sit with your ABAPers and ask them to debug the program.

Regards

Siva

Edited by: Siva K Kumar on Mar 9, 2011 9:25 AM

[Former Member]

In debug the program does not give any runtime error for the same selection criteria!

[stefan_koehler]

Hello Kumar,

In debug the program does not give any runtime error for the same selection criteria!

well ... did you understand the problem at all? You can not figure it that kind of problem in a debugger.

At first you need to figure out, if that deadlock is caused by application or database (ITLs) itself. If you don't know howto identify - then check sapnote #84348 like already mentioned before.

If it is caused by application your developer should first think about the problem and how such a situation can be avoided ... if it is a database "issue" (ITL) ... check it and change it.

Regards

Stefan