ST22 // DBIF_RSQL_SQL_ERROR

[mohsin_m3]

Hello All,

Runtime Errors DBIF_RSQL_SQL_ERROR

Except. CX_SY_OPEN_SQL_DB

Date and Time 15.07.2009 19:10:20

Short dump has not been completely stored (too big)

Short text

SQL error in the database when accessing a table.

What happened?

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

your transaction.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in

procedure "ZCLEAN_SNP_KEY_FIGURE" "(FUNCTION)", nor was it propagated by a

RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is 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.

please help me to resolve the issue.

Regards

Mohsin

[Former Member]

Hi ,

This is due to insufficient tablespace in your database. The table name is listed in error code.

Ask your BASIS administrator to add tablespace.

regards,

Pravash Raikar

[mohsin_m3]

Hello

I have checked tablespace and found no issue related to tablespace

Thanks

MOHSIN

[Former Member]

Hi,

can u paste the DB log which here.

Also try to analyze the logs in SM21 and also the trace files of work processes for which ur seeing these dumps.

If u find difficulty in analyzing the logs and error of trace files(red color errors in trace files) paste the same here.

Regards,

Ravi

[mohsin_m3]

Hello Ravi,

can u pls guide me how i can check DB log?? (Sorry I dont know how to check DB log)

SM37 -- job deatil -- wp id -- found following trace in sm50

Wed Jul 15 14:08:21 2009

• ERROR => PfSetActDBConRec: record not found after insert (3) conn=<LEA> [pfxxstat.c 6816]

• WARNING => PfStatBegin: no DBCON rec for opcode 11 on conn <LEA> [pfxxstat.c 3451]

• ERROR => PfSetActDBConRec: record not found after insert (3) conn=<LEA > [pfxxstat.c 6816]

• WARNING => PfDbProcEnd: no DBCON subrec found for DB conn <LEA > [pfxxstat.c 16466]

• ERROR => PfSetActDBConRec: record not found after insert (3) conn=<LEA > [pfxxstat.c 6816]

• WARNING => PfDbProcEnd: no DBCON subrec found for DB conn <LEA > [pfxxstat.c 16466]

( timestamp >> Jul 15 14:08:21 2009 but job failed at

15.07.2009 19:10:24 ABAP/4 processor: DBIF_RSQL_SQL_ERROR

15.07.2009 19:10:24 Job cancelled )

<SM21> I have paste log in previous mail

-

---

hostname:oraSID 3> more SID_ora_14028950.trc

Dump file /oracle/SID/saptrace/usertrace/SID_ora_14028950.trc

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

With the Partitioning, Data Mining and Real Application Testing options

ORACLE_HOME = /oracle/SID/102_64

System name: AIX

Node name:

Release: 3

Version: 5

Machine: 00C0E09D4C00

Instance name: SID

Redo thread mounted by this instance: 1

Oracle process number: 163

Unix process pid: 14028950, image:

• 2009-07-15 19:10:19.835

• ACTION NAME:(2315) 2009-07-15 19:10:19.833

• MODULE NAME:(/SAPAPO/SAPLPCM_CIF ) 2009-07-15 19:10:19.833

• SERVICE NAME:(.WORLD) 2009-07-15 19:10:19.833

• SESSION ID:(1259.28498) 2009-07-15 19:10:19.833

DEADLOCK DETECTED ( ORA-00060 )

[Transaction Deadlock]

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-00100028-00077bce 163 1259 X 122 1292 X

TX-0047001c-00007cdd 122 1292 X 163 1259 X

session 1259: DID 0001-00A3-00004F61 session 1292: DID 0001-007A-000028EF

session 1292: DID 0001-007A-000028EF session 1259: DID 0001-00A3-00004F61

Rows waited on:

Session 1292: obj - rowid = 000193E2 - AAAZPiAAFAAAAyyAAA

(dictionary objn - 103394, file - 5, block - 3250, slot - 0)

Session 1259: obj - rowid = 000193E2 - AAAZPiAAFAAAAy6AAh

(dictionary objn - 103394, file - 5, block - 3258, slot - 33)

Information on the OTHER waiting sessions:

Session 1292:

pid=122 serial=12028 audsid=3190085 user: 12/SAPR3

O/S info: user: ap5adm, term: , ospid: 4886772, machine: plaixlpc065

program: dw.sapSID_DVEBMGS00@hostname (TNS V1-V3)

client info: 0

application name: /SAPAPO/SAPLOO_TR_READ , hash value=2002299136

action name: 20587, hash value=3538676660

Current SQL Statement:

DELETE FROM "ZSNP_KEY_FIGURE" WHERE "MANDT" = :A0 AND "VERSION" = :A1 AND "IOBJNM" = :A2 AND "MATNR" = :A3 AND "LOCNO" = :A4 AND "BDATE" =

:A5

End of information on OTHER waiting sessions.

Current SQL statement for this session:

DELETE FROM "ZSNP_KEY_FIGURE" WHERE "MANDT" = :A0 AND "VERSION" = :A1 AND "IOBJNM" = :A2 AND "MATNR" = :A3 AND "LOCNO" = :A4 AND "BDATE" = :A

5

hostname:oraSID 4> pwd

/oracle/SID/saptrace/usertrace

Regards

Mohsin M

Edited by: mohsin m on Jul 16, 2009 8:51 AM

[Former Member]

check this note

Note 964859 - DB connection statistics records

Regards,

Ravi

[Former Member]

x

Edited by: Sunil Varghese on Jul 16, 2009 9:30 AM

[Former Member]

Hi Mohsin

The log clearly states that, this error is not an Oracle error:

>

> DEADLOCK DETECTED ( ORA-00060 )
> [Transaction Deadlock]
> 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:
> 

Check with the program behind the job which is causing the error. Check out SAP note 84348, this should give you an insight to the possible causes and solution.

Regards

Rahul

Edited by: Rahul Deo on Jul 16, 2009 3:32 AM

[Former Member]

check alert_<SID> trace file for more info. You can find it in /oracle/SID/saptrace/background.

[Former Member]

Hello mohsin,

This is a generic error caused by no of reasons like duplicate records /entries being insterted in the table or deadocks on the table etc. so i would suggest you look for errors in the system logs, deadlocks in DB , Application locks not realeased ( sm12) etc.

Best Regards

Umesh

[mohsin_m3]

Hello Umesh,

I have checked <DB01> no deadlocks found

<Sm21> following errors found

Deadlock occurred

Database error 60 at DEL access to table ZSNP_KEY_F

> ORA-00060: deadlock detected while waiting for resource

Run-time error "DBIF_RSQL_SQL_ERROR" occurred

> Short dump "090715 191020 hostname 02_SID_02 " generated

can u pls help me how to avoid such dead lock error in future

Thanks in Advance

Regards

Mohsin M

Mumbai

Edited by: mohsin m on Jul 16, 2009 7:54 AM

[Former Member]

Refer this

Regards,

Ravi