DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC

[Former Member]

Hi All,

I got a couple of dumps DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC in BW production.

Below is the screen shot.

How to correct the error

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

resource"

Internal call code.........: "[RSQL/INSR//BIC/FZSDGL ]"

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

"GP3WBSX71P2XVNPZ488HSACPEL5" or "GP3WBSX71P2XVNPZ488HSACPEL5"

"WRITE_ICFACT"

Pls help to resolve the issue.

Regards,

Kris

Edited by: raama krishna on Apr 1, 2008 10:55 PM

[Former Member]

Please check note 1513323

Regards,

Todor

[deidre_logan]

hello there,

Were you able to fix your Ora-00060 error.

We are getting the same error in our BW system loading the DSO.

I do not have any trace files in the /oracle/SID/saptrace/usertrace or /oracle/SID/saptrace/background for the deadlocks I had today.

I have many ST22 dumps with the abend DBIF_RSQL_SQL_ERROR

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

resource"

Internal call code.........: "RSQL/UPDT//BIC/AZMM_DCTA00 "

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"

"GP4IFW9RVCLI3JLR38BWM5IPOZR" or "GP4IFW9RVCLI3JLR38BWM5IPOZR"

"PROCESS_BUFFER_TABLES"

thanks for your guidance.

[former_member184473]

Hello,

If you check the alert.log during the time you faced the deadlock you can find the deadlock trace file name and location.

Regards,

Eduardo Rezende

[antonio_voce]

remember reward points and close the question!

Antonio Voce.

[Former Member]

Hi,

check Note 631668 - DEADLOCK when loading data into InfoCubes

regards,

kaushal

[Former Member]

Raama,

This is the forum for SQL Sever and you have an Oracle issue but anyway - the issue was a deadlock. You should have a file in the oracle directory that will let you know the processes that were involved and what they were trying to do.

Overall a deadlock is a situation where Oracle has determined that no matter what, the processes will not complete due to competing locks between two processes. Oracle determines the winner and rolls-back the failed process and allows the winner to continue forward. Oracle will also write a trace dump for the deadlock in the background trace file in the Oracle directory.

It is not uncommon for this to occur with tables like NRIV (number ranges) where buffering needs to be addressed to keep this from occuring again.

If this answers your questions, please set this thread to answered, if not, please provide your additional requirements so we can address your issues promptly.

[Former Member]

Hi David Milliken ,

Thanx for the response. I didnt find any deadlocks in DB01 or in ST04.

Here I am attaching the trace of the deadlock which has been generated at OS level.

Dump file /oracle/BWP/saptrace/usertrace/bwp_ora_8567.trc

Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production

With the Partitioning and Data Mining options

ORACLE_HOME = /oracle/BWP/102_64

System name: SunOS

Node name: jazzsap5

Release: 5.10

Version: Generic_120011-14

Machine: sun4u

Instance name: BWP

Redo thread mounted by this instance: 1

Oracle process number: 21

Unix process pid: 8567, image: oracleBWP@jazzsap5

• 2008-03-30 03:00:49.177

• ACTION NAME:(6934) 2008-03-30 03:00:49.137

• MODULE NAME:(GP3WBSX71P2XVNPZ488HSACPEL5 ) 2008-03-30 03:00:49.137

• SERVICE NAME:(BWP) 2008-03-30 03:00:49.137

• SESSION ID:(217.7) 2008-03-30 03:00:49.137

DEADLOCK DETECTED

[Transaction Deadlock]

Current SQL statement for this session:

INSERT INTO "/BIC/FZSDGL" VALUES( :A0 , :A1 , :A2 , :A3 , :A4 , :A5 , :A6 , :A7 , :A8 , :A9 , :A10 , :A11 , :A12 )

The following deadlock is not an ORACLE error. It is a

deadlock due to user error in the design of an application

or from issuing incorrect ad-hoc SQL. The following

information may aid in determining the deadlock:

Deadlock graph:

-

---

Blocker(s)--

---

-

---

Waiter(s)--

---

Resource Name process session holds waits process session holds waits

TX-001a000b-00003227 21 217 X 17 220 S

TX-0018000a-00003280 17 220 X 21 217 S

session 217: DID 0001-0015-00000003 session 220: DID 0001-0011-00000003

session 220: DID 0001-0011-00000003 session 217: DID 0001-0015-00000003

Rows waited on:

Session 220: no row

Session 217: no row

Information on the OTHER waiting sessions:

Session 220:

pid=17 serial=11 audsid=1838188 user: 22/SAPBWP

O/S info: user: bwpadm, term: , ospid: 8551, machine: jazzsap5

program: disp+work@jazzsap5 (TNS V1-V3)

client info: 0

application name: GP3WBSX6U0JZ9Y7CKS2NPY2NFVD , hash value=538968427

action name: 1330, hash value=1612758974

Current SQL Statement:

INSERT INTO "/BIC/FZSDGL" VALUES( :A0 , :A1 , :A2 , :A3 , :A4 , :A5 , :A6 , :A7 , :A8 , :A9 , :A10 , :A11 , :A12 )

End of information on OTHER waiting sessions.

Pls help to resolve this issue

Regards,

Kris

Edited by: raama krishna on Apr 2, 2008 1:45 PM

[antonio_voce]

Hi,

A deadlock occurs when two or more session are waiting for data locked by each other, resulting in all the sessions being blocked. Oracle automatically detects and resolves deadlocks by rolling back the statement associated with the transaction that detects the deadlock. Typically, deadlocks are caused by poorly implemented locking in application code

The steps necessary to identify and rectify code causing deadlocks are:

• Locate the error messages in the alert log.

• Locate the relevant trace file(s).

• Identify the SQL statements in both the current session and the waiting session(s).

• Use these SQL statements to identify the particular piece of code that is having problems.

• Alter the appliation code to prevent deadlocks by always locking rows in the tables in the same order.

Antonio Voce.

[Former Member]

Hi Antonio Voce ,

Thanx for the reply.

This partiuclar daily load is running for long time and I dont think SQL statements are having code problems.

I am facing this dumps problems only for the last days.

Any further help is appreciated.

Regards,

Kris

[antonio_voce]

Hi ,

so try to apply correction under oss note 84348 - Oracle deadlocks, ORA-00060.

Tell me the result.

Antonio Voce.