cancel
Showing results for 
Search instead for 
Did you mean: 

Short dump in the Warehouse

Former Member
0 Kudos
161

Hello Experts,

I have been receivig below error two or three days in a week and would like to ask you if you met before or i can have your suggestions. You can see the some part of short dump message as below. I am having below error via infopackage dataload.

Category               ABAP Server Resource Shortage
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          11.04.2013 00:36:44

Short text
     SQL error 60 while accessing table "RSODSACTUPDTYPE".

What happened?
     Database error text: "ORA-00060: deadlock detected while waiting for resource"

What can you do?
     Please make a note of the actions and input which caused the error.
     -

     To resolve the problem, contact your
     SAP system administrator.

     Using transaction ST22 for ABAP dump analysis you can see and
     administrate termination messages and retain them for longer periods.
     Please make a note of the actions and input which caused the error.
     -

     To resolve the problem, contact your
     SAP system administrator.

     Using transaction ST22 for ABAP dump analysis you can see and
     administrate termination messages and retain them for longer periods.

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 "SAVE_AGGREGATION_FROM_UR" "(METHOD)", 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:
     Database error text: "ORA-00060: deadlock detected while waiting for resource"

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

I guess that tho problem is in similar times. Isn't it. I think that you have several process chains and in one time there are two processes which are trying to access one table. Due to this there is the deadlock... Try to find what is going on in theese times on the BW and which process are running. Try to reorganize process chains...

Regards,

Tomas

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

usually this error occurs while loading data to a cube without having deleted the indexes first. So before loading the data to the cube make sure you add a process step 'delete index' to your chain and after the successful load add the step 'create index' to your chain. Then your issue should be solved.

regards

Siggi

Former Member
0 Kudos

Hello Siggi,

Thanks for your prompt response. My case is related with DSO and i am having this issue while loading to DSO and there is no either primary index or secondary index on it

Former Member
0 Kudos

well then try to follow Tomas recommendation.

Siggi

RamanKorrapati
Active Contributor
0 Kudos

Hi kenan,

Above error occurs due to the memory space issue, please check with basis team.

Mean while please check the below note.

Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB.

Thanks