cancel
Showing results for 
Search instead for 
Did you mean: 

BW job fails ...deadlock .....

nicola_blasi
Active Participant
0 Kudos

Hello

One of our BW Jobs is failing with the runtime error (DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB). the problem is a deadlock during an insert in an infocube called

ZFI2IC01. The loading happens with DTP

i show you the dump.....I have a Sap netweaver 2004s 700 kernel patch 185.

SAP_ABA 700 0013 SAPKA70013

SAP_BASIS 700 0013 SAPKB70013

ST-PI 2005_1_700 0006 SAPKITLQI6

PI_BASIS 2005_1_700 0013 SAPKIPYJ7D

SAP_BW 700 0015 SAPKW70015

BI_CONT 703 0008 SAPKIBIIP8

ST-A/PI 01K_BCO700 0000 -

the dump:

Err. run-time DBIF_RSQL_SQL_ERROR

Eccez. CX_SY_OPEN_SQL_DB

Data e ora 27.03.2009 12:08:25

Testo breve

SQL error in the database when accessing a table.

Causa dell'errore

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

your transaction.

Possibili soluzioni

If possible (and necessary), repeat the last database transaction in the

hope that locking the object will not result in another deadlock.

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

Analisi errori

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 "WRITE_ICFACT" "(FORM)", 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.

Indic. per la correzione

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

resource"

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

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"

"GP4CHWM2F933QM6RRCD03UJYNTF" or "GP4CHWM2F933QM6RRCD03UJYNTF"

"WRITE_ICFACT"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

"WRITE_ICFACT" "(FORM)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

Ambiente sistema

SAP-Release 700

Application server... "po1bwa3"

Network address...... "10.201.8.17"

Operating system..... "SunOS"

Release.............. "5.10"

Hardware type........ "sun4us"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 4

Shortdump setting.... "full"

Database server... "penelope"

Database type..... "ORACLE"

Database name..... "P1B"

Database user ID.. "SAPSR3"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Nov 18 2008 21:33:14"

create on........ "SunOS 5.9 Generic_117171-13 sun4u"

Database version. "OCI_102 (10.2.0.4.0) "

Patch level. 185

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "SunOS 5.9, SunOS 5.10"

Memory consumption

Roll.... 5938208

EM...... 0

Heap.... 264494208

Page.... 32768

MM Used. 210003688

MM Free. 59808744

Utente e transazione

Client.............. 020

User................ "UE006312"

Language key........ "I"

Transaction......... " "

Program............. "GP4CHWM2F933QM6RRCD03UJYNTF"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

Program............. "GP4CHWM2F933QM6RRCD03UJYNTF"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

Informazioni punto di interr.

Termination occurred in the ABAP program "GP4CHWM2F933QM6RRCD03UJYNTF" - in

"WRITE_ICFACT".

The main program was "RSBATCH_EXECUTE_PROZESS ".

In the source code you have the termination point in line 3605

of the (Include) program "GP4CHWM2F933QM6RRCD03UJYNTF".

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

Job Name....... "BIDTPR_116982_1"

Job Initiator.. "UE006312"

Job Number..... 11132800

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

procedure "WRITE_ICFACT" "(FORM)", but it was neither handled locally nor

declared

in the RAISING clause of its signature.

The procedure is in program "GP4CHWM2F933QM6RRCD03UJYNTF "; its source code

begins in line

3577 of the (Include program "GP4CHWM2F933QM6RRCD03UJYNTF ".

Dett. testo sorgente

Riga Tst.sorg.

3575 * write fact table data with array-insert *

3576 ----


3577 FORM WRITE_ICFACT

3578 USING i_req_SID type RSD_SID

3579 l_DATAP TYPE RSARR_S_RECEIVE_HEADER3-DATAPAKID

3580 CHANGING C_RC LIKE SY-SUBRC

3581 c_lines like sy-tabix.

3582 DATA:

3583 l_facttab type rsd_tablnm. " KFL01: local fact table

3584 l_facttab = '/BIC/FZFI2IC01'. "KFL01

3585

3586 * CALL FUNCTION 'DB_COMMIT'. "Commit falls duprec bei insert!P6 mk

3587 CALL FUNCTION 'RSDU_DB_COMMIT'. "Commit falls duprec bei insert!

3588 c_lines = 0.

3589 SORT GU BY

3590 KEY_ZFI2IC01P

3591 KEY_ZFI2IC01T

3592 KEY_ZFI2IC01U

3593 KEY_ZFI2IC011

3594 KEY_ZFI2IC012

3595 KEY_ZFI2IC013

3596 KEY_ZFI2IC014

3597 KEY_ZFI2IC016

3598 KEY_ZFI2IC017

3599 KEY_ZFI2IC018

3600 KEY_ZFI2IC019

3601 KEY_ZFI2IC01A

3602 KEY_ZFI2IC01B

3603 KEY_ZFI2IC01C

3604 .

>>>>> INSERT (l_facttab) FROM TABLE GU. " KFL01

3606 c_lines = SY-DBCNT.

3607 ***** Check requid if no inconsistency is happened********************

3608 CALL FUNCTION 'RSM_INFOCUBE_WRITE_CHECK'

3609 EXPORTING

3610 I_INFOCUBE = 'ZFI2IC01'

3611 I_RNSID = g_req_sid

3612 EXCEPTIONS

3613 WRITE_NOT_ALLOWED = 1

3614 OTHERS = 2.

3615 **** shortdump if write is not allowed in the current state *********

3616 **** If no entry in the table RSMDATASTATE ===> no abort *********

3617 IF SY-SUBRC = 1.

3618 message x299(brain)

3619 with sy-repid g_req_sid.

3620 ENDIF.

3621 ENDFORM.

3622 ***********************************************************************

3623 * form get_sid Kommentar Read Sid to chavl

3624 ***********************************************************************

Contenuto campi sistema

Nome Val.

SY-SUBRC 0

SY-INDEX 3

SY-TABIX 0

SY-DBCNT 1

SY-FDPOS 4

SY-LSIND 0

SY-PAGNO 0

SY-LINNO 1

SY-COLNO 1

SY-PFKEY

SY-UCOMM

SY-TITLE Eseguire processo batch

SY-MSGTY S

SY-MSGID RSDA

SY-MSGNO 230

SY-MSGV1 ZFI2IC01

SY-MSGV2

SY-MSGV3

SY-MSGV4

SY-MODNO 0

SY-DATUM 20090327

SY-UZEIT 120541

SY-XPROG SAPCNVE

SY-XFORM CONVERSION_EXIT

Chiamate/eventi attivi

N. Tp. Programma Include Riga

Nome

11 FORM GP4CHWM2F933QM6RRCD03UJYNTF GP4CHWM2F933QM6RRCD03UJYNTF 3605

WRITE_ICFACT

10 FORM GP4CHWM2F933QM6RRCD03UJYNTF GP4CHWM2F933QM6RRCD03UJYNTF 795

WRITEIC

9 METHOD CL_RSDD_U_CUBE================CP CL_RSDD_U_CUBE================CM005 60

CL_RSDD_U_CUBE=>IF_RSBK_CMD_U~RECEIVE_DATAPACKAGE

8 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM00Q 132

CL_RSBK_PROCESS=>PROCESS_REQUEST

7 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM002 13

CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~EXECUTE

6 FUNCTION SAPLRSBATCH LRSBATCHU13 411

RSBATCH_EXECUTE_PROCESS

5 FUNCTION SAPLRSBATCH LRSBATCHU01 885

RSBATCH_START_PROCESS

4 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM00Q 233

CL_RSBK_PROCESS=>PROCESS_REQUEST

3 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM002 13

CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~EXECUTE

2 FUNCTION SAPLRSBATCH LRSBATCHU13 411

RSBATCH_EXECUTE_PROCESS

1 EVENT RSBATCH_EXECUTE_PROZESS RSBATCH_EXECUTE_PROZESS 358

START-OF-SELECTION

Variabili selezionate

Nome

Val.

N. 11 Tp. FORM

Nome WRITE_ICFACT

%_DUMMY$$

0000

0000

2222

0000

GU[]

Table IT_71389[28305x92]

\PROGRAM=GP4CHWM2F933QM6RRCD03UJYNTF\DATA=GU[]

Table reference: 1088

TABH+ 0(20) = 0000000118977120000000000000000000000000

TABH+ 20(20) = 00000440000116DD00006E910000005CFFFFFFFF

TABH+ 40(16) = 040002F900001B5000102C8401800000

store = 0x0000000118977120

ext1 = 0x0000000000000000

shmId = 0 (0x00000000)

id = 1088 (0x00000440)

label = 71389 (0x000116DD)

fill = 28305 (0x00006E91)

leng = 92 (0x0000005C)

loop = -1 (0xFFFFFFFF)

xtyp = TYPE#000131

occu = 16 (0x00000010)

access = 1 (ItAccessStandard)

idxKind = 1 (ItIndexLinear)

uniKind = 2 (ItUniqueNon)

keyKind = 1 (default)

cmpMode = 0 (cmpAllDynamic)

occu0 = 1

groupCntl = 0

rfc = 0

unShareable = 0

mightBeShared = 0

sharedWithShmTab = 0

isShmLockId = 0

gcKind = 0

isUsed = 1

isCtfyAble = 1

>>>>> Shareable Table Header Data <<<<<

tabi = 0x000000010AE44D88

pgHook = 0x000000010C6075D0

idxPtr = 0x00000001153EEB10

shmTabhSet = 0x0000000000000000

id = 7929897 (0x00790029)

refCount = 0 (0x00000000)

tstRefCount = 0 (0x00000000)

..................................................

I have applied OSS note 631668 (the first point ) without success.

I can't apply the second point because with DTP is not more available that preocedure as note describes.

I have also applied the following notes using snote...:

1079193

1083305

1089157

1090952

Any help is appreciated

thanks

Nicola Blasi

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

please refer to Note 84348,this is quite useful for these errors

Rohit

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi everyone,

Note was created for solve this type of errors and dumps:

1946893 - ORA-00060 Deadlock in Cube load

Regards,

Janaina

Former Member
0 Kudos

Hi,

Refer SAP note 831234. This note has description of ora-00060 occur during BW loading.

Regards,

Sachin Rane.